Linked by Thom Holwerda on Fri 4th Jan 2008 20:35 UTC, submitted by koki
Permalink for comment 294326
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2005-08-26
This is the kind of post I love to read.
How do you eat an elephant?
One spoonful at a time.
Likewise with Haiku, by tackling huge efforts like this, we inevitably have to finish, revise, improve, and complete parts of the OS that have been or are missing, defunct, incomplete, etc.
It's very likely that the things that keep us from being self-hosting are the very things we'll need to overcome to port OpenJDK.
OpenJDK will inevitably attract new developers to the project. This means more people who are capable of fixing, fleshing out, and finishing things within Haiku itself -- even if it is for their own curious or selfish desires.
In the end, we all benefit.
Projects like WebKit and OpenJDK aren't just narrow-minded, one-trick ponies. They breed a larger community as well as improve the quality and quantity of code in Haiku.