top | item 12055769

(no title)

charlietran | 9 years ago

Great article! What did you end up replacing the asset pipeline with?

discuss

order

sophiedeziel|9 years ago

We decided to use Gulp and a bunch of real frontend tools like Browserify and Sass. We moved all the assets to a `frontend` directory, uninstalled the gem wrappers for js libraries and switched to npm to manage them. The assets pipeline is good for small apps, but when you grow, you need the right tools. Frontend tools are good for frontend, no matter how you like or dislike the Javascript ecosystem.

dhagz|9 years ago

I'm curious about this too. I'm at the point in my current project where the asset pipeline is becoming somewhat of a burden, and want to know what others have done to replace it or mitigate it.

sophiedeziel|9 years ago

It's on my ToDo list to write a blog post about the technical problem itself :) Not only the replacement of the assets pipeline but also what we did before.