News for hackers. Stuff that matters.
Re:CheerpJ Applet Viewer – Runs Java applets without a local... by exabrial on Monday June 19, 2017 @03:08PM (#14589503)
Applets were/are a terrible idea, but they started us down a path of improvement that's lead us to where we're at today with browser technology.

I really wish we had a powerful virtual machine like the JVM in our browsers though... Client-side frameworks are making the web much slower and are eating battery life.

Web assembly is a step in the right direction, but the "not invented here syndrome" makes my head hurt.

Re:CheerpJ Applet Viewer – Runs Java applets without a local... by hackcasual on Monday June 19, 2017 @03:56PM (#14589920)
Running the JVM in the browser had a horrible security track record. WebAssembly operates within the well defined parameters of the pretty decent for security Javascript sandbox. I'm not sure NIH is particularly fair, especially considering the relatively quick wide spread adoption WASM has seen.
Re:CheerpJ Applet Viewer – Runs Java applets without a local... by exabrial on Monday June 19, 2017 @09:51PM (#14591694)
I disagree. The Java -can- library has a terrible record and allows for all kinds of terrible things. The JVM itself is a memory model.
Re:CheerpJ Applet Viewer – Runs Java applets without a local... by flohofwoe on Monday June 19, 2017 @03:49PM (#14589862)
What are features of the Javascript VM in current browsers that make it less powerful than the Java VM?
Re:CheerpJ Applet Viewer – Runs Java applets without a local... by ianopolous on Monday June 19, 2017 @07:39PM (#14591214)
Single threaded, no 64 bit integers.
Re:CheerpJ Applet Viewer – Runs Java applets without a local... by exabrial on Monday June 19, 2017 @09:50PM (#14591691)
Also, dynamically typed (a feature rarely used and very costly)
Re:CheerpJ Applet Viewer – Runs Java applets without a local... by copperx on Tuesday June 20, 2017 @04:08PM (#14598111)
What do you mean by 'rarely used'?
Re:CheerpJ Applet Viewer – Runs Java applets without a local... by wbl on Monday June 19, 2017 @10:15PM (#14591752)
Firefox lags with GC due to a painful decision to permit C to point to JS directly.