Filip Hracek
Aug 22, 2017 · 1 min read

Thanks! I tried really hard to stay off any examples, because when you mention an example, people tend to focus on that.

Also, I don’t think there’s necessarily a single notable framework that should not have been ever adopted by anyone. It’s always per-project.

Alright, I’ll give an example :)

I used Ruby on Rails to build my ancient blog sometime in 2005. For that particular use case, I think RoR was a good fit. I never really had to touch the project after that, and about 10 years after the initial release, I just “baked” the app into static HTML and everything’s fine. (I don’t post on that blog since about 2009.) Ruby on Rails is one of those frameworks that is amazing to start with — so again, it was a good choice. But I’d argue that for many a big project that needs to be maintained even now, RoR might not have been such a great pick. (I’m saying this knowing full well that AirBnB and Github and many many other sites are built with RoR and are doing great. My statement is based on some examples among smaller sites with fewer engineering resources — if they picked something like PHP instead of RoR, they’d be better of. And this is coming from someone who is definitely not a fan of PHP.)

)

    Filip Hracek

    Written by

    Developer and manager working on Google’s Dart programming language and Flutter SDK; gamebooks enthusiast; https://filiph.net