alt Hacker NewsI’m ex-ruby on rails dev.
Framework and language upgrades are super annoying in ruby and rails. LLMs obviously make it easier, but a rails project can’t be “done” or you risk being so far back in versions that it becomes impossible to leap forward to the latest when you wanna fix a bug or add a feature.
Replies
This has been less and less true for a while now. The jump from 5-6 and forward have been pretty smooth for big projects I maintained. From 2-5 was quite painful... especially from 2 to 3.
I have a typescript app that launched February. It's regularly updated when there are bug reports, but I'm doing a big cleanup in prep for new marketing efforts.
I don't know how folks stayed on top of this ecosystem before LLMs. Rails was at least on a schedule.
Is that really different from anything else?
If you’re not upgrading your deps and rebuilding your rust project this morning, you’re pretty likely exposed to eMudhra. If your project was “done” a few years ago that’s likely not going to be easy.
I went 4.2 -> 6 once and it was horrible. Everything since then has been easy. Upgrade struggl’n are simply no longer an issue.
You could say the same about any language or framework.
I wonder how all the old PHP apps are going to fare today, I hear there's a major security issue.
This hasn't been the case for years.
There was only one hard jump and that was because of the frontend side of things. Luckily that's behind us.