DEV Community

Discussion on: My notes from DHH's RailsConf keynote interview

Collapse
 
andrewbrown profile image
Andrew Brown πŸ‡¨πŸ‡¦

I don't care for Webpacker being part of the stack.
It's odd because generally Rails has been reserved on integration such kind of conveniences.
I don't like how its not at easy to start a Rails project as prior

Collapse
 
wood profile image
Joshua Wood

Yeah, I'm torn on that. I personally have warmed to Rails embracing Webpacker because I've had to support issues with the asset pipeline/sprockets, and there is a lot of friction there. It's not that the old way is bad--I think it fits better into Rails, but it complicates using Rails with the modern JavaScript ecosystem so much that the bad outweighs the good. Webpacker has also been getting a lot better in my experience. I used to dread working with it, but I prefer it now.

Collapse
 
nickytonline profile image
Nick Taylor

We use webpacker at DEV and initially, I thought maybe we don't necessarily need it, but it just integrates so well and in some cases, we've had to use the erb-loader πŸ‘‰πŸ»
github.com/thepracticaldev/dev.to/...

Overall, I'm pretty happy with the integration.