4 ms·
Looks like eventually Wasm will become JVM and Firefox will become HotJava[0] :-P [0] https://en.wikipedia.org/wiki/HotJava https://en.wikipedia.org/wiki/HotJa
by badsectoracula 7y ago
Looks like eventually Wasm will become JVM and Firefox will become HotJava[0] :-P
[0] https://en.wikipedia.org/wiki/HotJava https://en.wikipedia.org/wiki/HotJava
- pjmlp 7y agoHowever given the progress rate of the proposals, I guess we will have to wait about 5 more years at very least.
- imtringued 7y agoEvery single day I am thinking how the JVM could actually be a platform that is worth using in many situations. That day may come but certainly not within the next decade. No matter how well you optimize your code the JVM will ruin it and make it slower and consume more memory than necessary. Of course none of this matters in a world where your internal dashboard with single digit user counts is set to use 4GB RAM just "to be sure".
- saagarjha 7y ago> No matter how well you optimize your code the JVM will ruin it and make it slower and consume more memory than necessary. On the contrary, I for one enjoy the benefits that the JVM brings to my poorly-optimized bytecode produced by javac.
- eitland 7y ago> No matter how well you optimize your code the JVM will ruin it and make it slower and consume more memory than necessary. Maybe you are really good at this. But for a good chunk of software engineers AFAIK compiling Java to bytecode and running it on the JVM easily outperforms their optimized code performance wise in most cases. JVM and JDK writers (and the same people on the Dotnet side) aren't dimwits and their efforts over the last two decades are being applied every time we compile and run software on their platforms.