Javalobby - Comments for "Java Was Not The First To Tout WORA" Comments for "Java Was Not The First To Tout WORA" en I had a job where the code <!--paging_filter--><p>I had a job where the code was constrained to ansi "C" and had to compile and run on every "C" platform.&nbsp; That was a joke.</p><p>I was attracted to Java and then to HTML because they were platform independent and had nice screen independent layouts.&nbsp; HTML works pretty well with different browsers.&nbsp; Applets were dependent on the browser, browser JVM or plugin, and Java OS install, which is still a problem today.&nbsp; Java is dependent on the quality and consistency between JVMs.&nbsp; It gets you at least 95% or 99% of the distance, which apparently is better than mobile HTML5.</p><p>If we are going to reach WORA nirvana, Java on a device specific JVM is as likely as anything to do it.&nbsp; Another possibility is that one device or device OS gains near 100% market share and we just program to that device OS (I hope it supports Java).<br /></p> Sun, 03 Mar 2013 02:39:43 -0500 comment 95691 at " HTML 5, as an application <!--paging_filter--><p>"&nbsp;HTML 5, as an application development technology, takes you about 60 - 80% of the way home, depending on what you want your application to do." &nbsp;For many apps, even less than that. &nbsp;You almost need at least one if not more JS libraries and/or frameworks. That is most of the work.<br /></p> Mon, 25 Feb 2013 19:01:31 -0500 mknutty comment 95257 at  LOWE - Learn Once, Write <!--paging_filter--><p>&nbsp;LOWE - Learn Once, Write Everywhere.<br /></p> Mon, 25 Feb 2013 17:45:30 -0500 qphase comment 95251 at  I started programming <!--paging_filter--><p>&nbsp;I started programming applets (R.I.P) in 1996 - the golden era of the MS JVM and the beginning of the browser wars that would only escalate for the next 10 years before settling into a mutual pact of stated incompatibility and indifference to the great developer population. After a few years of that horrible career choice I scooted to the backend and never looked back until 2006 when I bought a Blackberry for the purpose of programming. One look at the API and the crap emulator was all it took. Goodbye!<br /></p><p>I had no idea that anything could be as bad as applets, let alone worse. Mobile dev made applets look like sunny fields of wild flowers blowing gently in the wind. You can't even say "Hello World" in the mobile world without compiling against platform specific APIs.</p><p>But I will say this - if this were 20 years ago, each phone would have their own programming language instead of just their own Java API. Let's not forget that. (By the way, I still own and use that Blackberry phone.)<br /></p> Mon, 25 Feb 2013 17:41:07 -0500 qphase comment 95249 at