Re:Lennart Poettering on Systemd's Tumultuous Ascendancy in ...
by zeveb on Friday January 27, 2017 @05:23PM
(#13503262)
> I'm actually OK with the possibility of getting away from "everything is a file".
I actually much prefer going all the way with everything-is-a-file; when Poettering tried to claim that his printer is not a file, I really wonder if a) he's even heard of Plan 9 b) he knows about PostScript.
Where I'm not a fan of systemd is that it's all written in C, instead of a higher-level, safer language, and that we're getting to a point where systemd-terminal, systemd-browser and systemd-nano aren't a joke but mandatory.
Re:Lennart Poettering on Systemd's Tumultuous Ascendancy in ...
by digi_owl on Saturday January 28, 2017 @07:20AM
(#13505942)
That seems to be an ongoing flaw of his, and others around him. No real interest in the history of UNIX. Where it came from and why it is the way it is.
All he sees is a nice pile of drivers to bootstrap whatever computing project he wants to get done, and thats it.
Re:Lennart Poettering on Systemd's Tumultuous Ascendancy in ...
by JdeBP on Saturday January 28, 2017 @04:32AM
(#13505599)
I am unaware that systemd-terminal ever was a joke. It was there for a time, called systemd-consoled, and then quietly pulled in July 2015. Lennart Poettering failed to respond when asked about it.
* https://news.ycombinator.com/item?id=9722163
* https://plus.google.com/+LennartPoetteringTheOneAndOnly/post...
I'm actually OK with the possibility of getting away from "everything is a file". Although I still think that's a good starting point and should probably be the default case for most things.
Where I am not a fan of systemd is the extent to which it violates the single responsibility idea. That is, it does too many different things, and it's basically a monolith. Make it easy to substitute alternative implementations of logging and the like, and I wouldn't necessarily object to it.