While I do agree you in general, I believe the comparison is valid in this case.
The history of our product is like this.
The MVP was about 80% done in Laravel around the time I joined the company.
I joined the company as a symfony developer who was supposed to migrate the MVP to using symfony because "enterprise" and yadda yadda yadda as desired by our CEO.
We were successful in migrating to symfony 2 after about 2 months of work. From there, the system evolved over a few months going through multiple chaotic pivots.
While the product worked, we had taken on a non-trivial amount of technical debt due to the rapid pace of evolution and numerous pivots.
As we were about to move to the next phase in our development, I spoke with our CEO about the technical debt we had incurred and possible ways in which we could shed it.
Being a technical guy, he understood where I was coming from and allowed us a month to clean things up.
The plan was to migrate to symfony3 while cleaning up the mess we had created.
However, while were working on the update, we started experiencing some of the same pain points we had before including performance issues, composer memory issues, poor library availability, late or no feedback on github issues etc...
Since I had done a project using the rc1 bits of asp.net core and updated the application to rc2 bits after and had a good experience I suggested that we gave it a try.
The performance and dependency management issues went away. Development speed also improved as we had better tools to work with.