Bridging the Gap
summary
Claims that Composer plus framework-agnostic design fixes the add-on fragmentation: about 540 packages still require laravel/framework unnecessarily; century and an OAuth library evolve from five framework-specific forks into single packages with deep integration for four frameworks and native PHP usage; development uses interfaces and drivers, service providers and simple facades; one new OAuth1 implementation gets built because existing ports lack needed simplicity, and the unified packages prove easier to reuse and maintain.
AI-written summary · about
chapters (19)
- 0:00Start
- 1:47Things I Make Myself Part of
- 4:43The Framework Always Fell Short
- 5:15What Went Wrong?
- 6:21Sentry
- 7:11OAuth 2
- 8:36Scenario
- 13:31Step 2
- 15:47Step 3
- 18:02Laravel
- 19:15Reasons Against Making Your Own
- 25:42Forget Your Framework
- 27:02Interfaces
- 30:53Service Providers
- 33:11Facades
- 37:07Package Design
- 40:06Bridging Packages Are Drivers
- 40:28Why Bother?
- 42:32tl;dr
