11–20 of 160 posts
Let's hope exactly the other way around will happen. I would rather like to see better interop between different languages using wasm than wasm + js.
Earlier quoted context omitted.
What makes you say so? JavaScript in itself is not a bad language at all, and many programmers genuinely like it.
It's not a bad language in itself, no - it's just a waste of resources for the end-user, and in general it's being marketed to newcomers as the language they should learn by default - leading to a tonne of unoptimized sites and terrible applications using it. Then again, I suppose that's a fault of the type of programmers attracted to it than it is the language itself.
JavaScript isn't going anywhere. End-users don't care about executing "non optimal code."
Earlier quoted context omitted.
It's not a bad language in itself, no - it's just a waste of resources for the end-user, and in general it's being marketed to newcomers as the language they should learn by default - leading to a tonne of unoptimized sites and terrible applications using it. Then again, I suppose that's a fault of the type of programmers attracted to it than it is the language itself.
If you find yourself typing something about "the type of programmers attracted to X language" just delete what you wrote and move on. JavaScript isn't going anywhere. End-users don't care about executing "non optimal code."
I wouldn't say that's the right way to go about it or to think, especially in the case of JavaScript - more than ever, it's being taken up by people with no passion or desire to program solely so they can make what they think is going to be "The Next [WebCompany]," it's something that doesn't particularly have a parallel with any other language.
> End-users don't care about executing "non optimal code."
They do when the window freezes, or their Electron app locks and crashes, or when they suddenly can't have their browser running in the background while they're playing a video game.
Is this even a possibility?
I'm dreaming of seeing a wasm DOM api that directly binds to the browser's apis, without passing through javascript. Is this even a possibility?
[1] https://github.com/WebAssembly/host-bindings/blob/master/pro...
I'm dreaming of seeing a wasm DOM api that directly binds to the browser's apis, without passing through javascript. Is this even a possibility?
All of this tooling has been written to be forward-compatible with it, so whenever that lands, you can upgrade the tool and get a speed boost for free.
https://hackernoon.com/im-harvesting-credit-card-numbers-and...
It's great to see WASM taking off! In this context, see also Blazor, which runs C#/.NET code on WASM. https://github.com/aspnet/blazor
What’s the binary size like? One interesting thing about wasm is the difference between libraries and apps; Rust’s small binary size here can make it useful for this infrastructure work, but for languages that need to bring along the runtime, it’s much more complex. This is one reason why we’re pursuing stuff like wasm-pack. I’m glad to see more and more languages compiling to wasm though! Exciting times.
Now that they're using the Mono runtime it's significantly larger and it seems their main task now is finding ways to remove unused code from that runtime to get it back to reasonable.
Earlier quoted context omitted.
It's not a bad language in itself, no - it's just a waste of resources for the end-user, and in general it's being marketed to newcomers as the language they should learn by default - leading to a tonne of unoptimized sites and terrible applications using it. Then again, I suppose that's a fault of the type of programmers attracted to it than it is the language itself.
If you find yourself typing something about "the type of programmers attracted to X language" just delete what you wrote and move on. JavaScript isn't going anywhere. End-users don't care about executing "non optimal code."
I seem to remember Java Applets & Java "Web start" (or pretty much any browser "plug-in" runtime) causing a fair bit of grief for end-users...