Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Yeah I hear you, but I think the pros outweigh the cons. For one thing, I have never run a stateful V8 container, which makes scaling trivial (if the performance issue is actually just V8 and not some greater architectural defect). V8 performance issues can be overcome, and it’s not like the JVM is trivial to tune. Every workload has a learning curve.


I hardly ever had to tune JVM, and would never put the single threaded V8, with a dynamic language, under similar workloads.


Consuming more and more energy to do the same computation isn't environmentally friendly either. Just because you can scale by throwing more CPUs at the problem doesn't mean we should.


Assuming problems are worth the energy usage in the first place :)

How many Java apps do you think are out there that are not even worth the energy that they're using to run? How many absolutely asinine startups selling DRM-controlled juicers or internet connected water bottles or NFTs?

I'm not saying that every project that runs on Node or Python or whatever is worth the extra energy it uses, but this is kind of a silly argument to make with the kind of stuff coming out of the tech industry these days.


The JVM is actually the most “eco-friendly” out of the high level language platforms.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: