Why use a framework.
WHAT IT GIVES YOU
Routing Request and response handling Database access and an ORM Templating Authentication Validation Queues, scheduling, mail, events, caching A command-line tool
WHY THAT MATTERS
Every application needs these, and writing them yourself is slow and error-prone.
WHAT ELSE IT PROVIDES
Sensible defaults for security: escaping, request protection, password hashing.
WHY THAT MATTERS MORE
Protection by default beats protection by discipline.
WHAT IT COSTS
A structure you must learn More code loaded per request than a minimal script
WHEN IT SUITS
Applications with several features Anything with users and data Anything a team will maintain
WHEN IT DOES NOT
A single page Something an existing platform already does
THAT LAST POINT
Do not build in Laravel what a content system already provides.
WHAT TO LEARN FIRST
Routing, controllers, views, and the database layer.
