We're using this on a large'ish project at the moment and thrilled with the productivity gains. Right now we're using Rails 4.1RC2 + Opal and thrilled with the readability that we now have across the board. This is good sized project for several thousand concurrent users and was to test the waters before using for something larger on our plate.
I'm curious what kind of features you have on the client side that you're using this for.
Opal: Ruby in Your Browser – the Basics
41–47 of 47 posts
Re: Opal: Ruby in Your Browser – the Basics
#42I looked at this just a few days ago but decided not to pursue it any further because of how much junk JS it needs to generate and how readable that junk JS would be during debugging.
You might want to look at https://github.com/rubys/ruby2js
Re: Opal: Ruby in Your Browser – the Basics
#43How is this "Ruby in Your Browser", per se? You're just saying that you've used Ruby to build a web page now in the browser, correct? I ask because I'm seeking something more like a Ruby on Rails Implementation waiting for you in your browser, in effect, when you arrive at the service's website, which you can then take with you if you'd like, as a VM, in any number of ways.
The maker of `lissio` also started hacking on a little project that is not complete, but gives an idea of a WIP lissio project here: https://github.com/meh/gwentoo
Just kinda nice to see how it goes together and how very flexible it is.
Re: Opal: Ruby in Your Browser – the Basics
#44One big problem with this is that you still end up having to use raw JS anyway. Debugging is usually a big hassle too.
Re: Opal: Ruby in Your Browser – the Basics
#45This is amazing but I agree with others, dealing with generated code can be tricky in production environments.
Re: Opal: Ruby in Your Browser – the Basics
#46We're using this on a large'ish project at the moment and thrilled with the productivity gains. Right now we're using Rails 4.1RC2 + Opal and thrilled with the readability that we now have across the board. This is good sized project for several thousand concurrent users and was to test the waters before using for something larger on our plate.
I'm curious what kind of features you have on the client side that you're using this for.
Re: Opal: Ruby in Your Browser – the Basics
#47Earlier quoted context omitted.
Opal creator here. Debugging in Opal is no problem at all with source maps. I only need to look at generated code when Im working on improving the compiler/fixing bugs. Developing end apps always results in using the chrome debugger stepping through source-mapped code. About the raw JS, to use my current app as an example, I have one line of inline JS (using `...` notation) which is just to initialize FastClick. Writ…
What kind of client side coding are you using it for?