On Tuesday, March 25, 2014 11:40:02 AM UTC-5, Jonathan Dowland wrote: > I was very proud of my fellow colleagues for not feeding the troll a > full 24 hours later. Thanks for breaking the record :(
Jonathan.... we've been through this before. -> https://lists.debian.org/debian-devel/2012/11/msg00565.html -> https://lists.debian.org/debian-devel/2012/11/msg00604.html You think I'm retarded or a troll. Believe it or not, I can actually sympathize with why you think that. I too, would find myself to be a huge pain in the ass if I threw a wrench into something as big as systemd. I recognize the frustration, I really do. But I am not trolling you here. There is something that you fundamentally don't get.... -> if I present a question regarding the interaction of linux and systemd -> and you get pissed with me because it's too exhausting or difficult to formulate a response -> that means you don't really understand how the interaction between linux and systemd works Yes. That's the point (not to piss you off, but to test what you comprehend). That's why engineering has the phrase to begin with... -> if you can't put it in writing, then you don't understand it well enough Because it's pissing you off, it's telling me that we have a problem with the design of systemd. It's underthought. Dangerously underthought. This entire time, my concerns were never about the features of either program. It was always about the design. Features don't make good software.....good design makes good software. systemd is its own project (operating system?). It does not have any design blueprint for how it works with linux. That's why you need to pull it out of linux, because it's trashing all the good designs for crap that we can't even explain very well in writing. Which means that we don't really know what this is doing. And when we don't really understand what something is doing, we are extremely vulnerable to a symphony of problems waiting to occur. I would say that.... trying to resolve the default init system hassle is one example of a problem that could have been easily avoided if we had a blueprint for how systemd is designed. Please try to look past my failings with using lists, and see that we really do have a nightmare situation on our hands. -Kev -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cadkoaximadsjomvwd1xihlglp3v8utfyb4bqrpa+u0bypz3...@mail.gmail.com
