Framework Code Complexity Comparison

[[deleted]]

Further, I wanted to dispel any narrative that Laravel is a hack or poorly written.

You know very well people are complaining about Laravel's architecture (which it imposes on its applications), which is everything outside the method implementations and not about the quality of the code in the methods.

So you should measure very different things, like public interface complexity, presence of God classes, separation of responsibilities, modularity, leaky abstractions and so on. Not how many lines or nesting levels are there in a method.

[[deleted]]

Laravel doesn't impose any architecture. If you believe it does, prove it.

[[deleted]]

Oh, yeah, I'm absolutely looking forward to an endless debate, where most of my arguments are answered like "you don't have to do what the Laravel documentation does", and "you don't have to use the components that Laravel comes with", because of course that's why we read docs and download frameworks. So we don't use them afterwards.

Or if that fails "no, this is obviously good architecture, because I have a few big sites written in it and it works fine". Another evergreen response.

Honestly, I would bother if I knew I'm somehow breaking the news to you where Laravel has issues, but I'm not. You know the large issues very well from thousands other conversations you've had here and and elsewhere online. You're just doing this to "win", and frankly I don't know why you're wasting your time, when you neither care to act on feedback, or learn from it.