News for hackers. Stuff that matters.

catmando2

Re:Hyperloop – The Missing Ruby Front-end Library on Tuesday October 04, 2016 @11:45AM (#12636386)
Great question. We have played with a bunch of different names. As soon as we changed to hyperloop our visibility shot way up. We are not convinced that its the perfect name, but so far it has really helped generate interest!
Re:Hyperloop – The Missing Ruby Front-end Library on Tuesday October 04, 2016 @10:31AM (#12635787)
the reactrb ruby-dsl is built on top of React.js. Its not a huge piece of code (no bigger than many many other ruby gems people rely on, on a daily basis.)
Re:Hyperloop – The Missing Ruby Front-end Library on Tuesday October 04, 2016 @10:27AM (#12635761)
Amen and well said!
Re:Hyperloop – The Missing Ruby Front-end Library on Tuesday October 04, 2016 @10:25AM (#12635746)
at catprint we are using reactrb (now ruby-hyperloop) to clean up our mess of ruby + JS + HTML + ERB + HAML etc. So far the results have been excellent with a reduction from about 70K SLOC to 35K SLOC.

Some of the other advantages: A common tool chain, including testing (we are using rspec), people don't align themselves as front-end vs. back-end developers, easier training for new hires.

Point taken about choosing the "right tool for the job", however there is nothing in JS that makes it a better tool than ruby. In fact I would argue (but it is opinion) that ruby is a far better tool than JS. So why not use ruby for full stack? If I felt that somehow JS was better than we would have worked towards using Node for a full stack solution.

Of course its not just the language, its language + available libraries and tool chain. In that regard Ruby is far superior.