News for hackers. Stuff that matters.
Re:Introduction to WebAssembly: why should we care? by loup-vaillant on Tuesday December 19, 2017 @08:26AM (#15960013)
Problem is, adding to the bl… sorry, richness, doesn't remove the old cruft.

How about having an application platform that would be just an application platform? No HTML, no CSS, no built in multimedia. Just a VM, a viewport, audio, and inputs (and local storage if the user allows it).

Re:Introduction to WebAssembly: why should we care? by olavk on Tuesday December 19, 2017 @09:15AM (#15960306)
We already tried that - Java Applets. Silverligt was the same idea. And Flash I guess? All attempts failed in the marketplace. It turns out using higher level standards like HTML, CSS, URL's etc actually provide a a lot of value.
Re:Introduction to WebAssembly: why should we care? by niftich on Tuesday December 19, 2017 @09:51AM (#15960567)
Obligatory point that Flash didn't fail in the marketplace. Rather, it was wildly popular, so much so that Microsoft eventually felt the need to develop a comparable tech -- Silverlight.

Flash on the web faltered rapidly after many years of efforts by Mozilla, Apple, Opera, and associated individuals. They were looking to move the web 'forward' had a high-profile disagreement with W3C, so they started their own standard-setting collaboration to specify HTML5 and associated JS APIs. The blogosphere eagerly awaited the results, which promised to formally bring multimedia and rich interactivity to HTML, without having to use a vendor plugin.

When Apple announced that Flash won't be supported on the upcoming first iPhone, it was over. After a few years, when apps came to the iPhone, Adobe failed at marketing the fact that their Flash assets can be compiled into iPhone apps using Adobe AIR.

With existing Flash assets effectively relegated to desktop-only, it was only a matter of time before it was pushed out of the standard browser stack. Although later, both Microsoft and Google shipped Adobe's plugin (with better process isolation) together with the browser or the OS, and hooked into their respective auto-updaters, Flash was on its way out.

Re:Introduction to WebAssembly: why should we care? by loup-vaillant on Tuesday December 19, 2017 @10:41AM (#15960906)
Seconded. If Flash wasn't proprietary, it would still thrive. It could have displaced JavaScript itself.
Re:Introduction to WebAssembly: why should we care? by collyw on Tuesday December 19, 2017 @01:54PM (#15962893)
There is an open source version Gnash. I installed it on a laptop a few years back and it ran fairly well, but a bit slow compared to the real Flash. Why do you think that didn't take off?

Edit: Looking at the wikipedia page I see one reason (though I am not convinced its the reason it didn't take off). https://en.wikipedia.org/wiki/Gnash_(software)#Adobe_Flash_P...

Re:Introduction to WebAssembly: why should we care? by loup-vaillant on Tuesday December 19, 2017 @03:45PM (#15964086)
It's not fully compatible. Of course it didn't take off. You want the default application to be free software.
Re:Introduction to WebAssembly: why should we care? by cm2187 on Tuesday December 19, 2017 @11:06AM (#15961137)
They didn't fail in the market, they were actually quite popular (maybe not java, but flash definitely). It is just that Apple killed them by not making them run on mobile. That's more of a case of a major player strong forcing the market.
Re:Introduction to WebAssembly: why should we care? by 2sk21 on Tuesday December 19, 2017 @09:34AM (#15960439)
I was going to say there same thing - this just seems like java Applets have been reinvented
Re:Introduction to WebAssembly: why should we care? by flohofwoe on Tuesday December 19, 2017 @08:38AM (#15960077)
I'm all for building from scratch a lean minimal runtime platform as you describe (that's what operating systems should be), also it should be "easy", take a minimal Linux kernel and add some thin APIs on top. But good luck turning this into a project that gains any traction.

Using the browser platform to bootstrap such a thing isn't such a bad idea in comparison... sooner than later we need to depreciate the ugly parts, like WebRTC, WebAudio and trim some fat here and there, but other platforms have their ugly parts as well (look at the mess that is Android).

Re:Introduction to WebAssembly: why should we care? by JustSomeNobody on Tuesday December 19, 2017 @08:47AM (#15960129)
Exactly. Leave https alone and use it for hypertext. Have another protocol (vmtps?) that is used for apps. Browsers could support both.
Re:Introduction to WebAssembly: why should we care? by 0xfeba on Tuesday December 19, 2017 @08:54AM (#15960171)
Agreed. It seems we are just piling on one thing after another. Surely we can start fresh with a better eye toward the future.

TLS + HTTP Methods/WebSockets + HTML + CSS + JavaScript + JS frameworks

Plus all the server side stuff. It's all a mess.

Re:Introduction to WebAssembly: why should we care? by osrec on Tuesday December 19, 2017 @09:14AM (#15960299)
But that's also the beauty of it. Within the browser we can support the old and the new without too much trouble.
Re:Introduction to WebAssembly: why should we care? by loup-vaillant on Tuesday December 19, 2017 @10:36AM (#15960871)
You need a browser in the first place. The standards are now so big that to write a modern, compliant browser, you need to be an international corporation.

A market with only 4 competitors (Microsoft, Google, Mozilla, Apple), is not a market. It's an oligarchy.