Sure, that doesn't imply that every complex piece of code that uses reflection is slower than the competition. When profiling Laravel app's my experience is not that reflection is taking up any significant part of the request duration.
Blade templates (very slow, especially with components), reflection, macros, not binding things explicitly in the container, etc, all these things lead to very slow applications.
Those who use Laravel don't typically care about performance though
Comments
Laravel is slow. But it's mostly because of all the monkey patching it allows.
A quick hack to solve current issue often becomes a maintenance nightmare for large systems.
Laravel is slow because it uses reflection like it is free, and it doesn't even need reflection really. Its just a marketing gimmick, IMO.
Could you expand on how it uses reflection in a manner that incurs a performance hit?
Reflection by itself is a performance hit.
Sure, that doesn't imply that every complex piece of code that uses reflection is slower than the competition. When profiling Laravel app's my experience is not that reflection is taking up any significant part of the request duration.
Blade templates (very slow, especially with components), reflection, macros, not binding things explicitly in the container, etc, all these things lead to very slow applications.
Those who use Laravel don't typically care about performance though