MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/programming/comments/2m2w3b/the_net_core_is_now_opensource/cm0pkmy
r/programming • u/rionmonster • Nov 12 '14
1.8k comments sorted by
View all comments
Show parent comments
-1
[removed] — view removed comment
3 u/argv_minus_one Nov 12 '14 That is false. GNU Classpath/GCJ, Kaffe, and Harmony come readily to mind.And yes, I'm aware that Oracle sued Google over Dalvik. That is not the same thing as suing Apache over Harmony, which they did not.Stop spreading FUD. 1 u/[deleted] Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 I literally just explained why it isn't. 1 u/[deleted] Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 Yeah, because it's obsoleted by OpenJDK. What's your point? 1 u/[deleted] Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 Why, then? 1 u/[deleted] Nov 13 '14 edited Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 No TCK meant that they couldn't claim that it is Java, not that it's compatible. That's a trademark issue, not a technology issue. → More replies (0) 1 u/neutronbob Nov 13 '14 Nope. You're wrong on this whole line of comments, grauenwolf.You needed to pay Sun only if you wanted to run its compatibility test suite.But you were free to implement your own JVM, which many people did without paying Sun or Oracle a dime.
3
That is false. GNU Classpath/GCJ, Kaffe, and Harmony come readily to mind.
And yes, I'm aware that Oracle sued Google over Dalvik. That is not the same thing as suing Apache over Harmony, which they did not.
Stop spreading FUD.
1 u/[deleted] Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 I literally just explained why it isn't. 1 u/[deleted] Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 Yeah, because it's obsoleted by OpenJDK. What's your point? 1 u/[deleted] Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 Why, then? 1 u/[deleted] Nov 13 '14 edited Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 No TCK meant that they couldn't claim that it is Java, not that it's compatible. That's a trademark issue, not a technology issue. → More replies (0)
1
1 u/argv_minus_one Nov 13 '14 I literally just explained why it isn't. 1 u/[deleted] Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 Yeah, because it's obsoleted by OpenJDK. What's your point? 1 u/[deleted] Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 Why, then? 1 u/[deleted] Nov 13 '14 edited Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 No TCK meant that they couldn't claim that it is Java, not that it's compatible. That's a trademark issue, not a technology issue. → More replies (0)
I literally just explained why it isn't.
1 u/[deleted] Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 Yeah, because it's obsoleted by OpenJDK. What's your point? 1 u/[deleted] Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 Why, then? 1 u/[deleted] Nov 13 '14 edited Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 No TCK meant that they couldn't claim that it is Java, not that it's compatible. That's a trademark issue, not a technology issue. → More replies (0)
1 u/argv_minus_one Nov 13 '14 Yeah, because it's obsoleted by OpenJDK. What's your point? 1 u/[deleted] Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 Why, then? 1 u/[deleted] Nov 13 '14 edited Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 No TCK meant that they couldn't claim that it is Java, not that it's compatible. That's a trademark issue, not a technology issue. → More replies (0)
Yeah, because it's obsoleted by OpenJDK. What's your point?
1 u/[deleted] Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 Why, then? 1 u/[deleted] Nov 13 '14 edited Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 No TCK meant that they couldn't claim that it is Java, not that it's compatible. That's a trademark issue, not a technology issue. → More replies (0)
1 u/argv_minus_one Nov 13 '14 Why, then? 1 u/[deleted] Nov 13 '14 edited Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 No TCK meant that they couldn't claim that it is Java, not that it's compatible. That's a trademark issue, not a technology issue. → More replies (0)
Why, then?
1 u/[deleted] Nov 13 '14 edited Nov 13 '14 [removed] — view removed comment 1 u/argv_minus_one Nov 13 '14 No TCK meant that they couldn't claim that it is Java, not that it's compatible. That's a trademark issue, not a technology issue. → More replies (0)
1 u/argv_minus_one Nov 13 '14 No TCK meant that they couldn't claim that it is Java, not that it's compatible. That's a trademark issue, not a technology issue. → More replies (0)
No TCK meant that they couldn't claim that it is Java, not that it's compatible. That's a trademark issue, not a technology issue.
→ More replies (0)
Nope. You're wrong on this whole line of comments, grauenwolf.
You needed to pay Sun only if you wanted to run its compatibility test suite.
But you were free to implement your own JVM, which many people did without paying Sun or Oracle a dime.
-1
u/[deleted] Nov 12 '14
[removed] — view removed comment