6 ms·
Interesting. My own biggest gripe with rails is, by far and large, that any project that even so much as lightly touched the js ecosystem will become unbuildabl
by atomicnumber3 3y ago
Interesting. My own biggest gripe with rails is, by far and large, that any project that even so much as lightly touched the js ecosystem will become unbuildable within about 2 months if you don't tweak things. And for Rails, a huge driver of this is the sass compiler, which (afaict) will download a hosted binary component for recent enough versions but will fall back to building it if it's too old. And "too old" appears to be measured in months. But it's far from the only thing that breaks it.
- andrei_says_ 3y agoWhat expires within 2 months?
- jbverschoor 3y agoJavaScript
- andrei_says_ 3y agoOh, that :( The gift that keeps on giving.
- kbrannigan 3y agoNot just with rails, laravel had this problem with js/ mix. The PHP part would run just fine but the Js tools broke the app. npm install never just works. In my experience Compiled js apps decay really fast. The more complex newer the build tool, the fast it decays.
- kayodelycaon 3y agoRails 6 was a nightmare with javascript. Continuing down the path of handling javascript and css dependencies with ruby gems was a mistake. Rails 7 finally came up with better solutions out of the box. My latest application uses esbuild and the javascript version of sass. All javascript and css libraries are handled by node packages. Way less pain.
- glennericksen 3y agoRapid ecosystem churn is my gripe with Javascript. I've generally found Rails and popular Ruby gems to be very durable over time.
- closeparen 3y agoRuby and Javascript are interpreted languages! Why does there even need to be a build step?
- consoomer 3y agoMy issue with Rails has always been that-- not just the JS ecosystem rot, but gems in general. Running "bundle update" after six-eight months is like rolling the dice. Especially if you use any Rails engines, etc.