‹ BackHN Continuity

Thread

What About Rails?

334 points · 236 comments · jrochkind1

  1. meerita · · focus · HN ↗
    Every piece of software has an expiration date. You can extend its lifespan, but technology keeps moving. What was considered standard on the backend five years ago may look completely different today. I think that's a good thing. Rails worked extremely well for its time, especially around 2007–2015, but it started to show its age as newer, more capable languages and runtimes matured.

    We should be celebrating the fact that we can now port almost anything with far less effort, or modernize an existing stack to meet today's performance expectations, requirements, and engineering standards.

    1. voidUpdate · · focus · HN ↗
      Whats the expiration date on, say, the windows 95 version of paint? Because it still loads just fine on my current windows computer, does everything I'd expect from a paint program, and gets out of the way when I don't need it anymore
      1. meerita · · focus · HN ↗
        I don't know the expiration date of all software, I only know all software has some expiration date. Maybe that version you're using will not be usable in the next 5 years, and it will prove my point. That doesn't mean you cannot use it anymore, it means better options took over.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.