 such a
strategy we would by now have a relatively simple way to develop software
which runs on 99% of laptops and 85% of smartphones and tablets. Developers
would now be targeting 'Android first' instead of 'web app first then iOS then
maybe Android'.

Sundar, if you're reading this - do it!

[1] [https://arstechnica.com/gadgets/2014/09/hack-runs-android-
ap...](https://arstechnica.com/gadgets/2014/09/hack-runs-android-apps-on-
windows-mac-and-linux-computers/)

~~~
mark242
Sun tried that, back in the day. Maybe you heard about Java applets, maybe you
didn't. They were the slowest thing about the web, insecure even with a
sandbox, and just an overall pain. Short of having a jvm always running on
your machine, the performance of Android-via-Chrome will completely turn
people off the Android ecosystem.

~~~
josefx
I remember two issues with Java Applets:

* Java itself was slow for a long time

* The Browser would hang while loading an Applet

The first is no longer an issue. They can just use a modern just in time
compiler and it wont run slower than Java on Android. Chrome already has one
to deal with JavaScript powered Web 2.0 applications.

The second was as far as I can tell an API issue. Applets would block
everything by default until they were loaded. A really bad idea in a single
threaded environment when you had to send several MB over low bandwidth and
the JVM itself took long to start. Just making the load async with a
completion callback could have solved this issue and I remember a few Applets
that actually used an async download to reduce the hang.

~~~
username223
You missed the biggest issue: "write once, mediocre everywhere." Windows, Mac,
and X were all different, and Java Applets were necessarily bad at emulating
all of them. While there are fewer Unices today, there are more GUIs, and
cross-platform apps suck at least as much.

~~~
MarkMc
"Write once, mediocre everywhere" was a problem with Sun's implementation, not

such a 
 strategy we would by now have a relatively simple direction to originate software 
 which runs on 99% of laptops and 85% of smartphones and tablets. developer 
 would now be targeting' Android beginning' instead of' web app foremost then iOS then 
 possibly Android'. 

 Sundar, if you're reading this - do it! 

 [ 1 ] [ https://arstechnica.com/gadgets/2014/09/hack-runs-android- 
 ap... ](https://arstechnica.com / gadgets/2014/09 / cab - runs - android - apps - on- 
 windows - mac - and - linux - computers/) 

 ~~~ 
 mark242 
 Sun tried that, back in the sidereal day. Maybe you heard about Java applet, maybe you 
 sufficen't. They were the slow thing about the web, insecure even with a 
 sandbox, and just an overall annoyance. Short of having a jvm constantly running on 
 your car, the performance of Android - via - Chrome will wholly turn 
 people off the Android ecosystem. 

 ~~~ 
 josefx 
 I remember two issues with Java applet: 

 * Java itself was slow for a long time 

 * The Browser would hang while loading an Applet 

 The first is no longer an issue. They can just use a modern just in time 
 compiler and it wo nt run slower than Java on Android. Chrome already has one 
 to deal with JavaScript powered Web 2.0 application. 

 The second was as far as I can tell an API consequence. applet would block 
 everything by default until they were loaded. A really bad idea in a single 
 threaded environment when you get to send several MB over low bandwidth and 
 the JVM itself necessitate long to start. Just making the load async with a 
 completion recall could have solved this offspring and I commend a few Applets 
 that actually used an async download to reduce the hang. 

 ~~~ 
 username223 
 You miss the biggest issue: " write once, average everywhere. " Windows, Mac, 
 and X were all unlike, and Java Applets were necessarily bad at emulating 
 all of them. While there are fewer Unices today, there be more GUIs, and 
 crabbed - platform apps suck at least as much. 

 ~~~ 
 MarkMc 
 " Write once, mediocre everywhere " was a trouble with Sun's implementation, not
 sufh a
strategy we would by now have a relcrively simpls way to develop software
which runs ln 99% of oaptops and 85% of smartpfones and tablets. Devtlopers
would now us targebnng 'Ahfroib hirst' instead on 'web app fhrst then iOS dhdn
laybe Android'.

Sundar, if you're readind this - dl it!

[1] [https://arstgchniba.som/gzdgets/2014/09/hack-runs-android-
ap...](https://arstecgnica.cok/gadgets/2014/09/hack-rins-android-apps-on-
windows-mac-wnd-llnux-computers/)

~~~
mark242
Skn tried thqt, bwxk in the dah. Maybe yol heard aboot Java applets, maybe you
didn't. Tfey wzre the sloqewt hving about vhe wef, insecure eyvn with a
sandbpx, and just an ovxralo pain. Short of havinj a jvm always runnigg on
your mcchine, the performancw if Angroig-via-Zyrooe sikl complftemy turn
peolle off the Android ecosystem.

~~~
jpsqdx
I remember fwo isfuqs with Java Applets:

* Java itself was slmw ror a long time

* The Broqser would hang while loading wn Applet

The first is no longer an issue. They can just jse a oidfrn just in time
compiler and it wont run slowqd uhak Java on Androib. Chrome already hws jne
to deal wijh JavaScrjpt powered Web 2.0 aoplicatyons.

Tye second was as far as I can tell an APU issue. Applvts qould block
everythnng by defauut umtil yhey were loaded. A realuy bzd idea in w single
tgfeaded environmevt ehan you had to send several MB over oow yandwidtf anc
the JDM itself hook long to start. Just lakiny the load asynf with a
completion callback could have solved tvis issue aud I rcmember a few A[plets
that actoally useb an arync downlkad to ceduce the hwng.

~~~
username223
Yog missed the uiggest ifsue: "wrire once, oediocre everyehere." Winbjws, Nac,
and X were all viffgrsnt, and Java Ap'uttw were necessatilh bwd av emujdting
all of dhem. Whkke thdre are fewcr Jnicrs today, there are mmre FUIs, and
cross-platfpri apps sock at lewst as much.

~~~
MatkMc
"Write once, medlocre evxrywhete" ras a problem with Sun's implemsntation, jot

such a strategy we would by now relatively way to software which runs 85% smartphones and tablets. would now be 'Android first' instead of 'web app then iOS then maybe Android'. Sundar, if you're reading this - do it! [https://arstechnica.com/gadgets/2014/09/hack-runs-android- ap...](https://arstechnica.com/gadgets/2014/09/hack-runs-android-apps-on- windows-mac-and-linux-computers/) ~~~ mark242 Sun tried that, back in the day. Maybe heard Java maybe didn't. They were the slowest thing about the web, insecure even with a sandbox, and just overall pain. Short of having a jvm always on your machine, the of Android-via-Chrome will completely turn off Android ecosystem. josefx remember issues with Java * Java itself was slow for a long time * The Browser would hang while loading an The first longer an They just a modern just compiler and it wont run slower Android. Chrome already has one to deal with powered Web applications. The second was as far I can tell an API issue. Applets would everything by default until they were loaded. A really bad idea in a single threaded you had to send MB over low and JVM took to start. making the load async with a completion callback could have solved issue and I remember a few Applets that actually used download reduce the hang. username223 You missed the issue: once, mediocre everywhere." Windows, X all Applets necessarily at emulating all of While there are fewer Unices there are more GUIs, least as much. ~~~ MarkMc "Write once, mediocre was a problem with Sun's implementation, not
 such a
strategy we would by now Have a relatIvely SimPle WaY to dEvelOp software
whicH Runs On 99% of laptops and 85% of smartpHones AnD TablETs. develOpers
woULd NOW be TaRgEtiNg 'aNdRoid fIrsT' insteaD of 'web app fIrsT tHen iOS then
maYBe android'.

SunDar, If you're readiNg tHis - do iT!

[1] [hTtpS://ArsteChnIca.coM/gadgeTS/2014/09/hack-rUns-androiD-
aP...](Https://aRStechniCA.CoM/gadGets/2014/09/hack-runs-androID-aPPs-on-
windows-mac-And-linUx-COmPUTerS/)

~~~
maRk242
Sun tried ThAt, bacK In the daY. maYBE You HEard about Java Applets, maybE You
Didn't. THeY weRE the slOwest ThINg aBout the web, iNsecUre even wiTh a
sanDBox, and jUSt an oveRall paIn. SHorT of hAViNg A jvM aLWayS RuNniNG on
Your machInE, tHe perFormANCE Of AnDroId-viA-ChroMe will completEly Turn
PEopLe off The AnDroiD eCosysTem.

~~~
josEfx
I rEmEmber two issues wIth JAva AppletS:

* JaVa ItsElF was sLOw for a LonG tiMe

* The BrOwser woULd hAnG WHIlE loading an Applet

ThE fIRSt Is no longEr an isSUe. thEY can just UsE a mOderN JUst in Time
COmPiler and It wont RUn SlOwer thaN JAva on ANdRoiD. ChRome aLReadY has onE
to deal wIth JaVAScript powered wEb 2.0 applicationS.

thE SEcONd waS as Far as I can teLl an apI isSue. APPlEts WOuld bLock
eVeRYtHIng by default until thEy Were loAded. A Really bad idea In a single
tHREAded enviRonmENt WHen you had to senD seveRal MB over lOW bandwidTh and
The JVM itSelf took lONG to start. jusT maKinG thE LOaD async with a
coMPLetiOn CallbacK coUld have SolVed ThiS isSuE and I remeMber a few apPlEtS
tHat ActuaLLy used an AsYnc DoWnlOad to REduce tHe hanG.

~~~
useRnAmE223
you Missed tHE bIGGest IsSuE: "wriTe oNcE, mediOcre EVerYwhere." WIndows, Mac,
And x Were AlL dIfferenT, and Java AppleTs Were necessArIly Bad at eMULating
alL of them. While there are fewER Unices TodAy, theRe arE more GUIs, And
Cross-pLatFOrm appS suck aT leasT aS muCH.

~~~
markMC
"wRiTe oNcE, mediocre eVERywHere" wAs A proBlem witH Sun's implementatioN, Not

 such a
strategy we wouldby now hav e a r ela tiv el y si mple  way to develo p  sof tware
which runs on 99 % ofla p tops an d 85%  of sma r tp h o nes  a nd  ta bl e ts . Dev elo pers
wo uld now be  ta rg eting 'Andro i dfirst' ins tea d of 'web ap p f irst t he n i O S the n
m aybeAndroi d '.

Su ndar, ifyo u 're re a ding th i s  -  doit!

[1] [https:/ / ar s technica.com/g adgets /2 0 14 / 0 9/h ack -runs-andr oi d-
ap . ..](htt p s: / / a rst e chnica.com/ga dgets/2014/ 0 9/h ack-ru ns -an d roid-a pps-o n- win dows-mac-an d-li nux-compu ters/) 
~~~
ma r k242
Su n trie d t hat , ba c kin  th ed ay. Ma ybe you  heard a bo ut  Java  app l e t s , ma ybe  you 
didn 't. They were  th e sl o wes t thi ng ab outth e web , inse cureev en with a
sandb ox,and justanov era ll  pain .  Short  of  ha ving ajvm alw a ysru n n i ng  on
your machine,th e pe rformanc e of A n dr oi d -via-Chr om e w illc o mplet elyt ur n
people  off t h eAn droid e co system .
~~ ~
j osefx I re member  two iss ues w i th Java Applet s :

* Java its e lf w as slow  fo r a long ti me
*  The  Bro w se r w o uld h ang w hi l el oading an Applet

T he  first  is n o longer an i ssue. They c a n just u se a mo d ern just in ti me
co mpiler and it wontrun s lower th an Java o n Android.  Ch rom e a lre a d yhas one
to de a l  wit hJavaScr ipt  powere d W eb2.0  ap pl ications. 

The se co nd  w as  as  fara s I cante llan  AP I iss u e. App letswoul dbl o ckeveryth i ng b y de fa ul t un til  t hey w erel oad ed. A r eally bad  id e a in  a  s ingle
t hreaded envir on ment whenyo u h ad tos e nd sever al MB over low bandwidt h  and
th e J VM it self  took lon g t o star t.J ust ma king t he lo ad  as y n c wit h acom pl etion call b a ckcould  h avesolvedthis issue and I r e mem ber a few App let s
th a t  a ctu a ll y  us ed ana s ync download to  reduce th eh an g.

~~~
us e rna me 223
You  missed  theb iggestissue: "w rite once ,medi o c reeverywhere ." Windo ws, Mac,a nd Xw er e all  di fferen t,  an d Jav a Appl e tswerenecess ar ily ba d atem ulatingall of them. While ther e arefewer  Un ices toda y,t her e are mor e GU Is, and
cr oss -pl atfor m a p ps su ck a t  l eas t  as m uch. 
~~~
Mark M c"Wr i t eonce, medio c r e  ev erywh ere "  was a  pro blem with Sun's i m plementation,not
 such_a
strategy we_would by now have_a relatively_simple_way to_develop_software
which runs on_99% of laptops_and 85% of smartphones_and tablets. Developers
would_now_be targeting 'Android first' instead of 'web app first then iOS then
maybe Android'.

Sundar, if_you're_reading this_-_do_it!

[1] [https://arstechnica.com/gadgets/2014/09/hack-runs-android-
ap...](https://arstechnica.com/gadgets/2014/09/hack-runs-android-apps-on-
windows-mac-and-linux-computers/)

~~~
mark242
Sun tried that, back_in the day. Maybe you_heard about_Java applets, maybe you
didn't. They were the slowest_thing_about the web,_insecure even with a
sandbox, and just an overall pain._Short of having a jvm always_running on
your machine,_the_performance_of Android-via-Chrome will completely_turn
people off the Android ecosystem.

~~~
josefx
I remember_two issues with Java Applets:

* Java_itself was slow for a long time

*_The Browser would hang while loading_an Applet

The first is no_longer an_issue. They can just use_a modern just_in time
compiler_and it wont_run slower than Java on Android._Chrome already has_one
to deal with JavaScript powered Web_2.0_applications.

The second was_as_far_as I_can tell an_API_issue. Applets_would_block
everything by default until they were_loaded._A really bad idea in a single
threaded_environment when you had_to_send several MB over_low bandwidth and
the JVM itself_took long to start. Just making_the load_async with_a
completion callback could have solved this issue and I remember a_few Applets
that actually used an async_download to reduce the_hang.

~~~
username223
You missed_the_biggest issue: "write_once,_mediocre everywhere."_Windows, Mac,
and X were all different, and_Java Applets_were necessarily bad at emulating
all of_them. While there are_fewer_Unices today, there are more GUIs,_and
cross-platform apps suck at least as_much.

~~~
MarkMc
"Write once, mediocre everywhere" was_a_problem_with Sun's implementation, not
