• 2 Posts
  • 662 Comments
Joined 7 months ago
cake
Cake day: June 9th, 2024

help-circle

  • It is mostly professional/office use where this make sense. I’ve implemented this (well, a similar thing that does the same thing) for clients that want versioning and compliance.

    I’ve worked with/for a lot of places that keep everything because disks are cheap enough that they’ve decided it’s better to have a copy of every git version than not have one and need it some day.

    Or places that have compliance reasons to have to keep copies of every email, document, spreadsheet, picture and so on. You’ll almost never touch “old” data, but you have to hold on to it for a decade somewhere.

    It’s basically cold storage that can immediately pull the data into a fast cache if/when someone needs the older data, but otherwise it just sits there forever on a slow drive.





  • …depends what your use pattern is, but I doubt you’d enjoy it.

    The problem is the cached data will be fast, but the uncached will, well, be on a hard drive.

    If you have enough cached space to keep your OS and your used data on it, it’s great, but if you have enough disk space to keep your OS and used data on it, why are you doing this in the first place?

    If you don’t have enough cache drive to keep your commonly used data on it, then it’s going to absolutely perform worse than just buying another SSD.

    So I guess if this is ‘I keep my whole steam library installed, but only play 3 games at a time’ kinda usecase, it’ll probably work fine.

    For everything else, eh, I probably wouldn’t.

    Edit: a good usecase for this is more the ‘I have 800TB of data, but 99% of it is historical and the daily working set of it is just a couple hundred gigs’ on a NAS type thing.



  • One thing you probably need to figure out first: how are the dgpu and igpu connected to each other, and then which ports are connected to which gpu.

    Everyone does funky shit with this, and you’ll sometimes have dgpus that require the igpu to do anything, or cases where the internal panel is only hooked up to the igpu (or only the dgpu), and the hdmi and display port and so on can be any damn thing.

    So uh, before you get too deep in planning what gets which gpu, you probably need to see if the outputs you need support what you want to do.




  • underestimate how much work Mozilla does in standards and low-level shared API’s via w3c

    Oh, I didn’t mean to disparage the work they do: I know it’s important and extensive. I’ve been a Firefox user since, well, it was called Netscape. It’s a critical piece of software.

    I was mostly just rolling my eyes at the sheer panic they’re having with the only funding source they’ve bothered to cultivate going away, along with the fact that a good portion of that money is spent on things that aren’t the browser, and frankly, don’t bring a lot of value to the table or matter in the slightest.

    Dumping the Corporation baggage and making the Foundation strongly independent makes a lot more sense than begging to let Google keep paying them, which seems to be their approach, at least based on that open letter.










  • The problem was it was too quick: if you died of COVID, you were dead. You could be memory-holed and everyone would simply forget you and move on.

    If you had Polio, though, you were paralyzed and stuck in a metal tube and kept alive.

    Can’t forget your not-dead kid who lives in a tube, and thus it was treated as more of a thing that should be fought because there was a clear and visible reminder of what this disease was doing to everyone’s kids.

    If COVID left a couple million people living in tubes, then we absolutely would have treated it differently, but it didn’t.

    (Alternately, if COVID had killed 10 or 20 million people, we would have also treated it seriously: it just wasn’t sufficiently deadly OR left a wake of broken, but living, people.)