3 ms·
Hello world and hobby projects are not the target for the JVM. It may take a good chunk of RAM to fire it up at all but you can serve far more clients in that s
by cageface 15y ago
Hello world and hobby projects are not the target for the JVM. It may take a good chunk of RAM to fire it up at all but you can serve far more clients in that same chunk than you could with the number of Ruby processes, for example, you could run in the same memory. Look at how much more performance Lift/Scala can squeeze out of the same box than Rails.
- jshen 15y agoThis is certainly true when you have to scale at some high level, but I think that level is a lot higher than most people realize. I worked at yellowpages.com for a while and we were serving a large amount of traffic (the local ads on bing are from yellowpages) with native ruby. The JVM may have been a better option at that scale, but the vast majority of sites won't reach that scale. And ruby handled it just fine. The actual search logic was run on the JVM though.
- cageface 15y agoSure, but the point is that the JVM makes you pay that memory cost up-front, so it looks a lot more resource-heavy than it really is, whereas the scaling cost of things like PHP and Ruby is back-loaded. People worry about scaling too much in general, IMO, but you'll actually get more mileage out of your hardware with something Clojure or Scala than you will with Python/PHP/Ruby/Perl.