Earlier quoted context omitted.
Most of your corrections to my story aren't really germane to the point, and mostly involve your constant flogging of a bunch of sysvinit replacements that never caught on, but there's one where I think you move from mere pedantry to being wrong: > In fact, "some people from Red Hat" already had deeper architectural failings with Upstart (which I agree with, but absolutely not with how they decided to "solve" them) a…
Kay Sievers was actually a SUSE employee at the time, IIRC. Now, there's a case to be made that the public statements of intent did not necessarily correspond to the actual function , or strategy that made systemd emerge. Quoting from Lennart Poettering's Linux Voice interview [1]: > We, at that time, thought: OK, Upstart is the future! Scott understood how init systems work – it needs to be dynamic, it needs to reac…
No it doesn't. There is no reason that "conceptually, it was the wrong design" has to contradict with "they had different ideas to me, and couldn't contribute them because of the CLA" and "it could have quite easily evolved into what systemd looks like today, with an active community working on it." It is quite easy to read those statements as being in agreement -- Lennart decided that Upstart wasn't conceptually correct, SJR is amenable to discussing merging changes that would bring Upstart in line with Lennart's ideas, but the CLA is a roadblock so Lennart goes off to form his own project. Why not adopt the principle of charity and take everyone at their word?