pshaw....

Thank you!

I think Phoenix has been fairly stable, but I have had no direct experience using it for a while now. I can't talk about the JVM ones. I've also had zero experience on the JVM side of the house.

Nah, it's me that's going to feel stupid when the "why didn't you..." comments start rolling in. :)

Maybe you say I should just freeze all versions of the framework code, and run with that into the future. I tried that. I have 80kloc of Rails that won't run on Ubuntu > 18. And, or course, that means no security updates.

I think we need to start factoring this in to our choice of frameworks.

Not picking on Rails here: it's even worse in the Javascript world. And Python 2 -> 3 is still a mess, all these years later.

It's time to stop assuming latest = greatest, and instead know that latest will be most painful.

I don't want to incur the future debt of Rails or a JS framework.

This has reached the point where some frameworks are not even compatible with themselves. Rails 8, for example, changed how assets work (again) and deleted a manifest file. But use the Rails 8 generator to create an esbuild app, and that app won't run.

Well said! DRY is about having a single source of truth, and never about removing identical lines of code. I updated the 2nd edition of TPP to try to make that clearer.

Who knows, who knows...

We're making that easier: use the code turkeysale2024 when you check out at pragprog.com and get 40% off.

Make a little gerbil happy today...

I'll be interested to hear what you think.