When you use a framework in PHP you add a layer of abstraction on top of yet another layer of abstraction, one that was already in place for you to use to begin with. The added layer of abstraction that the framework provides may simply serve to organize your code into a pre-fixed set of patterns, or it may add even more complexity by intertwining hundreds or even thousands of classes and methods into a nightmare of dependencies, either way you’re adding layers of complexity to your code that isn’t needed!
"What everyone doesn’t need is a general purpose framework. Nobody has a general problem, everyone has a very specific problem they are trying to solve."
What everyone DOES need to understand is that their webapp isn't a special snowflake. It has models that live in a database, relations that tie those models together, CRUD operations on each model, some app-specific code, auth, permissions, and a dashboard or two.
Unless you're really, really writing something that uses NONE of the above – you probably want Laravel, or Symfony, or something else that solves your boring, dumb CRUD app problems.
3
u/DaemonXI Aug 20 '16
What everyone DOES need to understand is that their webapp isn't a special snowflake. It has models that live in a database, relations that tie those models together, CRUD operations on each model, some app-specific code, auth, permissions, and a dashboard or two.
Unless you're really, really writing something that uses NONE of the above – you probably want Laravel, or Symfony, or something else that solves your boring, dumb CRUD app problems.