3 ms·
>This got me thinking that it would be interesting to see a kind of “YJIT standard library” emerge, where core ruby functionality run in C could be swapped out
by ksec 2y ago
>This got me thinking that it would be interesting to see a kind of “YJIT standard library” emerge, where core ruby functionality run in C could be swapped out for Ruby implementations for use by people using YJIT.
This actually makes me feel sad because it reminded me of Chris Seaton. The idea isn't new and Chris has been promoting it during his time working on TruffleRuby. I think the idea goes back even further to Rubinius.
It is also nice to see TruffleRuby being very fast and YJIT still has lots of headroom to grow. I remember one obstacle with it running rails was memory usage. I wonder if that is still the case.
- Asmod4n 2y agoOne of the amazing things truffle ruby does is handle c extensions like ruby code, meaning C is interpreted and not compiled in a traditional sense. This makes way for jitting c code to make it way faster than the author has written it.
- pantulis 2y agoAmazing indeed!
- deleted 2y ago[deleted]
- 0x457 2y agoYup, Rubinius was probably the most widely known implementation of Ruby's standard library in Ruby. Too bad it was slower than MRI.
- e12e 2y agoI thought maybe mruby had a mostly ruby stdlib - but I guess it's c ported over from mri?
- Lio 2y agoI think jRuby takes a similar approach. It’s possible to write gems which will use underlying C on MRI or Java when running on jRuby. It would be interesting to know if a “pure” would also help jRuby too.