Hell, pass init=/bin/yes and you’ll see even more greatly reduced RAM usage!

❯ ps aux | grep /usr/lib/sys | awk '{print $6}' | sed 's/$/+/' | tr -d '\n' | sed 's/+$/\n/' | bc
266516

So that’s 260 MiB of RSS (assuming no shared libs which is certainly false) for:

• Daemon manager
• Syslog daemon
• DNS daemon (which I need and would have to replace with dnsmasq if it did not exist)
• udev daemon
• network daemon
• login daemon
• VM daemon (ever hear of the principle of least privilege?)
• user daemon manager (I STG anyone who writes a user daemon by doing nohup & needs to be fired into the sun. pkill is not the tool I should have to use to manage my user’s daemons)

For comparison the web page I’m writing this on uses 117 MiB, about half. I’ll very gladly make the tradeoff of two sh.itjust.works tabs for one systemd suite. Or did you send that comment using curl because web browsers are bloated?

For another comparison 200 MiB of RAM is less than two dollars at current prices. I don’t value my time so low that I’ll avoid spending two bucks by spend hours debugging whatever bash scripting spaghetti hell other init systems cling onto to avoid “bloat”. I’ve done it, don’t miss it.

What even are GCC’s advantages in 2024, besides “we painted ourselves in a corner with proprietary extensions” (e.g. Linux)? That aside I personally only see upsides to clang, but I don’t routinely do C work and maybe I’m missing something.

Removed by mod

Source?

In the EU at least this is demonstrably false. LNG has slightly risen since 2000 but other fossil fuels (namely coal) have gone way down. Total consumption has been steadily declining in the past few years and is down to 2004 levels. So overall our electricity is a whole shitload cleaner.

The story is even starker for domestic heating. Gas and coal are vanishing since the mid-2000s.

Wait until you learn about debhelper.

If you use a debian-based system, unless you have actively looked at the DH source, the one thing that built virtually every package on your system, you do not get to say anything about “bloat” or “KISS”.

DH is a monstrous pile of perl scripts, only partially documented, with a core design that revolves around a spaghetti of complex defaults, unique syntax, and enough surprising side effects and crazy heuristics to spook even the most grizzled greybeards. The number of times I’ve had to look at the DH perl source to understand a (badly/un)documented behavior while packaging something is not insignificant.

But when we replaced a bazillion bash scripts with a (admittedly opinionated but also stable and well documented) daemon suddenly the greybeards acted like Debian was going to collapse under the weight of its own complexity.

ls -l /proc/xxx/{fd,syscall}

Camera pans down to resource locks hiding under the floorboards

It’s not as bad nowadays that apps yielded to GNOME’s bullshit. Back when GTK2 apps were still common… Urgh. Plenty of apps were broken without it for no good reason.

I like opinionated UX - I use sway - but GNOME’s approach is incompatible with “general use” and only works (for now) because of canonical’s weight and ability to impose their vision as the only vision.

Also they didn’t replace the tray with a better way to manage background apps, so they can suck a dick on the UX front.

The fucking system tray. Which literally every other DE and mainstream OS out there supports because some apps depend on it and break if it doesn’t exist.

Last I checked GNOME devs said “no, we will never support it, because we’ve DePRecATeD the tray in GTK”.

It’s functionality so basic I have 3-6 apps which depend on it at any time on my work machine. Anyone saying it doesn’t fall under “basic functionality” is either a GNOME dev or a troll.

I agree with what you’re saying, but you’re shifting the goalpost.

Everyone is cheering Wayland on, no one believes it’ll succeed

That parent comment (and other comments like it in these threads) are what I take issue with. You can make the exact same argument why people should stick with Windows and not bother with Linux.

This software has been in development for a long time and still doesn’t work for my niche usecase and this therefore UNUSABLE and DOOMED TO FAIL

• Actual Linux users, completely oblivious to the irony of that sentence

There are quite a few mature projects in 0.x that would cause a LOT of pain if they actually applied semver.

I am generally of the opinion that version numbers do not matter at all until the author/distributor has GUARANTEED that they do. Until then they’re worthless, including in places where semver is supposedly enforced like NPM. If I had a penny for every NPM package that broke my project after removing the package-lock.json, I could retire.

It’s just a generational difference.

The Gen Xers get really confused because to them a stereotypical “computer nerd” is (was) a greasy 35 year old in his mom’s basement which is covered in RMS posters who would unironically 741k l1k3 7h15.

To us zoomers a stereotypical “computer nerd” is a proudly neuroatypical GNC queer with a body pillow of their waifu.