https://bugs.kde.org/show_bug.cgi?id=355892
--- Comment #14 from Mathieu Roy <yeu...@gnu.org> --- Martin Gräßlin, [off topic to this bug report that will anyway not amount to anything] Quotes should be used only to quote. No one ever wrote anything about a "systemd conspiracy" here, so let's drop this whole notion. You don't care what I'm using, though in your first reply you immediately suggest to me to use systemd. A bit much for someone that actually have no opinion about it. A quick look at your blog tells a lot. You wrote "To me it is clear for quite some time already that I won’t accept patches any more for non-Linux. Including another code path or even a build flag for non-Linux systems is not worth the increasing maintaining costs. If non-Linux systems want to include patches they should do it downstream", "Yes and I fully agree with Lennart on not including non-Linux OS in systemd. And I hope that Debian will decide for systemd and the motivation for this blog post was mostly systemd with both Debian and KDE in my mind" http://blog.martin-graesslin.com/blog/2011/08/thoughts-about-kde-plasma-on-non-linux-systems/ Downstream, isn't it a thing for you? There is no conspiracy (what, are we 5 year old?) but you surely look like someone not totally neutral about systemd. And you have the right too. It is not a problem per se. What I really said, though, is I find unlikely that coding an alternative to systemd is feasible in the long run. I scratched my itch, as you see, I went back using an outdated upower. I do not have time to do more than that and, most importantly, I dont think it is sensible to actually do more than that. Now, if we are here to give opinions, I'd just say that since this whole systemd story started, it looks like we are talking about something major in computing. Conspiracies? Seriously? Well, how to put it? Almost no one I know in life knows KDE. No one. Or one. KDE is a considerably minor desktop environment on a system still unfit for many simple desktop users. If using it itches too much, there is another option: looking somewhere else. Long time ago, ten years before you were even working on KDE, I was puzzled by what was going with GNOME. I was using GNOME and thought that their plans for GNOME 2 was a joke, for instance deciding to give to a company that came out of nowhere ( https://en.wikipedia.org/wiki/Eazel ) the task to write a new file manager out of the blue. Despite user community questioning this approach, they went with it. Turns out it was not at all a success story. I stopped using GNOME at that time. It was not such a big issue for me, I lived with it with no problem. It did not change everything for GNOME, they just lost users with GNOME 2. This systemd whole story looks to me more the business of young software developers that found a way to have a central role in GNU/Linux than anything else. So what's next? Maybe you are right, maybe systemd will turns out to be the best choice and ten years from now no one would imagine GNU/Linux without it. If you are wrong, well, KDE will continue to lag behind Apple OS X and MS Windows, despite its qualities. I already stopped using Konqueror two years ago. I was tempted to stop using kmail and I was forced to make people I know using thunderbird because of the unreliability of kmail2. It is not like quitting KDE is impossible. There is no killer feature. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
