News for hackers. Stuff that matters.
Re:Introduction to WebAssembly: why should we care? by sp332 on Tuesday December 19, 2017 @01:01PM (#15962235)
You can't download the entire internet. And loading a new web page every time you push a button is slow.
Re:Introduction to WebAssembly: why should we care? by TeMPOraL on Tuesday December 19, 2017 @01:21PM (#15962489)
Not in practice, given that in reality of this use case, JS code also does network requests, which tend to be at least as slow as downloading a HTML page.

That said, what I meant is modern JS enabled moving into the web things that should have stayed local. It's literally two step backwards (moving software into "the cloud") and one step forward (giving back some responsiveness through AJAX).

Re:Introduction to WebAssembly: why should we care? by adrianN on Wednesday December 20, 2017 @03:01AM (#15967844)
For some reason the web feels a lot faster when I disable JS...
Re:Introduction to WebAssembly: why should we care? by sp332 on Wednesday December 20, 2017 @06:50AM (#15968809)
I can make an application as fast as you want if it doesn't have to run correctly.
Re:Introduction to WebAssembly: why should we care? by TeMPOraL on Wednesday December 20, 2017 @07:07AM (#15968897)
Most of the time when you put JS on your page, what you're doing is breaking the thing that would - without JS - still correctly do what it's actually supposed to do.
Re:Introduction to WebAssembly: why should we care? by tskaiser on Wednesday December 20, 2017 @11:26AM (#15970973)
"Most of the time"? Citation needed.

While I generally agree with the sentiment of "do more by coding less", and minimalist user interfaces, there are plenty of cases where you throw a whole lot of functionality out the window by outright banning JS.