←back to thread

Taylor Otwell: What 14 Years of Laravel Taught Me About Maintainability

(maintainable.fm)
105 points robbyrussell | 5 comments | 26 Aug 25 12:37 UTC | HN request time: 1.162s | source
Show context
phplovesong ◴[30 Aug 25 15:27 UTC] No.45075453[source]▶
Laravel is using a outdated MVC model, its slow as hell and finally its purpose is basically to put lipstick on what is php.
replies(1): >>45077211 #
1. hu3 ◴[30 Aug 25 19:14 UTC] No.45077211[source]▶
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.

replies(1): >>45080360 #
2. N2yhWNXQN3k9 ◴[31 Aug 25 04:23 UTC] No.45080360[source]▶
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.
replies(1): >>45080877 #
3. stefanfisk ◴[31 Aug 25 06:35 UTC] No.45080877[source]▶
Could you expand on how it uses reflection in a manner that incurs a performance hit?
replies(1): >>45083852 #
4. ebcode ◴[31 Aug 25 15:20 UTC] No.45083852{3}[source]▶
Reflection by itself is a performance hit.
replies(1): >>45090566 #
5. stefanfisk ◴[01 Sep 25 07:58 UTC] No.45090566{4}[source]▶
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.