4 ms·
The thing is, the aforementioned trait is far too generic - it's a characteristic of how development is structured, and has little or nothing to do with the mor
by vezzy-fnord 12y ago
The thing is, the aforementioned trait is far too generic - it's a characteristic of how development is structured, and has little or nothing to do with the more technical aspects of the Unix design, which is what is being contested.
It's not just Unix. Development in a single repository has been how almost all operating systems were done.
In fact, standalone kernels have usually been research projects throughout the years. Linux is a notable exception.
- the_why_of_y 12y agoOf course you can get more specific - for example, the Solaris kernel/libc combination is so tightly coupled that it is described as a "welded unit" https://www.youtube.com/watch?v=TrfD3pC0VSs#t=29m10 https://www.youtube.com/watch?v=TrfD3pC0VSs#t=29m10 OpenBSD solved the Year 2038 problem by incompatibly changing the kernel and libc ABI in lockstep, which broke every single existing binary application using time_t - how's that for tight coupling... http://www.openbsd.org/papers/eurobsdcon_2013_time_t/ http://www.openbsd.org/papers/eurobsdcon_2013_time_t/