Oh right, somebody looked at the spec for 15 minutes, mis-read it completely (confusing the authentication protocol with the actual IPC protocol) and wrote a blog rant about their failure in reading comprehension. Very compelling.
> The fact that you even NEED a (crappy) doc is a sign it doesn't use the Unix design philosophy.
So HTTP is against the UNIX philosophy too? Or did you also happen to implement that without ever looking at the specification?
> In contrast, look at the Debian Control File format, which apt metadata is stored in.
In other words, apples make better apple juice than oranges.
> That reason being: you simply end up with less code when your systems are modular and composable.
You seem to be under the mis-apprehension that monolithic is somehow an antonym of modular. systemd is both modular and monolithic (in your meaning of that term).
Oh right, somebody looked at the spec for 15 minutes, mis-read it completely (confusing the authentication protocol with the actual IPC protocol) and wrote a blog rant about their failure in reading comprehension. Very compelling.
> The fact that you even NEED a (crappy) doc is a sign it doesn't use the Unix design philosophy.
So HTTP is against the UNIX philosophy too? Or did you also happen to implement that without ever looking at the specification?
> In contrast, look at the Debian Control File format, which apt metadata is stored in.
In other words, apples make better apple juice than oranges.
> That reason being: you simply end up with less code when your systems are modular and composable.
You seem to be under the mis-apprehension that monolithic is somehow an antonym of modular. systemd is both modular and monolithic (in your meaning of that term).