tag:blogger.com,1999:blog-741750605858169835.post4697977383888489616..comments2024-01-24T14:53:02.919+00:00Comments on Stephen Colebourne's blog: No Java SE 7 - US DOJ investigationStephen Colebournehttp://www.blogger.com/profile/01454237967846880639noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-741750605858169835.post-85632479106036566132009-07-10T03:13:34.000+01:002009-07-10T03:13:34.000+01:00Your conclusion that "the DOJ is concerned ab...Your conclusion that "the DOJ is concerned about the licensing of Java" completely misses the actual procedural reason for the delay. It takes little more than someone asking for something to be investigated for antitrust reasons, and they have to delay the merger while that investigation is done. Someone asked, and they did. No matter how much we might dislike the license terms, there is no reasonable legal theory under which java licensing could be construed as an antitrust issue, so we can expect the investigation to be wrapped up without much effect.Neal Gafternoreply@blogger.comtag:blogger.com,1999:blog-741750605858169835.post-68857933581172259272009-07-09T13:23:25.000+01:002009-07-09T13:23:25.000+01:00@Stephen, @MikeJ: How exactly do you think they ca...@Stephen, @MikeJ: How exactly do you think they can make Java 'non-open-source again'? They might be able to choose not to do any more public development themselves, but the cat is out of the bag; we'll always have HotSpot and the libraries in their current state available under the GPL now.<br /><br />FWIW, I agree that this whole mess with the Java 1.7 JSR and 'field of use' issues needs to be sorted. The only way I see to do this properly is to open up the whole JSR process and the TCK, making it available for all. That's the only way any trust can be established; how exactly do you trust the results of a TCK that has only been run on Sun-derived JDKs (to my knowledge) and which can not be publicly verified? Such an open playing field would benefit those involved in Harmony, GNU Classpath and OpenJDK if done right.Andrew John Hugheshttp://fuseyism.com/noreply@blogger.comtag:blogger.com,1999:blog-741750605858169835.post-33864028237077529702009-07-07T06:58:16.000+01:002009-07-07T06:58:16.000+01:00@Mike J but if Oracle start to charge money to use...@Mike J but if Oracle start to charge money to use Java then all the ecosystem will fall apart and Java will be dead, thats for sure. <br /><br />Everybody will migrate maybe to PHP, Python, Ruby, C#.Net and C++. The cobol people will continue with cobol why bother and the people that cant move out from java cause they already invested lots, have to pay they will be ofcourse pissed. <br /><br />This is a bad move of sun not to have a promised spec for Java SE. Java have been always a trap and trouble platform. Do you remember in 1998 i think Sun didnt let go Java to an open standard and I thinki it will never be. Also I think .Net is more healthy. Or much better LAMP or C++ are more healkthy and true open.<br /><br />This is sad sad sad for Java folks.OtengiMnoreply@blogger.comtag:blogger.com,1999:blog-741750605858169835.post-12357761056233443962009-07-01T07:35:43.000+01:002009-07-01T07:35:43.000+01:00Interesting blog posting Stephen. If I were in Ora...Interesting blog posting Stephen. If I were in Oracles position, once the acquistion has been completed, I would start charging a license fee for commercial use of new versions of java runtimes. Starting off with charging a low fee which could be then be gradually increased each year. What would you do about java if you were in charge of Oracle?Mike Jnoreply@blogger.comtag:blogger.com,1999:blog-741750605858169835.post-82670281132773620352009-06-30T15:16:40.000+01:002009-06-30T15:16:40.000+01:00@Fatih, As of today, Sun still holds all the cards...@Fatih, As of today, Sun still holds all the cards. This means that they could make Java non-open-source again, or they could make Java no longer an open standard or they could start charging for Java. Each of these possibilities are worth all Java developers being concerned about.Stephen Colebournenoreply@blogger.comtag:blogger.com,1999:blog-741750605858169835.post-13022309812411136772009-06-30T13:00:10.000+01:002009-06-30T13:00:10.000+01:00I find it quite assumptive to claim that this is o...I find it quite assumptive to claim that this is of concern to every Java developer. It is a big issue for developer who are contributing to Java in any way. It is less so for developers, who use Java as a programming language for their everyday work. I have read every blog entry you have made in the last couple of months, and never did I see how the JCP problems affect me as a Java developer.Fatih Coskunnoreply@blogger.comtag:blogger.com,1999:blog-741750605858169835.post-41770269307439141402009-06-29T15:28:08.000+01:002009-06-29T15:28:08.000+01:00Hopefully this means there will come a "JCP o...Hopefully this means there will come a "JCP organisation" of some sort. This is more relevant then ever with an owner that doesn't share Sun's reputation in the open source world.<br />Creating an independent Java organisation would help their reputation immensely.Jaap Beetstranoreply@blogger.comtag:blogger.com,1999:blog-741750605858169835.post-27072472502966696522009-06-29T14:25:51.000+01:002009-06-29T14:25:51.000+01:00I would support the idea of DoJ's blocking of ...I would support the idea of DoJ's blocking of the merger, at least until Sun starts the Java SE 7 JSR and makes some progress in the JCP'd field of use issue.Osvaldo Pinali Doederleinhttp://weblogs.java.net/blog/opinali/noreply@blogger.com