4 ms·
The assets pipeline can be tricky, sure, but it's tackling an issue that is really hard to get right. Routing in Rails on the other hand, I don't really see wha
by VeejayRampay 10y ago
The assets pipeline can be tricky, sure, but it's tackling an issue that is really hard to get right. Routing in Rails on the other hand, I don't really see what's so complicated about it. You define resources, you have namespaces, constraints, the DSL is extremely nice and straightforward, I think it's actually one of the huge successes of Rails as a framework.
- carsongross 10y agoIMO the asset pipeline is not worth the complexity. CDNs + caching do a good enough job of getting stuff to clients, so the complexity (and distinction between dev mode and production mode) isn't worth it. My problem with routing is that the default is an implicit semi-REST pattern, and that routing a lot of verbs to the same controller method is tedious. I prefer Sinatra's "ground up" model instead, although you can certainly write a rails router that way (and sinatra has the same verb problem.) But I concede that's a matter of taste.