4 ms·

All the problems with the JVM have been written up to death, and many are easily inferable from surface-level background knowledge. If you don't know them, who'

• kaba0 3y ago
  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.
  • pie_flavor 3y ago
    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.
    • kaba0 3y ago
      > 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.