Skip to content

Comment on Taylor Otwell: What 14 Years of Laravel Taught Me About Maintainabilityparent

Comments

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

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.