Frameworks come and go. What is trendy today will be deemed obsolete a few years later. By the time when the community no longer interested in said framework, it will feel like the rug got pulled leaving many projects stranded.
I'm not a java developer so I don't pay much attention to spring.
But I think the overarching point also includes versioning. For example, asp.net 1 app will still run today just fine, not so for many of these frameworks. RoR, Laravel, et al, all become a rat wheel of upgrading every 1-2 years.
It's a problem.
Contrast that with CakePHP which is still supporting CakePHP2 (I think, it's EoL is coming up soon though) over many many years. I do worry they're increasing their cadence and becoming like most other frameworks in this regard, so I may have to stop praising them for their attitude for support of older versions.
Agreed - I think most programming language communities have settled on one major framework (though there are plenty of other smaller ones) and they've survived.
Oh I agree - 15 years ago picking a web framework would have been much more difficult - for web frameworks now though I think that using the most popular choice should be quite safe.
Symfony is actually more like several different frameworks under the same name. Some of our projects are stuck with Symfony 1 and upgrading them to the latest version is aking to switching the frameworks because they have almost nothing in common.
I don't have that experience. I have personally run many different services, and most of them starts in seconds. The exceptions are usually those that start some process at startup (like syncing jobs, leader elections, database migrations, waiting for database locks etc.), but that is not something specific to Spring.
