5 ms·
What about the webpack rails7 situation? I feel like rails has guessed wrong too many times about FE (coffeescript, asset pipeline, websockets) that I don't tru
by itake 4y ago
What about the webpack rails7 situation? I feel like rails has guessed wrong too many times about FE (coffeescript, asset pipeline, websockets) that I don't trust them to deliver their own stack.
- the_gastropod 4y agoI'm not sure this is a fair representation. Rails didn't "guess wrong" too many times. They chose the best option available at the time. Remember, CoffeeScript was used in Rails in 2010! Brendan Eich even borrowed many ideas from CoffeeScript in subsequent versions of JavaScript. Ditto, the asset pipeline solved a great number of problems for many years. With recent advances in web browsers, many of these problems aren't really problems, so it's less relevant, and Rails has to take advantage of import maps as an alternative.
- coffeefirst 4y agoThis is kind of a great example because Django did the opposite: insist on having no frontend opinions. As a result, Django left its users completely on their own, while Rails made choices that wouldn't last the test of time. Given how chaotic the frontend ecosystems have been over the past decade, I'm not sure there was a "right" answer in hindsight.