[-] Static_Rocket@lemmy.world 28 points 4 weeks ago

Yo, they added full page copies now? Gotta give it a spin again

[-] Static_Rocket@lemmy.world 20 points 1 month ago* (last edited 1 month ago)

Fuck it. Gun it at the brick wall. Jerry's rigging up an emergency break as we speak. Don't mind that the last piece to said break may be missing.

- Man who will probably die before we hit the wall

[-] Static_Rocket@lemmy.world 22 points 2 months ago

Some of them advertised specific performance improvements.

I'm not going to rag on them though. Some of them did have performance improvements and basically created the tools and optimized defaults that propagated to standard distros, allowing the gap to close.

[-] Static_Rocket@lemmy.world 20 points 4 months ago

"You're not just wrong, you're so far off I could make this the pivotal piece of a case study in misinterpreting humor"

God damn.

[-] Static_Rocket@lemmy.world 26 points 5 months ago

I present to you the holy hardware compatibility table:

https://networkupstools.org/stable-hcl.html

Anything not listed there is not worth buying.

[-] Static_Rocket@lemmy.world 21 points 6 months ago* (last edited 6 months ago)

I don't think configuration languages should be turing complete. At that point you're just writing an extension.

[-] Static_Rocket@lemmy.world 21 points 6 months ago* (last edited 6 months ago)

Well, when the game is essentially running in a virtual machine with an address translation layer that scrambles the backing memory every few minutes you're lucky the game even runs. Good luck trying to decipher that hell. A few guys have done it, I remember the one dude ranting on Twitter about trying to crack Borderland's 3 back around launch.

And then the follow up which was that Denuvo was basically adding a ~30fps overhead to the game and everyone was initially blaming the devs for releasing unoptimized garbage.

Gabe had it right, piracy is a service problem. And my motto has always been if the game has some garbage like Denuvo, then you couldn't even pay me to take a copy. Not worth the headache.

[-] Static_Rocket@lemmy.world 21 points 7 months ago

Eh, I welcome the iteration. It gives people a reason to practice and hey, who knows, maybe they'll come up with something neat while rewriting curl or something

[-] Static_Rocket@lemmy.world 25 points 11 months ago

No, no, they've got a point. The architecture of Wayland is much more sane. Because of the way refresh events are driven its also much more power and memory efficient. I'll miss bspwm and picom but man there is a lot riding on simplifying the graphics stack under Linux. The X hacks, GLX, and all the other weird interactions X decided to take away from applications made things non-portable to begin with and a nightmare for any embedded devices that thought GLES was good enough.

[-] Static_Rocket@lemmy.world 20 points 11 months ago

For desktops it doesn't make much sense, but now everything's so oriented to systemd its actually starting to affect embedded Linux applications... so lets try our best to keep the alternatives alive.

[-] Static_Rocket@lemmy.world 25 points 1 year ago

Clippy 3.0 incoming...

[-] Static_Rocket@lemmy.world 21 points 1 year ago* (last edited 1 year ago)

You'll need to do 4 things:

  1. Refresh your keyring
pacman-keyring --init
pacman-keyring --populate archlinux
  1. Remove the archlabs section from your pacman.conf
  2. pacman -Syyu
  3. Maintenance: https://wiki.archlinux.org/title/System_maintenance#Check_for_orphans_and_dropped_packages

This should be everything. You'll need to be careful with removing packages with no upstream. I'm not sure how archlabs distributed their configuration files but if they were packages you'll have to be selective about what you remove. Ideally you'll slowly drop those configs for your own versions with future upgrades.

view more: ‹ prev next ›

Static_Rocket

joined 1 year ago