Analogy doesn't work because the bomb came first and the reactor later, that is, regarding fission the reactor isn't even here yet. And it was clear from the beginning that the chain reaction is real not hypothetical.
No, there was a functioning reactor built as part of making the bomb.
And it is not a hypothetical concern that a new type of agent might be fundamentally uncontrollable; we're already barely surviving corporations persuing their inhuman goals.
haha that word. back in the 80ies,some polish friends of mine taught me that but refused to tell me what it meant and instructed me to never, ever use it. Until today I don't know what it is about...
Obviously they are not talking about the difference between the two browsers, but between the two situations. Your post looks like you chose the least charitable interpretation in order to pick a fight.
The two situations are also totally different: Chrome has been far better for the Web than IE ever was, and the reason Firefox is still keeping up is that it got that money from Google.
If we decide that Web innovation is done in the browser, and it all has to move to Javascript libraries again, the way we did when browser innovation stalled in the 2000s and we got jQuery, so be it, I suppose.
Oh nice, I wasn't aware. I always associated hacking with "gaining unauthorized access" and googling for the first definition confirmed that I'm my eyes. Didn't know it was the other way around and the term is actually much older than I assumed.
I think you are beating a somewhat dead cow here. systemd wars are over. It's in most mainstream systems nowadays, but there are also lots of cool projects out there doing different things. Everything's fine, nobody wants to go into those old pro and con flame wars any more.
Everything is fine, unless/until many developers begin to assume systemd is present and make software ports to non-systemd Linux (or *BSD) systems prohibitively expensive.
> Nothing wrong with this if a system service is going to be present on 99.999% of installs
Is there a sign linux installs will hit this metric in our lifetime? I don't think there's any strong indication of this. There are multiple distros devoted to not moving to systemd.
> GNOME swapped its service manager for subprocesses (e.g. bluetooth) to systemd user units because it does a far better job.
Not on computers without systemd it doesn't! Besides, Gnome still runs just fine on systems with init scripts like *BSDs with no visible loss of quality or stability so this was a purely political choice to spite their own linux user base.
> There are multiple distros devoted to not moving to systemd
Yes and zero have wide spread adoption outside of specific use cases (e.g. Alpine with containers, Android with its.. slop).
As far as base distros go, only RHEL and Debian have any wide spread impact and both use systemd.
> so this was a purely political choice to spite their own linux user base.
It's possible the old system exists as a fallback, but it wouldn't surprise me if its not guaranteed to stay around. People aren't required to support other peoples choices unless you pay them.
> Nothing wrong with this if a system service is going to be present
This kind attitude will be the death of Linux. In the form of systemd-os.
> a system service is going to be present on 99.999% of installs
It's not, because a large number of users and system administrators dislike it, and don't use it. And the high number it does have is mostly due to distributions forcing it on you - so that you can only remove it by switching distributions altogether.
With every new Ubuntu version I have to carve out new metastasis no one asked for. For example, 24.04 (or maybe even 23.10) changed the way sshd is started up - by systemd listener instead of sshd on its own like it was for decades. This way they saved a few megabytes of RAM (solely on computers that are not exposed to the internet, of course).
While fighting against systemd-as-PID1 is futile for many years, fighting against the spread is definitely worth it.
Fair, point taken: Some people are working on systemd replacements because they want to build some cool things in that area. Just like there are multiple programming languages and no one says "Why don't you just use Java/C++" it should be OK to work on Linux systems without systemd and not think too much of it.
This doesn't make sense. I, for one (transitioning to Linux usage only gradually), haven't been aware of the systemd and its criticism, and I'm grateful for the info. Then, the informed users can vote with their feet. Things change all the time, and only mass adoption/usage is what makes a given distribution to be mainstream or niche.
So, please do continue to criticize, continue to raise awareness. That's useful.
> Then, the informed users can vote with their feet.
That's the thing, that it is quite difficult to vote with your feet. You can't remove systemd from your distribution in favor of separate independent facilities: The combination of its design, its gradual expansion, and the way some higher-level packages depend on it (especially GNOME) - typically prevent its removal.
So, you would need to switch distributions, which most users are not very inclined to do. And - even then, you look around, and you see that the big basic distros: RedHat/Fedora, Debian (and Ubuntu), Arch - use systemd. So almost all of the distributions based on them are also not an option if you want to avoid systemd.
... and the bottom line is that users will effectively not vote with their feet. And neither will system administrators, or whoever maintains OS images at organizations, because it's difficult for them to tell their superiors they want to switch everyone to, say, Slackware, or Devuan.
While you could argue that it's flooring, it feels much more like truncating. We have a inner representation of time that's like yyyymmdd-hhmmss-mmmm and we truncate it to the precision we need for a given task. If we need the month we truncate to yyyymm, and if we need hours we truncate to yyyymmdd-hh.
That's quit intuitive for all kind of time precision, and the author's rounding solution would be somewhat counterintuitive, at least for me.
reply