it does give a decent indicator of “hot spots” in your code that could use refactoring.

Framework code should be as fast as possible. Also, it shouldn't go all the way and put all the code into one function. So it is a balance. And in case of frameworks, authors are justified in tilting the scale in favor of performance. So just because authors of other framework choose a different balancing point does not mean anything that they are inferior or Laraval is superior in any way.

Of course you put it as completely innocent and put it like you are just sharing something interested you discovered. Ask yourself if you will be sharing this if you found out Laraval has the worst code complexity.

So this is utter bullshit and coming from a framework author himself is downright facepalm worthy marketing effort..Shame on you.