3 ms·
On the "Ruby Kaigi" presentation (http://www.atdot.net/~ko1/activities/2015_RubyKaigi2015.pdf http://www.atdot.net/~ko1/activities/2015_RubyKaigi2015.pdf), Koic
by pantulis 11y ago
On the "Ruby Kaigi" presentation (http://www.atdot.net/~ko1/activities/2015_RubyKaigi2015.pdf http://www.atdot.net/~ko1/activities/2015_RubyKaigi2015.pdf), Koichi Sasada states that Matz doesn't like the automatic compilation of source files a la Python, which automatically generates .pyc files.
Why is this? I understand the inconvenience of having lots of compiled files in your deployment structure but I guess having a static compile phase would be worse. Any opinions on this?
- chrisseaton 11y agoI think Rubinius used to do it the python way (.rbc files in the same directory) but I think it stopped (not the authority on that so may be wrong). I think if you could do it transparently as a cache, and out of sight and synchronised properly it would be fine, but writing files everywhere is not ideal. Imagine two users running the same files but with different configurations in the same directory at the same time. It's just a mess waiting to happen. Don't know if that's Rubinius' or Matz's problem with it though.
- YorickPeterse 11y agoRubinius stores the bytecode either in $PWD/.rbx or $HOME/.rbx depending on which of the two exists. By default $HOME/.rbx is used. EDIT: I meant the default being $HOME/.rbx, not $PWD/.rbx