Poettering has clearly the better arguments than this reactionary Draxinger die-hard.
Could you provide the counterarguments?
I don't have a gnome session in my login manager because I don't need i18n for the words "login" and "password". (although that would be totally possible without a whole gnome session). I don't have a braille line so i can't say anything about accessibility, but that should be (in a ideal unix world) a single printf to /dev/braille. Also the feedback is audible and visual, this seems to be no issue to me.
Edit: Plus saying X breaks Y so X is not needed is not a good argument. Because you have not addressed if X is needed or not, only said that Y breaks.
I think I can safely say that if X breaks Y, and I need Y than X sucks. Especially if it worked before X came. X made things worse.
/edit: I think that's why Poettering is hated so much. There was community on the Nixes, with their own ecosystem and their own way to do stuff. It's wasn't always beautiful or nice, but their had their way to solve stuff so it would a kind of blend in with the rest. And then Poettering wants to turn it into MacOS X or Windows and adds stuff new users probably appreciate, but the old users never misses. There is a cultural shock. And then it breaks backwards compatibility. It shouldn't suprise anybody that this product should rather be superb and not just medicore to accepted.
The problem with "it's not the UNIX way" argument is that a lot of people don't care about UNIX that much, they just want a good system. Poettering mentions in that video that all his, and his colleagues' work (pulseaudio, consolekit, udev into udisks/upower) has been done because there was an actual demand for those features. There is a reason why most distributions use their work even as people complain about them.
Is there really anything at all that a majority of Unix-derivative users can agree on?
https://bugzilla.redhat.com/show_bug.cgi?id=461546
First, he denies that this is something people need. Then, when he is told that people need it, he says that they are just doing things the wrong way. Then, when people point out that this is neither unusual nor the wrong thing to want to do, he just repeats that this is not what was intended so too bad. He offers no advice on how to do things the right way despite being the only person who seems to think that everyone else is wrong.
------------------------------- Internal Server Error
TracError: IOError: [Errno 2] No such file or directory: '/home/lennart/svn/trac/pulseaudio/VERSION'
--------------------------------
That kind of sums up.
For data shared by sevaral users, I very much prefer some separate /data/service/instance/... structure. Also much easier to allocate sane directory permissions.
This doesn't answer your question of course. There is still the 'why' of it.
Why has this become the standard?
The homedir is a volatile place. Where users reside often. And make changes often. Any place humans change things is a place where stuff breaks easily and on a regular basis. What if Lennard calls 'rm' with a wrong switch? Or chown? Or chmod? The service receives pain.
Or he could decide that he no longer wants his homedir to be readable/executable by everyone on the system, so he chmod 0700 his homedir. Forgetting that this will render his trac instance unavailable.
Or what about sharing some responsibility? How is Lennard ever going to share the maintenance of the ticketing system with anyone else? What impact will that have on the ticketing system? Will it have to be migrated anyway to /srv or /usr/local or /opt? What configs will that affect? What about the webserver configs? What about file permissions, uids, gids?
What about backups? Are they configured for this specific service? If it is ever migrated to another location, do they have to be reconfigured? Or will /home/lennard just be backed up as before and no one will remember that trac is now in /srv/trac, making a restore improbable.
What about a reboot? Will the service come back up? What if you have to re-implement this service on another machine after this one explodes? Are you sure you did not forget to point /etc/rc.local (or some other hack) to your new machine?
These are only the reasons I could think of off the top of my head. And most of these are actual examples from the field.
A standard is a standard, because it works for more people than just you. The question you, and lennard, should be asking yourself is: How can these standards work for me as well?
(As you can probably tell, I grew up in Ops, not Dev. I have seen the pain of the 'works-for-me'-mentality.)
Also, cnvogel is obviously more consise than me. :-)
I don't know whether existing open bugs were moved over at the time though.
"Why knowing your hardware is important" http://www.youtube.com/watch?v=QUUdVFZBd5g
"Scalable Parallel Programming Techniques" http://www.youtube.com/watch?v=jfimI7UC9Pg
When a problem is easily solved by just an "apt-get remove X" it is easy to start hating the piece of software. No matter who was actually at fault.
By making Linux audio temporarily problematic Linux audio became a solved problem (at least in my mind, and the minds of many users of the major distributions that use it)
Stop it.
And yes I reported the bugs.
I realize that is all anecdotal and I could be one of the few people in the world who still have problems with it.
And everytime, without fail, audio starts working again.
That's pretty much where my analogy falls apart, so I'm ditching it.
Whether I'm capable of contributing to a project that does not, in its current state, suit my needs has nothing to do with whether I'm in a position to contribute to that project.
This is especially true when there is an alternative that I'm already accustomed to using.