Java in the browser! There is nothing new under the sun.
the Sun?
CheerpJ 3.0: a JVM replacement in HTML5 and WASM to run Java on modern browsers
71–80 of 179 posts
Re: CheerpJ 3.0: a JVM replacement in HTML5 and WASM to run Java on modern browsers
#72Related, if you like Java but want to create a modern, Lighthouse-ready web app, check out Flavour: https://flavour.sourceforge.io/
Re: CheerpJ 3.0: a JVM replacement in HTML5 and WASM to run Java on modern browsers
#73For anyone interested in the Kotlin side of things: Kotlin has a great compat with Kotlin/JS[0]. they also have Compose For Web which is more WASM based[1] though its marked as experimental [0]: https://kotlinlang.org/docs/js-overview.html [1]: https://github.com/Kotlin/kotlin-wasm-examples/tree/main/com...
Re: CheerpJ 3.0: a JVM replacement in HTML5 and WASM to run Java on modern browsers
#74With this and Ruffle, we will soon return to the days of Internet Explorer 6 but with 4k monitors! All we need now is to run ActiveX. I think BottledWine can run Windows executables in the browser, how hard would it be to simulate the ActiveX bindings?
Reminds me of "The fall and rise of JavaScript"
https://www.destroyallsoftware.com/talks/the-birth-and-death...
Re: CheerpJ 3.0: a JVM replacement in HTML5 and WASM to run Java on modern browsers
#75Earlier quoted context omitted.
WASM has memory, and any native code compiled to WASM will allocate on WASM memory. CheerpJ's runtime is written in C++, which when compiled to WASM knows how to allocate memory, so there's no reason why direct buffers won't work.
Direct ByteBuffers are used to interop with the underlying platform, particularly for the purpose of IO. I could be wrong, but I fail to see how 'WASM memory direct Buffers' will work in that scenario.
It seems to work fine:
https://javafiddle.leaningtech.com/#JYWwDg9gTgLgBAKwIYDckDoB...
Re: CheerpJ 3.0: a JVM replacement in HTML5 and WASM to run Java on modern browsers
#76Not bad at all.
Re: CheerpJ 3.0: a JVM replacement in HTML5 and WASM to run Java on modern browsers
#77If only we could get a new version of Java for the browser. Something more of a scripting language that is not compiled but interpreted. Could probably knock out a proof of concept in a week, might call it Javascript or something... In all seriousness, anything that spits out canvas for a simple textbox is completely misguided about what the web is.
I suspect the goal is a way to bring Java desktop applications into the browser without rewriting the application from scratch.
Personally, as a fan of Blazor, I thought this was going to be a Java-based analog of Blazor; or a modernized replacement for GWT.
(One flavor of Blazor compiles C# to WASM, and uses a C# templating engine to generate HTML.)
Re: CheerpJ 3.0: a JVM replacement in HTML5 and WASM to run Java on modern browsers
#78Re: CheerpJ 3.0: a JVM replacement in HTML5 and WASM to run Java on modern browsers
#79For anyone interested in the Kotlin side of things: Kotlin has a great compat with Kotlin/JS[0]. they also have Compose For Web which is more WASM based[1] though its marked as experimental [0]: https://kotlinlang.org/docs/js-overview.html [1]: https://github.com/Kotlin/kotlin-wasm-examples/tree/main/com...
Re: CheerpJ 3.0: a JVM replacement in HTML5 and WASM to run Java on modern browsers
#80This reminds me abit of java applets