3 ms·

So you want Swing apps on Android?

anonymouse12 9y ago
Quit shilling for your employer. No one takes this argument about a piece of technology (swing) that has not been relevant for over a decade and a half seriously. Look up the history of innovations that Java and in particular the hotspot JVM brought to the mainstream. Enough with this false narrative that java and the jvm sucked and was in decline and Google swooped in and saved it. Some of the creators of your beloved V8 and Go Lang were the very same folks who helped create the hotspot JVM. Google basically pulled a fast one by not buying a license and they knew the consequences even at the time this occurred.
cromwellian 9y ago
Someone flagged the comment before I could post my response, but here it was (re: Google didn't save Java on the client): Java on the server was not in decline, but Java on the desktop was declining, had declined. Applets were dead, very few success stories around Java Web Start. And the main three 'consumer' success stories for Java on the frontend were Limewire, Minecraft, and IntelliJ/Eclipse. As a consumer facing technology, Java was a complete failure. No sane person wanting to ship a commercial, consumer app to end users would consider Java as a first choice. I have been a Java developer from the day HotSpot Alpha was released, I say this as someone who loves the platform. Personal Java failed. I worked for years on J2ME apps, Java on high end Nokia Phones, Java on Palm devices (Ghost VM), etc. All these platforms amounted to nada. Flash was far more widely used for front end user facing apps than Java. Ditto for Visual Basic. The relevance of the Swing comment is the people complaining about the fragmentation of Java's write-once-run-anywhere promise, which was always more of a promise than a reality. If you want to make a viable mobile Java, you had to remove Swing, Java2D, CORBA, JMX, and a ton of other JDK libraries, which is exactly what Sun did with the various profiles as well. But once you do that, you have "fragmentation" If Google had not produced Android, I can bet the leading platform today for mobile development that is not from Apple, would either be Xamarin based C#, or some scripting language like Lua or Python on top of a Linux widget toolkit. Java would not be in the mix at all. Or perhaps it would FlashMX sitting on top of Linux (ugh)

Quit shilling for your employer. No one takes this argument about a piece of technology (swing) that has not been relevant for over a decade and a half seriously. Look up the history of innovations that Java and in particular the hotspot JVM brought to the mainstream. Enough with this false narrative that java and the jvm sucked and was in decline and Google swooped in and saved it. Some of the creators of your beloved V8 and Go Lang were the very same folks who helped create the hotspot JVM. Google basically pulled a fast one by not buying a license and they knew the consequences even at the time this occurred.

cromwellian 9y ago

Someone flagged the comment before I could post my response, but here it was (re: Google didn't save Java on the client): Java on the server was not in decline, but Java on the desktop was declining, had declined. Applets were dead, very few success stories around Java Web Start. And the main three 'consumer' success stories for Java on the frontend were Limewire, Minecraft, and IntelliJ/Eclipse. As a consumer facing technology, Java was a complete failure. No sane person wanting to ship a commercial, consumer app to end users would consider Java as a first choice. I have been a Java developer from the day HotSpot Alpha was released, I say this as someone who loves the platform. Personal Java failed. I worked for years on J2ME apps, Java on high end Nokia Phones, Java on Palm devices (Ghost VM), etc. All these platforms amounted to nada. Flash was far more widely used for front end user facing apps than Java. Ditto for Visual Basic. The relevance of the Swing comment is the people complaining about the fragmentation of Java's write-once-run-anywhere promise, which was always more of a promise than a reality. If you want to make a viable mobile Java, you had to remove Swing, Java2D, CORBA, JMX, and a ton of other JDK libraries, which is exactly what Sun did with the various profiles as well. But once you do that, you have "fragmentation" If Google had not produced Android, I can bet the leading platform today for mobile development that is not from Apple, would either be Xamarin based C#, or some scripting language like Lua or Python on top of a Linux widget toolkit. Java would not be in the mix at all. Or perhaps it would FlashMX sitting on top of Linux (ugh)