Linked by Thom Holwerda on Tue 16th May 2006 22:13 UTC, submitted by adstro
Thread beginning with comment 125316
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.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2005-07-06
i am sorry if i offended, it was a joke, apologies for that word.
But i dont understand your last point here. why are you trying something evil on the changes in Sun? in the recent years basically they changed their strategy. it is perfectly ok for a commercial company to change their strategies. aparently in the OS arena they understood that it is difficult to live without open sourcing it. Same way, their enterprise suite was not selling they preffereed to open source it and focused on service.
The thing is, Java should be treated a little differently when subject is Open Source. it is being used by so many third party companies, open sourceing it should be done with extreme care, they cannot allow code to be changed without strict test and quality measures and i guess they feared fragmentation may break backward compatibility and VM or language may change in not so experienced hands. Also, being open source does not add too much vaue to SUn's Java since code is perfectly downloadable and comunity contributions are already accepted by Sun. To me , All they need to do is to make contribution easier, provide version controlled source access and building much easier, thats it.