6 ms·
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 th
by steveklabnik2 14y ago
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.
- irahul 14y ago> 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?
- steveklabnik2 14y agoI've responded to your sibling.
- mahesh_rm 14y agoWhy don't you? Can you please elaborate on that? Thank you!
- steveklabnik2 14y agoBasically, 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.