Weird example there though, that change in Laravel 5.7 doesn't really affect anything whether you upgrade your older app or make a new one, why would that in particular set you on this path?
No, not this in particular, though it did make me vomit that there was so much chest-thumping and ceremony about this useless change. Being tied to a framework is very bad from a business perspective: imagine having built a large Laravel 4 app. Today a lot of their efforts would be going in "upgrading". Same for Symfony 3/4. I mean, I understand that framework authors realize their mistakes and correct them, but often these changes tend to be too expensive.
The problem, of course, is that thanks to excessive marketing, frameworks are embedded deep within our psyche. Consulting businesses must recommend them with glowing praise (because they help save time), job aspirants can feel good about adding a new (shallow) skill set, and everyone feels like there's on the top of the world.
This merits a full discussion of its own, but I don't have the energy for it. The bottom line is that after a point, a developer feels restricted by a framework and may want to structure things his way. If I ever get the freedom to do that, I'll avoid all of the full stack frameworks.
The kind of enthusiasm i see around Laravel kinda reminds me of how Apple products are thought of.
Maybe i don't see it, and Laravel is really freakin' good and i'm really dense..
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.