At work, we've been using a new JS framework paired with server-less infrastructure for the past 9 months. It's barely production stable, so it's been painful, but hey look at our fancy new framework.
When I started a new side project, I wanted to get an MVP out as quickly as possible. I opted for PHP/MySQL, and development time felt like lightning. It was so refreshing.
I plan on rebuilding the code base, now that the side project is making money, and perhaps I can use newer tech for that, but quite happy sticking with PHP for MVPs.
I have a similar story I recently set out to build a SaaS product and wanted to use/learn elixir. I enjoyed using elixir but a lot of the fairly complex things I wanted to do requires quite a bit of learning and custom solutions. I wound up scraping that version after 2 months and rewriting it in Ruby/Rails in about a week. And adding new features.
I did the exact opposite: I have ~8years of professional ruby/rails experience and I was building a little SaaS. At some point, after 100 hours, I got bored/stuck with only 20% of the planned features to reach a MVP. I decided to switch to elixir/phoenix, where I had few confidence and there was apparently a growing ecosystem not always ready or complete. After 100 hours I completed the MVP and launched it. Using elixir was refreshing and right now I'm using it for almost all my side projects/prototypes.
When I started a new side project, I wanted to get an MVP out as quickly as possible. I opted for PHP/MySQL, and development time felt like lightning. It was so refreshing.
I plan on rebuilding the code base, now that the side project is making money, and perhaps I can use newer tech for that, but quite happy sticking with PHP for MVPs.