No, systemd is not the bane of Linux. What existed before it was much worse. Upstart was a totally broken mess and almost all sysv init scripts contained several bugs.

I don't like systemd but it is a lesser evil.

Upstart? These Ubuntu-centric kids will never learn. OpenRC works fine there.

Meanwhile people still have issues on turning off their machines.

systemd is not an init system; it _contains_ an init system. It is a huge swatch of the whole userspace of a Linux system up to shell or GUI sessions - and having an init system was just an excuse; and in fact, the systemd point brought up in the linked article is unrelated to init systems.

There are quite a few init systems: The venerable sysvinit, runit, s6, openrc and others. You don't like upstart? Ok, choose another one, there are many. Here is a comparison table by the Gentoo folks:

https://wiki.gentoo.org/wiki/Comparison_of_init_systems

As for the claim of "almost all sysvinit scripts contained several bugs" - that's both hyperbole and false. Plus, you seem to be implying that systemd has not been troubled by bugs, which of course it has (and that does not disqualify it; the fundamental design and organizational nature as a project are the disqualifiers).

The systemd init system is quite the Trojan horse, though. I prefer it greatly to SystemV init. Most of the rest of systemd varies from unremarkable to problematic in my opinion.

One bright spot is systemd-networkd allows one to change quite a few things about interfaces in the way server automation platforms expect to work without doing a network restart. The workaround otherwise on, say, CentOS was always to write the new config file used by future restarts, also run CLI commands to update things in memory, and be sure to tell the service not to trigger a restart on the config file(s) changing. Otherwise if you’re doing something like streaming UDP video your own automation can become a reliability issue.

Yes, I am. And these days Google has become about as bad as DDG. And not because DDG has become better.

Have read this comment before multiple times, even a year or two ago. Hence my “unreasonable” demand for screenshots if someone has the minutes to script it. - Hmm, really should be a live site to track over time... Can make that and Show [Three People On] HN!

(Google could give better results to those unloyal to them, as one example, so testing needed! We could be getting wildly different results or just have starkly different usage tendencies, there’s just no way I could disagree with so many of y’all on something this basic assuming no DDG astroturfing or anything unless we’re looking at things differently one way or another)

Waiting for your screenshots. Do the legwork yourself first.

And obviously there is no astroturfing here from DDG. That you could have seen from a tiny look at my profile. I have a pretty public persona on the internet.

Thanks, and important to say beyond not accusing them I was _definitely_ not accusing you!

Yes, it us common among people who use git and it makes reviews of complex features much easier.

I looked at one thing the bun developers wanted to fix in Zig and the issue with it was a bad idea which would not have been merged even if it had been written by a human.

And hurting AMD.

Nah, feel free to insult any company I have worked for or even the company that I am one of the founders of. I don't see why that should be off limits. But do not insult me as a person.

> Do they just write a bullet list of notes and then tell the LLM to go wild?

Pretty sure that is what most of them do.

Spruce allergy is a thing but it is rare. Only a few unlucky people suffer from it.

No, that is only the cause of some of the uptime issues. Some have clearly been caused by deploying briken code.

Given that exactly the same thing has been regulated as gambling in Europe under the name "betting exchange" for 25 years the case for it being gambling is quite strong.