Linked by Kroc Camen on Thu 1st Oct 2009 21:02 UTC
Thread beginning with comment 387317
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Apple didn't fork X then because X was in a terrible state then. A huge amount of work has gone into it since then and I have a feeling that if Apple had to make the decision today, it would be much more likely to fork X.
Sure, but in some ways things were actually better in the 1990s with 1990s hardware and X than it is in the 2000s with 2000s hardware and X.
Now that I think of it, beyond anything else my first impression is the enduring instability during the whole decade.
The funniest thing is that when they completely broke their development process, moved to git, etc., the X stack is constantly in an immense state of chaos.
Git isn't the problem. They just need more manpower. There is a big discussion going on on their listserv right now about how to fix the development process and get more people involved. That is, IMO, the biggest problem facing X today. The technical issues can be surmounted, but not without enough developers and testers to make it happen.
Isn't google going to ditch X as well with ChromeOS?
Anyways X obviously still has problems, just look at some of the complaints in this recent thread:
http://www.osnews.com/comments/22271







Member since:
2006-01-02
Apple didn't fork X then because X was in a terrible state then. A huge amount of work has gone into it since then and I have a feeling that if Apple had to make the decision today, it would be much more likely to fork X.