I agree, and will add that even though it might seem "boring" to some people, there are plenty of unique fun requirements per project even when using the same stack. 5 different clients have gotten me to start new projects in the past 3 years, and I chose Rails for all of them. Different business domains, different budgets for MVPs (4 figures to 6 figures), sometimes multiple developers and sometimes not, but in all cases we were able to ship product quickly without burning too much of the client's money. Contrast that with some bloated, slow dev on traditional SPA apps I saw during my last stint in enterprise, Rails enables us to move at lightning speed. Seriously, I saw people burn way more money for far less output! Maybe SPA wasn't the only problem and enterprise was, but the point is for that a lean MVP for a wide variety of domains, it's hard to beat Rails if you already know it.