3 ms·
* Threads without GIL (which also requires an explicit memory model) * concurrency libraries * Garbage collectors that scale to hundreds of gigabytes worth heap
by the8472 13y ago
* Threads without GIL (which also requires an explicit memory model)
* concurrency libraries
* Garbage collectors that scale to hundreds of gigabytes worth heap, are parallel and concurrent
* JIT that performs within a small factor of C code
* Tooling support, especially profilers and debuggers are lousy and frequently break in my experience
* bytecode weaving/AST transforms at runtime. The whole refinements thing could have been done more cleanly with callsite and method entry/exit hooking
Talking about MRI here. I know rubinius and JRuby exist and offer some of those features
- aaronblohowiak 13y agoThe creation/creators of Java are not responsible for most of the things you listed. They are attributable to HotSpot, built by the fine folks that brought you the best-of-breed Smalltalk implementation half a decade after Java's release. HotSpot wasn't released until 1999. Prior to that Java did not have a JIT. Java used to be very slow compared to compiled code and HotSpot was a BIG DEAL when it was released in '99. GC that scales to hundreds of gb? Do you mean Azul, the proprietary and expensive JVM implementation?
- the8472 13y agoG1GC for dozens of GB, Azul (for now) for hundreds and in the future there'll be Shenandoah. You're right that those features provided by hotspot. But it is the reference implementation for the JVM after all. The point remains that the java ecosystem - which includes tooling like eclipse/netbeans/yourkit and JVM implementations - provides the things I've listed that I find lacking in ruby.
- djur 13y agoBut by the same measure, JRuby is part of the Ruby ecosystem.