Changes

[ben-norton]

Why has Laravel become focused on removing things from the codebase? Making things smaller doesn't make things better. It makes things harder for many users. Before passing judgment, I thought it was worth asking. Maybe (and hopefully) there's a good reason for this.

[ahinkle]

Huh?

Example?

[ben-norton]

That's fair.
Middleware. Why was middleware moved? Prior to 12, it had a home under app. The setup was straightforward and intuitively designed. Now, it has to be setup manually using a far less intuitive syntax.

Providers. Why were all of the providers (except for one) removed in laravel 11? They were great and now have to be set up manually (I think, although its not totally clear how to use them now or if they are used at all).

Here are examples of awesome features that were added - the addition of the Api routes file in l5 and the models subdirectory in l8.

A shift occurred somewhere around l10 or l11 where the additions and revisions of the past were replaced with removals and limitations. This trend closely mirrors the growing integration of "pro features". The difference being that the change in monetary focus seems logical and inevitable.

Another one. Why was laravel ui bootstrap dropped? Why am I limited to the small set of Javascript framework starter kits to get things moving. I prefer to avoid out of the box setups like breeze. The laravel ui blade scaffolding was great. I know Laravel Daily kept it alive, but still. It's another removal.

[ahinkle]

There are countless articles online of the reasons behind the listed changes but in short, it was to remove the cruft of the framework. All of those items you listed, you stand still do things that way today — the framework doesn't reject the old architecture.

[robert-moore96]

i could be wrong but i dont believe any functionality was removed, just a few bits of it were moved around to be within the framework rather than the skeleton app unless your specifically want to override that component