These are chat archives for opal/opal
hamstergem doesn't run on Opal. :-( I fixed the syntax errors it generated, but it turns out it also depends on
concurrent-ruby, which depends on a native (C/Java) extension.
grand_centralas my data store), so I put a lot of effort into making it work, but
concurrent-rubyisn't something Opal can run.
@viebel Some gems that aren't Opal-aware can be used directly by calling
Opal.use_gem(gem_name) on the server side. This adds their require paths to Opal's list of require paths. Then you can
require them in your client-side app as normal Ruby libraries.
Unfortunately, for it to work, those gems can't use anything Opal doesn't support, like threads, files (in the browser), native extensions, POSIX stuff (
Net::HTTP, and other things that can't be done in the browser (at least, not the way Ruby does it).