4 ms·

I worked on a project not long ago that used Rails to serve up purely JSON via a REST API and the front-end was all Ember and Coffeescript. (Coffeescript becaus

I worked on a project not long ago that used Rails to serve up purely JSON via a REST API and the front-end was all Ember and Coffeescript. (Coffeescript because an intern started prototyping part of the UI in it, and we all figured it'd be fun to learn. I'm not sold on it though.) We designed our JSON model differently than Ember Data expected, though, so we basically had to make our own Ruby GEMs and EmberData adapter. But with those in place it's fairly easy to use Ruby as just a back end.

cpursley 13y ago
Interesting. How did you like the Ember/Rails combo? Were you using the Rails asset-pipeline to server the Ember app, or did you separate the Ember app (served statically and hitting API)?
agibsonccc 13y ago
Exactly. I think a lot of web developers could easily find a transition to that model. There's a lot of great libraries out there for this use case. Not surprised you had to do a bit of customizing though. I think over time this will be come easier if not baked in to the frameworks themselves.