Less than 10 years ago "Ruby on rails" was the official successor to Php, at least. Really. Only the last of its "Mohicans" still believe in this, today.
That exactly reflects my feeling too. One should always consider the alternatives at the time, and also their exact incarnation (read: framework), not just the name of the language.
Just like when I thought Delphi was the future of UI development
Well, I still deliver VCL apps after 20 years, 15 years of which in my current job from basically the same codebase, so how bad can it be?
Seriously, the point was more that when you are deciding development target to consider more than just language (so tooling, framework, reuse of current codebases (*) etc). Also keep your requirements straight and narrow, and don't be tempted to add too many new wishes at once as "nice to haves".
The most extreme example was a boss nagging in the decision process to have it "portable" (because he had a Mac, and about 1% of the customers too), but when we really started already canning it after one week as it being to expensive. I learned from that if people want to add requirements, I immediately ask them allocate extra budget for it. Usually that settles it :_)
(*) whole rewrites nearly always are behind on target.