@fkchang Opal certainly needs more promotion. These days every second Ruby conf I visit has a talk on Crystal, but I’ve yet to see anyone besides you and @ryanstout talk about Opal. I aslo found a talk by @elia, but it was in Italian. :-)
Part of the problem may be brain-drain at this point -- many people that are keenly interested in heavy frontend dev have long jumped on the JS bandwagon, and people that are still really super into Ruby (and likely Rails) tend to be more backend focused. It's challenging to find folks in the client-side frame of mind that are gung-ho about coding in Ruby rather than something else.
@bbatsov I think its that the tools aren't there yet. Since most of the front-end tools are (currently) written in JS, they don't see the advantage of using opal. I think once we get more idiomatic ruby tools for the client side, people will see the benefit. That said, Volt seems to be getting lots of adoption. I think once its more feature complete it will ramp up pretty quickly.
@bbatsov I keep submitting proposals for opal, but only one has been accepted. I keep trying though
@jaredcwhite I think if we can show that browser based ruby is just ruby, more rubyist will adopt. I proposed a few talks where I basically tried to paint how when I code Ruby in the browser it's so much better than when I do JS, one thing I do instinctively is quickly abstract away browser specific code, so that 95% of the coding I do is "just Ruby"
I suspect I need to find a better way to say it, or maybe I should just rewrite and submit again, maybe before wasn't the right time. I've also submitted a talk on how "all ruby web components was a good thing". In the post React days, this talk topic might make more sense.
@ryanstout I should look into helping w/some volt tools
@ryanstout should I hit you up on the volt gitter?
@jaredcwhite it's worth entertaining, should it be a virtual conf (they seem popular these days), I'd be surprised that we'd have enough bodies to fill an actual for pay venue. At least some of my opal proposals will get accepted ;)
@elia close, my tentative title is "Reasons to NOT use Ruby in the browser", where the items are pretty silly, i.e. "I love never knowing what this refers to", "I love rewriting complex business logic and tests in a different language than the server"