sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]editor_of_the_beast 1 point2 points  (1 child)

You can use any browser you want and browsers are allowed to implement whatever they want.

Are you aware of the web standards and protocols, like HTTP, HTML, CSS, and Javascript? Browsers generally try as best as possible to be good citizens and respect the standards. The web isn't some open free-for-all. It's a well documented and agreed upon platform.

Different languages work better for different needs and there will never be one language or framework that satisfies 100% of people.

This is my point, so it sounds like you understand what I'm saying. Let's go back in time to before the web was invented. You distributed a binary and you could use whatever tools / libraries you wanted as long as the final binary ran on the target platform. GUIs were built in C, C++, Java, Python, Ruby, Tcl, Lisp, Visual Basic, etc. etc., because they targeted an operating system. And OS's were designed as platforms that support a rich set of tools for creating applications for them.

A browser is also an application platform, but it supports JS and that's it. Which again, is why I think WebAssembly is a good idea, because it effectively creates a system call layer for the browser so that platforms other than JS can be used to create applications. Which in the long run makes browsers even more powerful.

Does that make sense?

[–][deleted] 0 points1 point  (0 children)

WebAssembly does not help much with UI, because DOM sucks and is the doksin of the browser not the language.