disable-webassembly VS j2cl

Just in case those who prefer not to allow Java need this, here's some info about disabling WASM in various browsers.

https://github.com/stevespringett/disable-webassembly

Dear All, I was reading https://github.com/stevespringett/disable-webassembly and was wondering if WASM can be disabled in qutebrowser or if it already is disabled when content.javascript.enabled is set to false?

For Chrome you can also run:

chrome --js-flags=--noexpose_wasm

More info for other browsers and platforms:

https://github.com/stevespringett/disable-webassembly

There are many open source projects like, https://github.com/google/j2cl/tree/master/samples/wasm

This was a grand stroll down memory lane; having hacked Java since JDK 1.0, I've seen a lot of improvement.

An idle thought: he favors server-side rendering whereas the javascripts seem to favor client-side rendering. Along the way doing servlets, there came to be "view first" rendering, where you use serverside to paint a minimal page which, itself, uses ajax calls to fill in the blanks. I used that a lot.

It's true also that I migrated from servlets to node. But, in all of this, clojurescript erupted on the scene. And, for me, that's where the piece gets interesting: he introduces us to a java to clojurescript transpiler and tells us it was used to craft the google app suite. Now it's time to go play [1]

[1] https://github.com/google/j2cl

So it looks like we have pretty much everything except for the most important part: three.js that we can use from Java. And it’s a little bit of a complex part. To interop with JavaScript we should use J2CL JsInterop API, but there is a little problem: Closure Compiler must be able to recognize types of (most of the) three.js objects. Here we have two options:

You mean https://github.com/google/j2cl ? You understand though that these are trying to solve multiplatform in very different ways. I don't think this approach has a bright future.

Have you seen J2CL? https://github.com/google/j2cl