3 ms·
I don't see how Laravel lends itself to "rapid prototyping" than any other framework. Sure, Symfony2 or ZF2 has best practices on how to do things, but at the e
by debaserab2 12y ago
I don't see how Laravel lends itself to "rapid prototyping" than any other framework. Sure, Symfony2 or ZF2 has best practices on how to do things, but at the end of the day it's just MVC - you can skip any best practice you want to just get something done. This isn't unique to Laravel.
- mgkimsal 12y agoI think it tends to do with the marketing. Lots of hand-holding walk-through tutorials and help people get "rapid" prototyping with laravel, moreso than the actual code itself. And, to an extent, when you present yourself as being good for "rapid dev", that's what people will associate with the framework. (by comparison, zf has never promoted itself as allowing for rapid development, AFAIK).
- ceejayoz 12y ago> by comparison, zf has never promoted itself as allowing for rapid development, AFAIK Well, no, because everyone would laugh at them.
- mediascreen 12y agoIt's less verbose than Symfony2 and, being pretty opinionated, requires much less configuration for new applications. Facades, macros and route closures supports rapid prototyping and are pretty easy to replace as needed. Included libraries like Flysystem, Cashier, Elixir and the new cron wrapper also eases rapid development. There are also a few tools around it, like Homestead and Forge, that makes it easy to set something up quickly. It's not like you can't do rapid prototyping with other frameworks, but Laravel, to me, is the first PHP framework that actively supports it while providing a flexible enough structure to grow in.