On Tue, 04 Sep 2012 11:07:23 +0200
"Dominique Leuenberger a.k.a DimStar"
And 'how long is long' in software development?
Depends whom you ask. Enthusiasm for change is in reversed proportion to available time. If you can learn something in 1 month with 8 hours a day devoted to learning, then someone with 1 hour needs 8 months. So, if a new software comes in 2 years downtime is respective 4% and 33%. While above is idealized picture, where learning is separated from usage, lost time on handling computer and its software is what irritates people. Even geeks would like to watch a movie, or even help other geeks, instead of learning something new all the time just to have computer running. It makes people tired and prone to look for some not so labor intensive alternative. PS. I don't oppose focus on systemd, but at the same time I'm not sure how much more frustration I can take. While 12.2 RC2 worked fine, update to 12.2 broke system, then it recovered on its own, after night powered off, and then second update broke it again, this time much better, only power switch works. Rescue system locks even before normal boot, as it appears, because NetworkManager can't start. No command line. Luckily grub2 works, so I can access 12.1. Problem is that I don't know grub2, systemd and all newly introduced spaghetti before, between and after them, so I can't help myself and, of course, after years helping others that is frustrating. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org