> * Real-World projects like Jekyll involve a lot more code, and JITing that code has a high start-up cost.
> * Real-world code like Jekyll or Rails is optimized for MRI Ruby, and many of those optimizations don’t help or actively hinder the JVM.
The title seems a bit provocative, though I guess if you were reading it from within the Jekyll community, it makes sense without further disclaimers, but otherwise the article seems fairly even-handed.
The threading stuff just seems like a special case of his second point.
> I think there are two reasons for this:
> * Real-World projects like Jekyll involve a lot more code, and JITing that code has a high start-up cost.
> * Real-world code like Jekyll or Rails is optimized for MRI Ruby, and many of those optimizations don’t help or actively hinder the JVM.
The title seems a bit provocative, though I guess if you were reading it from within the Jekyll community, it makes sense without further disclaimers, but otherwise the article seems fairly even-handed.
The threading stuff just seems like a special case of his second point.