|
|
|
|
|
by asdkhadsj
2578 days ago
|
|
And if Java managed to get a hold we'd be asking why this is better than Java (which doesn't exist with these features in this manner). That's the point. It's seemingly good, and available. Why the pushback? I don't get your (or anyones) objections. > If Chrome already had the current market share back then, we wouldn't be seeing such adoration, as if no one ever done it before. I think you misunderstand the adoration. It's not as if this has never been done before. It's that this isn't done now. What else can I use? Nothing. I remember 10 years ago dying for a way to run Python in the browser and having no reasonable options for general web. Even now, what other option do I have? ASM.js is the only thing that comes to mind, which has significant downsides. It feels like the dislike/complaints are pointed in the wrong direction. If you're upset that this isn't Java (not that you are), complain about why Java can't be used right now like WASM can. Complain that Java didn't manage to hold favor 10 years ago. |
|
10 years ago there were ways run Python in the browser. ActiveState used to have such plugin for example.
Why do you think there is a language attribute on the <script> tag?
And for some strange reason, the same ones that adore WASM, seem to only be aware of Java as bytecode format and nothing else.