Afaik it wasn’t a temperature problem, it was voltage related. Obviously cooler temps help, but you would probably still be vulnerable to this.

Wow, I’ve actually never seen this disc. However, funnily enough, I have another disc with that program burned into it. Someone didn’t read the notice, it seems.

The launch was terrible, but there are some things that keep them apart from the rest of terrible launches.

Cyberpunk 2077 was a really ambitious game, with a lot of new mechanics and incredible graphics. Beasts like that are really difficult to optimize for a large range of computers with different specs, so at first it ran poorly on some.

The most notably buggy release was the PS4 one. And rightfully so. They were trying to run a truly next gen game on a console which was more than a decade old. They not only had to optimize the game, but they basically made a completely different game, with different assets and engines, which was really difficult to do. Still, it was too much for the console, especially old PS4s that were full of dust or had old fans and were overheating.

Another important fact is that users were also pressuring CDPR into releasing Cyberpunk 2077. It was delayed at least once (maybe twice, I don’t remember), and people wanted to play the game. They probably had to choose between delaying it another time or releasing it without polishing it that much.

I believe it was Cyberpunk 2077 that started the trend of “release now fix later” games. However, I don’t think they really did it on purpose. The game was too ambitious for its own good, and having to develop, optimize and test two basically different versions of it was too big of a task for a studio that in today’s terms wasn’t even that big. The rest of the AAA producers just realized that CDPR still won loads of money at launch, and decided to release incomplete games on purpose, after seeing that CDPR could make profits that way.

But must importantly, CDPR did an amazing job at fixing the game, unlike many other studios releasing broken AAAs. They optimized the code, fixed most of the bugs, improved the AI massively and made the game really stable, to the point where I’ve seen it running at 40 FPS on 10+ year old overheating laptops. Even though it took a while, they still delivered the game they promised to their buyers.

Wait, what happened now? Do they want to ban Lemmy?

🔫🔫🔫

Afaik, they are unblockable. They are served from the same domain as the video, so if you block them you can’t see the video either.

Instead of blocking it at the domain level, you can install adblockers on almost any platform. I recommend uBlock for Firefox and ReVanced for Android. ReVanced is also supposed to work on Android TVs, iirc.

The thing about parallel booting is it’s only faster in systems with lots of cores, and the overhead of the parallelized code is sometimes enough to negate the benefits in older processors.

My machine is a Core 2 Duo lappy, which allows me to run most modern programs cheaply. However, it’s slow (even though I don’t use DEs either), and laptops are the kinds of computers you boot multiple times a day. That’s why I care about boot times. And in this case, you can see that booting with a parallelized init system is slower than booting with a “regular” one.

Yeah, Systemd might be the new fad, but I still believe there are lots of things to learn from the simple init systems. After all, an init system should only focus on initializing a system, and it shouldn’t be as complex and complicated as Systemd is.

I might be just another old man yelling at clouds. But hey, that makes two of us now.

I run Void with runit.

I’ve tried to completely avoid systemd, and so far I think I’ve managed. It’s still a pain in the ass, because a lot of software depends on it.

As an upside, startup time on my old lappy went from 2+ minutes on barebones Arch with systemd to just under 40 seconds on Void with runit.

It’s slow and heavy, and it does too many things. It’s a monolithic piece of code so big it’s getting too difficult to maintain, so it has more vulnerabilities than other alternatives. It’s also taking over the whole system, to the point where Linux systems will soon be Systemd/Linux instead of GNU/Linux.

It’s also developed and funded mainly by Microsoft, which is also something people don’t really like. Microsoft are trying to make it similar to Windows in some ways, which makes it way more difficult to debug random errors.

And it doesn’t follow the UNIX guidelines, which is just the cherry on top.

If you use Arch, you aren’t really affected. As far as we know, the backdoor only affects SSH if it is linked against liblzma, which is a requirement for libsystemd. However, Arch doesn’t use that, so SSH has probably been safe. However, you should still update, because we don’t know if the backdoor could’ve been used in other ways.

Note that if you update, xz 5.6.1-2 will be installed. This is a safe version. However, if you run xz --version, it will still report version 5.6.1.

Why is the prong at the right shorter than every other one? Bad fork, 1/5. Giving it a 1 and not a 0 because it’s probably heavy and I like that.

Obligatory “I use Arch, btw” comment. I’ve been using Arch for years and, honestly, it isn’t that much of a pain. It mostly works with the defaults, installation is really easy now with archinstall, and there’s a ton of software ready to install from the repos or the AUR. Besides, the arch wiki is amazing and has solutions for many of the problems you’ll ever have.

Yes, we use it. However, it’s more common to say “hubiera”. There’s no specific rule to differenciate between both, but at least in the center and north of spain we mostly use “hubiera” for first person and “hubiese” for third person.

“Ojalá hubiera podido ir, pero tenía deberes” (yo)

“Ojalá David hubiese venido, se lo habría pasado bien” (él)

As I said, both options would be correct in both cases, and probably in other places they use the words differently.

the’r*

Spaces can exist in filenames. The only problem is that they have to be escaped. As the comment that you reread explained, cat hello world.txt would print the files hello and world.txt. If you wanted to print the file "hello world.txt" you’d either need to quote it (cat "hello world.txt") or escape the space (cat hello\ world.txt)

People are really creative when it comes to potholes, huh?

I do like this way of dealing with them though. You get a laugh, it doesn’t harm anyone and gets the potholes noticed.

Discord on Xorg is a mess too. It’s not even the electron part, the app itself is really bad.

Not only it’s inefficient, but (at least in Arch) it doesn’t auto update on big versions. And instead of just warning you, it refuses to start until you manually install the new update. And god forbid if the package mantainers need a day or two to update the package, because until then you can’t use it.

The funniest thing is, there’s a file in the app’s directory called “build_info.json” which contains the version number, and with a simple edit you can make it think it’s updated, and it suddenly works without problem.

I really don’t know what they’re updating, but I have a version from 2021 running on my phone (it’s old and the new app is really slow), and it still works fine. Even after the account handle change and several other additions to the app.

Oh, and for the Arch users: there’s a discord version on the AUR called “discord-canary-electron-bin” that uses system wide electron, so it should be updated faster than discord’s own bundled electron. I don’t know if there’s a non canary version of it, tho.

On summer we normally hit 40+ (in some places even 45+) in Spain. I can confirm it’s hellish.

the fact that you have to go to other years proves that this happens way more rarely in France than in the USA. In fact, you can see that in all of the graphs there are gun related deaths in every country.

The point is that it happens 100 times more in the USA than in any other developed country

you can't really hot swap the kernel, because all of the system runs on it.

you'd need to stop the system (you can save its state and recover where you left), reboot to load the new kernel and let it take control.

however, there are some distros and programs that allow you to hot swap certain parts of the kernel (mainly drivers) without rebooting. Note that, even though the system doesn't reboot, most packages still need to be restarted for them to pick up the new driver.