This lesson was a bit involved. Though I am pretty impressed with the authorization aspects of Laravel. There are a lot of helper methods that seem to take care of a lot of the grunt work. I can see why people use this framework for their projects.
Authentication seems to be mostly taken care of behind the scenes. The next lesson will teach the log in process which should be interesting. This one was more of the authorization.
In comparison Laminas I had something that looked at what route that was being used and would redirect as needed for any kind of authorization for a controller. Which given I had separate controllers for edit, delete and so on so it worked pretty well. With Laravel it uses a policy object to control the policies in the controllers, but using an authorize method that would determine which policy it should utilize. Which is way simpler, than keeping a list of controllers.
In the lesson they make use of a Invokable controller. Which is a one function controller that utilizes the __invoke method. They use it for registration and logout. Since it really doesn't fit in the resource controller type, it seems to make sense.
I still argue there is a lot of overhead, though even with Laminas depending the implementation, could also have a lot of overhead. I haven't really looked at the memory usage of Laravel yet, but I am sure it could be up there.
As I said the next lesson is on Authentication. So we will have a sign in page to setup.