News for hackers. Stuff that matters.
Re:Why WebAssembly Is Faster Than Asm.js by flukus on Thursday March 16, 2017 @01:36AM (#13882790)
Yes they were slow and clunky, but they ran on computers with 100Mhz processors and 8/16MB of RAM. I doubt you could load a chrome tab on that.

> had weird clunky UIs that were out of place in the host OS and the browser

Just like web apps, the may be prettier, but they look just as out of plus with custom widgets everywhere and complete disregard for the desktop theme. Hell, for some reason chrome added that shitty task bar color attribute that allows a web page to alter the desktop (well mobile top) theme.

Re:Why WebAssembly Is Faster Than Asm.js by beagle3 on Thursday March 16, 2017 @02:34AM (#13883011)
Yes, but the competition at the time was HTML (slowly getting interactive with time, and mostly ugly, but fast and dependable), and Flash -- and Flash was way faster, way more compact, and way more prevalent than Java.

So, Java wasn't ahead of its time, and it was much much worse than Flash (which, despite numerous efforts to kill it, is still alive, unlike Java Applets which have essentially been dead for years).

Re:Why WebAssembly Is Faster Than Asm.js by flukus on Thursday March 16, 2017 @02:46AM (#13883057)
I don't think flash was much better at anything interactive, or at least animated. On the same hardware as above I remember "frog in a blender" could render well south of 1FPS, on a 486/686 (outdated but still in common use) it was more like 0.1FPS.

Too be fair though, it's a hard comparison, applets were generally apps while flash was fancy graphics.