3 ms·
Sure you could, but it would take a much longer time and you'd miss lots of functionality. How long would it take you to build user registration / verification
by viraptor 4y ago
Sure you could, but it would take a much longer time and you'd miss lots of functionality. How long would it take you to build user registration / verification / password recovery / 2fa / sso / profile editing / spam registration prevention / etc. ? How long would it take instead to include some Laravel module which does all of that? If you're building a service with some purpose, do you really want to spend days writing the first option instead?
- tored 4y agoHow many hours spent on battling Laravel to do what you want? How many hours spent on upgrading Laravel versions? Framework solves a general problem, but we try to solve a specific problem, thus it will always be a mismatch, frameworks usually solves that with a combination of magic and opaque abstraction layers. Frameworks works best for short running projects, long running projects tend to outgrow the framework. Prefer libraries over frameworks.
- viraptor 4y agoThat works for some things better then others. For example user management is hard to do as a library, because now you need to hook up all those actions / pass the data to them manually. Then make sure you handle all the headers correctly. Then handle the sessions/invalidation yourself. Potentially implement your custom authz as well because that's also happening throughout your app. There's still a lot of glue code that would be involved here - it may be worth trading it for the occasional Laravel upgrade.