3 ms·
Such strong opinions. > GC sucks > android app Android's runtime is not the Java Runtime. I'm starting to think Oracle should have at least gotten some damag
by niftich 10y ago
Such strong opinions.
> GC sucks
> android app
Android's runtime is not the Java Runtime. I'm starting to think Oracle should have at least gotten some damages from Google for causing so many people to think that the stuff running on Android is the Java and getting people like this guy vocally misplacing the blame.
> name clash: X and Y have the same erasure
Programmer unfamiliarity. Consume a List<T> with one function.
> Methods With the Same Name as Constructors
Constructors are never void. Obviously, because they have to return the object.
> Inner classes Don't Work
This is a quip. What's the critique?
There are a handful of reasonable points but the overall product is not. Furthermore, the pre-emptive rebuttals make it clear that there's no convincing them.
- deleted 10y ago[deleted]
- flukus 10y ago> Android's runtime is not the Java Runtime. I'm starting to think Oracle should have at least gotten some damages from Google for causing so many people to think that the stuff running on Android is the Java and getting people like this guy vocally misplacing the blame. Because java desktop apps had such a good reputation before android?
- BoorishBears 10y agoNo, but I said this the other day, Google made things worse by spreading its "Java 6.5" hybrid mess. Now we have Java 6 with 7 features and Java 8 with no Java 8 APIs being called Java 7 and Java 8 by people new to Java...
- niftich 10y agoIndeed; looking back, we made the same points, and I don't think it's an isolated sentiment. While Android may have positively affected the Java ecosystem at first, official Java has long since evolved in appreciable ways that Android-compatible code can't use. It's awful, and until Android gets a wholesale port of the new APIs it won't get any better -- and despite Oracle being no angel, none of this is their fault.