Devuan
What's the trade off of having a non systemD system?
I need a no BS assessment, not some "proselytic" stuff or wishful thinking
Is it doomed to be "deprecated" in some way? As in, past a certain date in a not so distant future, support will drop entirely for instance
Because if you're going to have PID 1 responsible for everything and doing the dishes, you might as well install windows?
I realise this may verge on "proselytic", but it really does come down to a difference in design philosophy - systemd violates the "do one thing and do it well" approach of *nix software design. This makes it not only more frustrating to work with (personal opinion), but also more difficult to replace - the latter point more-so as a result of its creeping integration with other software (This is the part where I'd glare at GNOME, but honestly, fuck GUI's, man. Tiling terminal or bust. TILING TERMINALS OR BUST.)
Though, this thread has now forced me to think about computers three days early.
You assholes!
>TILING TERMINALS OR BUST
I agree
It's too bad nobody is maintaining an i3 debian based distro... Or arch based, or whatever
I've gone tired of installing the entire kit everytime I have to for whatever reason, this + this + this + this + this.... Oh fuck I forgot that pain in the ass again...
I've made a stripped down i3 ubuntu live distro with installer using cubic... 700 Mb...
But well, I'm not a pro, and I would rather prefer a team of pros doing this shit, because I don't want to play make ubuntu image disk for the rest of my days every time a new distro version is out
...
But really my concern about non systemd distros is about... What it's going to become in 5 years for instance. Are people going to drop it because "go with systemd it's the future!" ?
Because it sounds a bit like that
I used to be a pretty standard one-monitor-one-terminal sort of guy up until I installed xmonad on a lark one afternoon some years ago now. Why xmonad? Because haskell, which to someone who comes from a C and COBOL background, seemed like awfully futuristic space magic.
Anyway...
I'm not a pro, and I would rather prefer a team of pros doing this
The problem with putting trust in the so-called professionals is that the truck number goes down and the whole enterprise becomes institutionally fragile. Just remember that where open-source is concerned, they're not really capable of doing anything you aren't.
"go with systemd it's the future!"
If you find yourself in any sort of sysadmin type position, then I'd say that it pays to understand it if only for the reason that one might encounter it in a professional capacity. As for one's own systems, that comes down to how one wants them configured, and how much effort one is willing to put into maintaining that.
One of the big draws of the *nix world is that things are modular and easy enough to replace, and that you're rarely stuck with one solution to a problem. Even systemd, for all of its deep integration with other things, can be carved out and replaced. Alternatives will remain as long as people see fit to maintain them.
I think the big reason we're seeing systemd itself become so popular as of late, is that it's the big corporate-backed solution to parallelizing init, largely for the popular-conciousness marketability factor of low boot times. Looks good on the promotional materials, but it is still a specific optimisation for a specific use case.
Personal anecdote: I couldn't possibly care less about boot times. My machine spends over twenty minutes training RAM when it POSTs anyway. An extra minute or two to load the OS is meaningless to the man who's outside having coffee.
Much of the Linux world is going with systemD so yeah you will be missing updates for the next several years probably.
(post is archived)