4 ms·
Almost offtopic because not directly related to symbols performances in Ruby but, coincidence, I was reading a 2011 post from Rubinius site http://rubini.us/201
by pmontra 12y ago
Almost offtopic because not directly related to symbols performances in Ruby but, coincidence, I was reading a 2011 post from Rubinius site http://rubini.us/2011/02/17/rubinius-what-s-next/ http://rubini.us/2011/02/17/rubinius-what-s-next/ a couple of minutes before seeing this on HN.
At almost 50% of the post there is a code snippet that explains why Ruby method calls must be slower than the ones of statically typed languages. It also explains how Rubinius was addressing that 3 years ago.
Hopefully they'll optimize that in all language implementations.
- donpdonp 12y agoalso almost off topic but the lead Rubinius dev just posted a great writeup on rubinius 3.0 which could be a possible future of ruby in general. http://rubini.us/2014/11/12/rubinius-3-0-part-3-the-instructions/ http://rubini.us/2014/11/12/rubinius-3-0-part-3-the-instruct...
- pmontra 12y agoInteresting read. Thank you.