For someone looking to build their own this would be a great starting point, im more looking for micros that I can just build on , and these one are great ones to do that with. Allows me to concentrate on building my code and not on the framework itself.
The point I tried to make is that Symfony allows you to bring your own batteries if that is what you want.
The thing is if is a application that is going to be around for a considerable time, most of the times it will outgrow the micro framework because other people are going to work on it.
If you choose a non standard way of building your application, you are the one how is in charge of documenting it. And we all know how bad we are at documenting things.
The benefit of having a bigger framework from the start is that there is a standard way of working. You might not like it, but if you build multiple projects that standard way of working will make you more productive, for example by using generator commands.
I mentioned Symfony because it provides a way to create a single file app to an MVC website, and everything in between. But You can do that with Laravel too. It is more MVC leaning so you have to ignore more things than with Symfony.
In my head ruby is the language that made micro frameworks mainstream, with Sinatra. And then when node became big Express took over that torch.
I see the appeal of a barebones tool. But I never had the feeling that Symfony or Laravel made me jump through hoops to create smaller applications.
PHP dev for over a decade. Currently the lead maintainer of the Flight Framework for PHP. Love focusing on simplicity, performance and finding good pizza.
I looked this over and while Symfony can do it in one file-ish, I ultimately prefer the path that's simplest. If I was a new developer wanting to build a new project for the first time, even that page on symfony while following proper design patterns, would be a difficult start for me to wrap my head around all of what's happening.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Did you check this page? symfony.com/doc/current/configurat...
For someone looking to build their own this would be a great starting point, im more looking for micros that I can just build on , and these one are great ones to do that with. Allows me to concentrate on building my code and not on the framework itself.
The point I tried to make is that Symfony allows you to bring your own batteries if that is what you want.
The thing is if is a application that is going to be around for a considerable time, most of the times it will outgrow the micro framework because other people are going to work on it.
If you choose a non standard way of building your application, you are the one how is in charge of documenting it. And we all know how bad we are at documenting things.
The benefit of having a bigger framework from the start is that there is a standard way of working. You might not like it, but if you build multiple projects that standard way of working will make you more productive, for example by using generator commands.
I mentioned Symfony because it provides a way to create a single file app to an MVC website, and everything in between. But You can do that with Laravel too. It is more MVC leaning so you have to ignore more things than with Symfony.
In my head ruby is the language that made micro frameworks mainstream, with Sinatra. And then when node became big Express took over that torch.
I see the appeal of a barebones tool. But I never had the feeling that Symfony or Laravel made me jump through hoops to create smaller applications.
I looked this over and while Symfony can do it in one file-ish, I ultimately prefer the path that's simplest. If I was a new developer wanting to build a new project for the first time, even that page on symfony while following proper design patterns, would be a difficult start for me to wrap my head around all of what's happening.