Bringing the web up to speed with WebAssembly

Re:Bringing the web up to speed with WebAssembly by marcosdumay on Friday September 22, 2017 @01:39PM (#15314148)

HTML is also much a more convenient encoding for content than writing on the canvas. It's fully declarative¹ and everything.

Yet, plenty of people already prefer to send you a black page and manually write everything on the DOM's document. I certainly do not understand them, but they are way too common.

1 - You just write your content, and it's there. There isn't more declarative than that.

[ Parent | on HN ]

Re:Bringing the web up to speed with WebAssembly by goatlover on Friday September 22, 2017 @06:45PM (#15316596)

HTML isn't great for application code. That's the issue, and anyone targeting WASM and canvas would be looking to recreate desktop apps on the web, not traditional websites.

[ Parent | on HN ]

Re:Bringing the web up to speed with WebAssembly by marcosdumay on Friday September 22, 2017 @10:47PM (#15317770)

Yes, it's bad for applications. But that does not explain why people send their text based pages as javascript.

[ Parent | on HN ]

Re:Bringing the web up to speed with WebAssembly by krapp on Saturday September 23, 2017 @08:14AM (#15319392)

> But that does not explain why people send their text based pages as javascript.

Probably because they're using front-end javascript frameworks which do that, and because they were taught that this is the best and most efficient way to render anything on the web. No one wants to make a special case for text because it seems inelegant.

[ Parent | on HN ]

Re:Bringing the web up to speed with WebAssembly by goatlover on Saturday September 23, 2017 @06:28PM (#15322123)

But it's not the best and most efficient way to render everything. If you have a mostly static site, you don't need the front-end framework.

[ Parent | on HN ]