• 4 Posts
  • 74 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle


  • Shit shit shit, I just remembered I haven’t attended English class all semester.

    Shit shit shit, I can’t remember my locker combination, and I can’t find the orientation sheet that has it, also I can’t find my class schedule, I have no idea what class I’m supposed to be in right now.

    Plus a few other variations. All High School. I dunno why the focus on High School, I’m 34. I get one of these once or twice a month.









  • JakenVeina@lemm.eetoGames@lemmy.worldLegend of Zelda
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    2
    ·
    edit-2
    3 months ago

    Gotta be Breath of the Wild, for me. Taken together with Tears of the Kingdom, the series’ storytelling and immersion has never been better, I think, and as a game, Breath of the Wild was the tighter, more-satisfying experience, overall.

    Wind Waker is a veeerrrrrrry close second. I think it’s the most-polished entry in the whole series, in both categories. I’m really not sure what I would change, if given the chance.




  • I think it’s a fallacy to say that you can or should build an application layer that’s completely DBMS agnostic. Even if you are very careful to only write SQL queries with features that are part of the official SQL standard, you’re still coupled to your particular DBMS’s internal implementations for query compilation, planning, optimization, etc. At enterprise scale, there’s still going to be plenty of queries that suddenly perform like crap, after a DBMS swap.

    In my mind, standardization for things like ODBC or Hibernate or Entity Framework or whatever else isn’t meant to abstract away the underlying DBMS, it’s meant to promote compatibility.

    Not to mention that you’re tying your own hands by locking yourself out of non-standard DBMS features, that you could be REALLY useful to you, if you have the right use-cases. JSON generation and indexing is the big one that comes to mind. Also, geospatial data tables.

    For context, my professional work for the past 6 years is an Oracle/.NET/Browser application, and we are HEAVILY invested in Oracle. Most notably, we do a LOT of ETL, and that all runs exclusively in the DBMS itself, in PL/SQL procedures orchestratedbbybthe Oracle job scheduler. Attempting to do this kind of data manipulation by round-tripping it into .NET code would make things significantly worse.

    So, my opinion could definitely be a result of what’s been normalized for me, in my day job. But I’ve also had a few other collaborative side projects where I think the “don’t try and abstract away the DBMS” advice holds true.





  • Generally speaking, fault protection schemes need only account for one fault at a time, unless you’re a really large business, or some other entity with extra-stringent data protection requirements.

    RAID protects against drive failure faults. Backups protect against drive failure faults as well, but also things like accidental deletions or overwrites of data.

    In order for RAID on backups to make sense, when you already have RAID on your main storage, you’d have to consider drive failures and other data loss to be likely to occur simultaneously. I.E. RAID on your backups only protects you from drive failure occurring WHILE you’re trying to restore a backup. Or maybe more generally, WHILE that backup is in use, say, if you have a legal requirement that you must keep a history of all your data for X years or something (I would argue data like this shouldn’t be classified as backups, though).