3 ms·
"Note that we are not using Ruby 1.9.x due to its reliance on threads, which cannot be ported directly using Emscripten." - https://github.com/replit/emscripted
by DanWaterworth 13y ago
"Note that we are not using Ruby 1.9.x due to its reliance on threads, which cannot be ported directly using Emscripten." - https://github.com/replit/emscripted-ruby https://github.com/replit/emscripted-ruby
- akanet 13y agoHey, I made CoderPad. I'm looking at replacements for emscripted-ruby currently. Interesting candidates currently include doing it all server side, and using mruby compiled via emscripten. Unfortunately mruby's greatest current shortfall is lack of `require` support, which may or may not be a dealbreaker. What do you think?
- judofyr 13y agomruby is a completely different beast from Ruby. Consider it a different language, not a different version. What about using JRuby on the server-side?
- akanet 13y agoI've thought about it. The daunting bits are the trickiness around how long the session should live. You'd like the repl's variables to persist between commands, etc, but at the same time letting an arbitrary code session live for a long time on your server is probably not the safest thing. If you have any resources on the topic, I would love to look at them.
- DanWaterworth 13y agoI think the emscripten threads problem will eventually get fixed. In the mean time, I don't think there's a huge problem with using 1.8.7, but you might be able to improve it using the backports gem [1]. [1] https://github.com/marcandre/backports https://github.com/marcandre/backports