• 0 Posts
  • 70 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle

  • Drathro@dormi.zonetolinuxmemes@lemmy.worldIt broke again
    link
    fedilink
    English
    arrow-up
    22
    arrow-down
    1
    ·
    10 days ago

    1000% on the money here. You want encode, decode, calculation, acceleration? They got it. Rock solid, beautiful and simple. You want that shit to actually SHOW UP ON SCREEN? Get the fuck outta here. What do you think nVidia is, a GRAPHICS CARD company!?









  • Drathro@dormi.zonetoLinux@lemmy.mlBest way to swap drives?
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    4 months ago

    Absolutely this. Relatively quick and clean, no messing with installation or reconfiguration. That is, assuming your data isn’t completely corrupted and the old drive doesn’t just outright fail during transfer… But if that happens you were screwed to begin with.




  • Cheaper than Spotify for the number of users it gives you (at least where I live) and the app itself has functioned significantly better than Spotify’s has in my experience so far while not depriving me of any of the artists and albums I listen to regularly. Early on in its life it was big time selling snake oil, but at this point it’s just a solid alternative to Spotify and YouTube music which have both, frankly, gotten “too big to fail” and have begun enshittification because of it. Man we need more competition…





  • You seem to be arguing it’s all about the implementation of the phoning home itself- I’m arguing that running the entire executable/binary through a virtual environment likely has far more drastic performance implications than a phone home, regardless of frequency. It probably IS mostly an implementation problem, but I’m more inclined to believe that the implementation of the Denuvo virtual environment is at fault, not just a server call and response delay. **EDIT: Apologies, forgot to include a link- see HERE. Looks like a substantial/measurable difference. Not massive, as measured here, but certainly enough that if your hardware is just barely able to run a game it could easily make or break the entire experience.



  • There’s an old article on the Arch wiki I used to use HERE. For simplicity I’d just always use section 2.2. Hasn’t ever steered me wrong, but I’m also under no illusions that no digital data is sacred. And if it IS sacred, then it’s already backed up under the 3-2-1 approach. Just make sure you know which device is which so you don’t mix up “if” and “of”. There’s probably significantly more user friendly ways of doing it, but I guess I’m old now so I’m stuck in my ways.


  • Get a same sized drive (or larger) and just dd it? I used to do that all the time, even to Windows installs, if I knew a drive was starting to become unreliable. I’d advise mounting the original/donor drive as read-only to mitigate any potential data losses while transferring. But dd makes a perfect bit for bit copy of any partitions, drives, etc that you feed it. Just don’t get the inputs/outputs backwards! And always remember: dd stands for “disk destroyer” because if you get it wrong, bye-bye data.