On 2013-01-23 20:45:49 -0800, Russ Allbery wrote: > Adam Borowski <kilob...@angband.pl> writes: > > > There are two ways to design a system: > > * a monolithic well-integrated system, granting features and efficiency at > > the cost of portability and hackability > > * the traditional Unix way, with a stress on replaceable tools that do only > > one thing, granting freedom to tinker, using the system in a way not > > envisioned by its creators > > ...at the cost of occasional complex, difficult-to-debug interactions > between the separate components, and a larger total code base to support > fallbacks and alternatives to provide loose coupling between the > components.
I disagree. A monolithic system makes things more difficult to debug, in particular when one needs to include 3rd-party code, because everything gets tainted (e.g. the Linux kernel + non-free drivers, Firefox + extensions...). A clean separation between components with a good specification makes more clear where a bug can be. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130125134737.ga25...@xvii.vinc17.org
