Is this how laravel will look like in v15? #53917
-
(This is a pamphlet, so please don't be offended) I see more and more features making their way into the core, especially the ones that use php attributes, so I ask you: Is this how laravel will look like in version 15? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 18 replies
-
When the alternatives are only:
then perhaps features in core Laravel makes sense. And remember that Taylor is extremely resistant to feature growth for exactly this reason. Imagine what it would be like if he wasn't so resistant??!! But perhaps it might be possible to split out the core but less used functionality into packages and have artisan commands to make it easy to add them in (assuming that we don't want to expect the user to run a |
Beta Was this translation helpful? Give feedback.
-
There isn't a reason to use Lumen when you have Octane. Laravel isn’t "bloated with features" — it’s flexible and built to handle a variety of use cases. You can easily use only the parts you need for APIs without the extras. No idea where you got that Octane is removing features. I've seen them instead trying to improve performance with better persistent memory. It’s not pushing monoliths, it’s about giving developers options. |
Beta Was this translation helpful? Give feedback.
-
I dream of a laravel free of politics that will not release new versions each year. I dream to have a bare bone inspired by Laravel/lumen 10 latest version at most (not 11) that should be maintained until the maintenance is impossible without breaking changes. New features should come only via packages and once every 5 years lets say (medium lifetime of a project) should a new version be released with breaking changes and their new features but only if needed. Benefits. No more milking clients for their money for useless updates and of course no more big profits for devs and their contractors. Last thought. If you (laravel community) don't wake up, you will end up just like in the above picture and younger devs will stop and say: |
Beta Was this translation helpful? Give feedback.
When the alternatives are only:
then perhaps features in core Laravel makes sense.
And remember that Taylor is extremely resistant to feature growth for exactly this reason. Imagine what it would be like if he wasn't so resistant??!!
But perhaps it might be possible to split out the core but less used functionality into packages and have artisan commands to make it easy to add them in (assuming that we don't want to expect the user to run a
composer
command instead).