Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I don't disagree with your rebuttal of GP's post, that said,

Google with Android Java have no else but themselves to blame.

That argument is equivalent to "well, you should just have not left your door unlocked". Just because Google could have used OpenJDK and thus avoid the lawsuit doesn't mean they should have to do so.

And Microsoft's case is completely different, as they did get a license from Sun, and preceded to deliberately violate it, with the intention (as we know from the internal emails and documents) of killing Java.



Google is also killing Java with their Java 6 and a half fork, without any public roadmap how future versions are going to be supported.

This will become even worse after Java 9 and 10 get released, specially with the infrastructure API and language changes they bring in.

So if Google keeps their stubbornness, any Java library writer will be faced with support Android Java or official Java dilemma.

And hacks like RetroLamba aren't going to help anyway.

I really don't see any difference in behavior vs what Microsoft did.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: