| ▲ | jakozaur 3 days ago | |||||||||||||||||||||||||||||||
Not sure if I get this: WASM lets you use any language in the browser, though it still works way better with languages without GC, such as Rust or a transpiling C engine. Java is unlikely to be the best choice. In the era of LLM assistants like Claude Code, any engineer can write frontend code using popular stacks like React and TypeScript. This use case is when those tools shine. | ||||||||||||||||||||||||||||||||
| ▲ | another_twist 3 days ago | parent [-] | |||||||||||||||||||||||||||||||
Java running in the browser is unlikely as typescript has largely tamed the mess of Javascript. Java requires a JVM and shipping an entire JVM so its runs atop another VM is kinda redundant. Except if JVM itself gets compiled and cached as a WASM bundle and Java compilers start accept WASM-JVM as a target. That will just be distraction tbh, Java has its strength in large scale systems and it should just focus on those rather than get caught up in Frontend's messy world. | ||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||