David Heinemeier Hansson (DHH)

If there's one that's dated, it's probably that one.

At this stage, Rails has been incredibly stable over many, many generations.

The last major release, Rails 8, was basically a no-op upgrade for anyone running Rails 7.

Rails 7 was almost a no-op upgrade for anyone running Rails 6.

I used to think it required more churn to get

progress to stay on the leading edge of new stuff.

And I wrote this before I experienced the indignity of the 2010s in the JavaScript community, where it seemed like stability was not just unvalued, it was actually despised.

That churn in and off itself was a value we should be pursuing.

That if you were still working with the same framework three months later, you were an idiot.

And I saw that and I actually recalled, and if I was going to write the doctrine today, I'd write that differently.

I wouldn't say progress over stability.

Maybe, or a deeper understanding of the problem.

I think part of what's so fascinating about technology is that we have this perception that everything constantly moves so fast.

No, it doesn't.

Everything moves at a glacial pace.

There is occasionally a paradigm shift, like what's happening with AI right now, like what happened with the introduction of the iPhone in 2007, like what happened with the internet in 95.

That's basically the total sum of my career.

Three things changed.

Everything else in between was incremental, small improvements.

You can recognize a Rails application written in 2003.