There's one fundamental difference between X and the kernel that I haven't heard mentioned here. Linux for servers is a thriving and profitable business; Linux for clients (desktop, laptop, PDA, phone etc..) is promising and might make money outside of a few narrow niches one day.
Server ($$$) and Client (?$) both need the kernel; only client needs X, so much more $$ flows into kernel than into X.
Given the resources that are being made available for X vs the complexity of the features being demanded (functional parity with Windows but on perhaps 1/50th the investment) the development work is going surprisingly well. There is not a big demand for schedule predictability from the groups and individuals contributing resources, but there is a big demand for progress, and that results in the project management model (take aim, write down the plan, then everyone develops like crazy until it's done) you see today.
The spirit among the developers is very enthusiastic and positive; everyone seems to be trivializing Dave's comments. His point is not that priorities and approaches are being set based on the whims of the developers; his point is that many of the developers are working for successful companies with clear priorities, and those priorities are where the developers spend *most* of their time.
Server ($$$) and Client (?$) both need the kernel; only client needs X, so much more $$ flows into kernel than into X.
Given the resources that are being made available for X vs the complexity of the features being demanded (functional parity with Windows but on perhaps 1/50th the investment) the development work is going surprisingly well. There is not a big demand for schedule predictability from the groups and individuals contributing resources, but there is a big demand for progress, and that results in the project management model (take aim, write down the plan, then everyone develops like crazy until it's done) you see today.
The spirit among the developers is very enthusiastic and positive; everyone seems to be trivializing Dave's comments. His point is not that priorities and approaches are being set based on the whims of the developers; his point is that many of the developers are working for successful companies with clear priorities, and those priorities are where the developers spend *most* of their time.
Comment