[dead]
Endive: A JVM native WebAssembly runtime
21–30 of 44 posts
Re: Endive: A JVM native WebAssembly runtime
#22Why not resurrect applets? We had this webasm thing 30 years ago.
Re: Endive: A JVM native WebAssembly runtime
#23Why not resurrect applets? We had this webasm thing 30 years ago.
The two main points are that wasm is entirely sandboxed and that it's designed to be streamed, and to start up very quickly. The official Java youtube channel coincidentally posted this two days ago - https://www.youtube.com/watch?v=fy0KyGLrbJo - which includes some interesting details.
Re: Endive: A JVM native WebAssembly runtime
#24I guess we can come full circle and eventualy port it to Android Java.
[deleted]
Re: Endive: A JVM native WebAssembly runtime
#25Projects like this would be significantly funner and easier to make in Jdk25+(well technically 24+) because of the new Java classfile/bytecode API. It looks like Endive uses OW2 ASM, probably because this supports back to Jdk11. The new jdk API has a minimum target of Jdk17. OW2 ASM is significantly harder to use IMHO though. What got me into this is I just finished a major release of Petrify ( https://github.com/exa…
bytecode manipulation has been a thing ever since late 90s and early 2000s (e.g. BCEL, Jan, 2001), along with byte code decompilation.
Generally one must understand how bytecode signatures, all flavors of invoke, and constant pool work. After that using visor pattern or 'functional' alike stuff makes no difference whatsoever.
I have used (still using) bytecode manipulation along with custom classloaders as part of my job (albeit not on daily basis any longer). Personally, I don't consider objectweb asm hard to use in any way. and java's class file won't be funnier - perhaps it was the very project I'd not pick bcel, though.
Re: Endive: A JVM native WebAssembly runtime
#26Shameless plug: we solved the opposite problem, running any Java application in the browser via WebAssembly: https://labs.leaningtech.com/blog/cheerpj-4.3 And yes, it does run Minecraft as well :-) https://browsercraft.cheerpj.com/
But can it run Endive?
Re: Endive: A JVM native WebAssembly runtime
#27Shameless plug: we solved the opposite problem, running any Java application in the browser via WebAssembly: https://labs.leaningtech.com/blog/cheerpj-4.3 And yes, it does run Minecraft as well :-) https://browsercraft.cheerpj.com/
But can it run Endive?
I wonder what the performance loss is for each level?
Re: Endive: A JVM native WebAssembly runtime
#28Shameless plug: we solved the opposite problem, running any Java application in the browser via WebAssembly: https://labs.leaningtech.com/blog/cheerpj-4.3 And yes, it does run Minecraft as well :-) https://browsercraft.cheerpj.com/
But can it run Endive?
Not something I tried myself, but conceptually if it's Java it should work.
CheerpJ Just-In-Time compiles Java bytecode at runtime, so it makes no difference if the classes come from JAR files or are dynamically generated.
Re: Endive: A JVM native WebAssembly runtime
#29Shameless plug: we solved the opposite problem, running any Java application in the browser via WebAssembly: https://labs.leaningtech.com/blog/cheerpj-4.3 And yes, it does run Minecraft as well :-) https://browsercraft.cheerpj.com/
Mmhh should work for clojure as well then. I should try this.
Re: Endive: A JVM native WebAssembly runtime
#30Earlier quoted context omitted.
The component model is still in phase 1 (standardization is phase 5) and the Bytecode Alliance are its sponsors and the ones pushing it into the ecosystem with wasmtime.
I don't think you're fully saying what you want to here. Are you saying this is bad? The point of a component model is interoperability, so the more runtimes that support it the better.
I am saying as far as anyone other that the Bytecode Alliance is concerned it is custom API for Bytecode Alliance projects.