>>It's this ability to make major architectural changes that differentiates
>>free software from commercial software, as the accounting people and the
>>marketing people don't have any leverage as to what goes into the OS. It
>>allows us to stay "pure" in the technical sense and not full of legacy
>>wrappers and useless or over-hyped features. And the one place we REALLY
>>do not want legacy interfaces hanging around is the kernel.
> Linux hasn't been around long enough for anyone to call _any_ of the
> published interfaces ``legacy'' After 15 years, maybe, but certainly
> not after 8.
1 year is enough for internal kernel interfaces... Or even 1 month...
> ____
> david parsons \bi/ At 100k code-bloat per major release, there are many worse
> \/ things to worry about than whether it's time to kill
> off the stable interfaces
Code bloat is not a problem. Ugly hacks needed to keep old interfaces around is.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/