View Single Post
Old 08-11-2014, 10:41 AM   #176
ApK
Award-Winning Participant
ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.
 
Posts: 7,393
Karma: 68715774
Join Date: Feb 2010
Location: NJ, USA
Device: Kindle
Quote:
Originally Posted by taosaur View Post
I actually appreciate the major mobile platforms pushing developers away from Flash and Java, forcing them to adapt to HTML 5.
While I get (and agree) that HTML5's open standard is the better way to go than proprietary plugins like Flash for multimedia content on the web, and while I appreciate the chicken-and-egg necessity of "adopt HTML5 first, eliminate codec fragmentation later," I don't see what HTML5 has to do with Java, in the sense of a multiplatform, full-fledged development platform.

Sure, it can eliminate the need for Java-based media viewers, just like it does for Flash-based ones, but it offers no alternative for how to run your Java apps without a JRE, or more correctly, it offers no alternative for Java app developers to port their work over to.

IOW, IMHO:
Killing Flash support on a platform to encourage HTML5 = reasonable disruption.
Killing Java support on a platform to encourage HTML5 = too disruptive, if you use any Java apps.

p.s. "disruptive" in this context is not as positive a thing as in the context that Jack Tingle used it above...."

Last edited by ApK; 08-11-2014 at 10:48 AM.
ApK is offline   Reply With Quote