5 ms·
This is the first time I've heard of Opal (and I think it's pretty neat). Has anyone written about sharing ruby code between the frontend and backend with Opal
by seniorsassycat 11y ago
This is the first time I've heard of Opal (and I think it's pretty neat). Has anyone written about sharing ruby code between the frontend and backend with Opal (or something like it)?
- ch4s3 11y agoVolt http://voltframework.com/ http://voltframework.com/, and Clearwater https://github.com/clearwater-rb/clearwater https://github.com/clearwater-rb/clearwater are exactly what you're looking for
- rickcarlino 11y agoI've been blogging about it as hard as I can over at http://datamelon.io/blog http://datamelon.io/blog . Hope that more people spread the word- it's going to be an amazing technology.
- thirdsun 11y agoThanks for that, I've been following your series - good stuff. Personally, I might jump into Volt once it becomes more mature.
- nolite 11y agoThis might seem like a dumb question... but why not just write javascript if you want javascript?
- rurounijones 11y agoFor a multitude of reasons. * Some people don't want to context switch between a different front-end and back-end language. * Some people want everything in one language / environment for easier deployment / tooling / package management * Some people just plain hate writing Javascript.
- fkchang2000 11y agoI've written a fair amount via this tag on my blog http://funkworks.blogspot.com/search/label/opal http://funkworks.blogspot.com/search/label/opal I'm committed to providing content for opal newsletter http://opalist.curated.co/issues http://opalist.curated.co/issues so that will be ongoing. Hope there's some interesting info in there
- fkchang2000 11y agoI will be writing some articles on "isomorphic rails" -- I figure that has big reach and gives you the best of both worlds * shared ruby code and views on front and back end * everything else Rails does without having to learn a new server framework