Re:A world to win: WebAssembly for the rest of us
by kaba0 on Thursday August 17, 2023 @04:25PM
(#37167451)
The only problem with the JVM were politics. Safety? Should have been whitelisting, nothing inherent with the JVM. Performance? We had shitty hardware back then, the improvements there alone would have solved the issue (see: we use Javascript), but especially today, the JVM is more than fast enough for most workloads.
[ Parent
| on HN ]
Re:A world to win: WebAssembly for the rest of us
by pie_flavor on Thursday August 17, 2023 @06:15PM
(#37168922)
Fundamentally object-oriented, fundamentally garbage-collected, carries around a massive stdlib that's tightly integrated with precise functioning of the VM. And no, the performance concerns do not reduce to 'hardware'; the point is to eke out more performance than a high-level object-oriented garbage-collected system can muster. V8 is already on par with the JVM; if the JVM's performance was good enough for you, you'd just use JS.
Re:A world to win: WebAssembly for the rest of us
by kaba0 on Friday August 18, 2023 @02:49AM
(#37172121)
> Fundamentally object-oriented, fundamentally garbage-collected
And?
No one said that the performance concerns reduce to hardware — but at the Java Applets days it was most definitely the primary reason for their slowness. Since then, with the improvements of JITs, it became very fast.
> than a high-level object-oriented garbage-collected system can muster
That’s not a well-defined performance level and the ceiling changes each year.
And V8 has no real parallelism, so for many kind of workloads they are not drop-in replacements.