3 ms·

I don't think this is a good argument for or against any framework. It's just an interesting side note.

• zapt02 10y ago
  In the case of Laravel vs Symphony, I think it can. Laravel packs absolutely everything you need to build a web app while still being less than half the size of Symphony, which has a lot less out of the box and expects a litany of third party packages to become functional.
  • tyingq 10y ago
    Laravel seems to pull in at least 9 pieces (probably more) of Symfony via composer: https://github.com/laravel/framework/blob/5.3/composer.json https://github.com/laravel/framework/blob/5.3/composer.json Are those pieces counted in these statistics or the "half the size" thought?
    • realityking 10y ago
      They're not. From the article: > The primary goal of this comparison is to compare how I personally write code vs. how other projects are writing code.
    • zapt02 10y ago
      Good observation. Some of them appear to be debug packages (console, debug, var-dumper) and the others seem to be quite basic stuff (routing, http handling) that is good to reuse, and is also likely something you'll have in your Symfony projects.)
• deweller 10y ago
  From time to time, I need to understand what is going on under the hood of a framework to debug a problem or understand the best way to do things. I find Laravel easy to understand when browsing code because of the short methods. There are tradeoffs, of course, as sometimes it can take several hops through the code to trace down some functionality. But I prefer more short methods vs. one long method any day for readability.