Because of the bureaucracy... I have invited people from debian to make conferences and know myself one of the former DLP. Debian has something scarily bureau

Because of the bureaucracy... I have invited people from debian to make conferences and know myself one of the former DLP. Debian has something scarily bureaucratic in its organization. As an effect of conway's law (structure of the organization gets in the product) the debian developer's guide is like hellish, their level of indirection for forcing everyone in the LSB without breaking the change in the "reasonnable" default conf are heavy. And not even close to correction : the spliting package policy (avoiding too much dependency) makes installed python or latex feels broken. It is like the heaven of both former soviet idealism (comitee of workers handling the positions), and engineers (debian can easily be considered an example of the best practices of ISO 9001/ITIL process) With good intentions. I used to be a debian sysadmins for 15 years. I mean, they really are trying their best to : satisfy everyone in choosing the best default conf/options/requirements so that other packages integrates well. The embedded world, x86, ARM, virtualisation. But I think bureaucracy sometimes ends up like a cancer. Bureaucracy requires to drains part of your effort into its sustainability, and sometimes the energy involved in bureaucracy itself out sucks to much resources for even getting the job done. I think they try to hard to do what they think the right things. I am not even sure they have a clear view of their monster blob distro. Mozilla fundation is another new growing tumor in the world of open source. Do we really need to had statefullness over a stateless protocol in order to bring RT in a non realtime-able container ? When will the brainwashing of the XUL team will end? NO! the web browser is a terrible substitute for GUI especially in async fashion. And js is a terrible scripting language for GUI. Tcl/Tk should be back again.