black0ut

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.

Side note for Arch (btw) users: If you run xz --version, it will report to be version 5.6.1, even if it's the updated version. This is because the updated and presumably safe package is xz 5.6.1-2.

The backdoor didn't really affect Arch, because it only compromised SSH when it was linked against liblzma, which is a requirement for libsystemd. However, Arch doesn't link it that way, so it's safe to use. You should still update though, because we don't know if the backdoor could be used in any other way.

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.

Spain has not really banned Telegram. It has instituted a temporary restriction while the company appeals. However, this restriction isn't really enforceable, because it must be implemented within 3 hours of the ISPs receiving the ban notice. However, ISPs can only receive these notices oficially on working days, and right now they're celebrating easter.

Telegram has 3 days to appeal the ban, and it probably will appeal before ISPs start blocking it. The appeal will most probably be accepted (as Telegram is an important company, and many people there use it as their only messaging app).

Thus, the ban will probably be lifted even before ISPs start blocking Telegram, unless something goes terribly wrong.

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.

Wayland, Texas. According to wikipedia it had a population of 100 people in the year 2000. AFAIK it's a ghost town now.

I know that town because I once read a "fun fact" about the Wayland Protocol that said its name was chosen for being the name of an actual town, which (supposedly) cannot be copyrighted.

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.

No, because then people would be able to exit it. I'd say they are :, w and enter.

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*

Java code is run inside a client (JRE) that provides it a non system-dependent runtime environment. If there's a JRE for your OS, all java programs should work fine regardless of the OS.

This is the case with Minecraft, for example. When the launcher was still based on Java, you could run the Windows executables on Linux and it worked.

However, some programs might still not work on another OS despite it having a JRE. That could be caused by intentional limitations or the use of a system-specific library.