| The ecosystems. Laravel's first-party ecosystem, both paid and free, on top of the framework is quite widespread. This also brings a lot of people to the party on the third party side with excellent tools like Filament and Ploi. I don't see this nearly as much for Django. Have a look under the Ecosystem tab on the Laravel homepage. Within a few `composer install`s, you can get: - Local dev environment (i.e. actually running the app): Herd, Sail - Stripe/Paddle support: Cashier, Spark - Starter kit scaffolds including all the usual auth goodies (e.g. 2FA): Breeze, Jetstream - View layer alternatives to plain old HTML views: Livewire, Inertia - API and Social logins: Passport, Sanctum (for SPAs), Socialite - Fulltext search: Scout - Robust APM: Pulse, and Telescope on dev - Admin panels: Nova, and 3rd party Filament - Websockets: Echo, Reverb (coming soon) - Infrastructure, both traditional and serverless: Forge, Envoyer, Vapor, Ploi - Completely alternative PHP runners to replace php-fpm: Octane with Roadrunner, Swoole, or FrankenPHP - Automated browser testing: Dusk You can find Django packages for these things too, but I struggle to see many of them coming from the actual Django team. I also think the Django Admin solution is very neat for getting off the ground, but doesn't seem as robust as Nova or Filament. Lastly, call it my bias, but Python's overall lacklustre developer experience with package and environment management (compared to Composer and Ruby gems) also affects Django as a result. |