News for hackers. Stuff that matters.
Re:Introducing the Rails API Project by steveklabnik2 on Thursday November 22, 2012 @02:24PM (#4819745)
The asset pipline isn't removed, so you don't need to do anything special.

That said, I don't think that it's ideal for heavy JS apps. Lots of possible work that could be done in this area.

Re:Introducing the Rails API Project by irahul on Thursday November 22, 2012 @03:49PM (#4819941)
> That said, I don't think that it's ideal for heavy JS apps.

Rails-api churns out JSON, JS consumes it. I can think of performance being an issue.

What are the other issues?

Re:Introducing the Rails API Project by steveklabnik2 on Thursday November 22, 2012 @07:33PM (#4820557)
I've responded to your sibling.
Re:Introducing the Rails API Project by mahesh_rm on Thursday November 22, 2012 @04:25PM (#4820069)
Why don't you? Can you please elaborate on that? Thank you!
Re:Introducing the Rails API Project by steveklabnik2 on Thursday November 22, 2012 @07:33PM (#4820556)
Basically, as it stands, you have to put your {Ember,Backbone,..} app in `app/assets/javascripts/app/models`, for example, which is kinda crazy. I'd like to see JavaScript become an actual first-class citizen.

Also, the pipeline has been re-written for Rails 4, but historically it's been kinda slow and buggy.

For an example of what I'm thinking about, rake-pipeline-web is interesting.