2 ms·
Or PHP/Laravel/PG|MySQL Or Rails/PG Or Phoenix/Elixir/PG Or .Net... There's lots of mature stacks not just django. Laravel being my choice because I find djang
by gremlinsinc 7y ago
Or PHP/Laravel/PG|MySQL
Or Rails/PG
Or Phoenix/Elixir/PG
Or .Net...
There's lots of mature stacks not just django. Laravel being my choice because I find django's default admin clunky to grok and kind of ugly would rather just build my own admin or use a package that implements some basics that I can plug into. I also like laravel migrations better, feels more like rails which I started my career in. I know you can do that w/ django rest and what not, but feels like an anti pattern to have a default admin panel that nobody uses because it sucks or everybody uses but you don't want to because it's ugly, etc... Also not a fan of the way people generally handle db models. Eloquent is a beautiful thing, and Query builder is more beautiful when you need raw queries ran.
I've only seriously used Rails/Laravel in dev/production and they're so similar I can easily move back/forth and just change lang syntax. I like laravel better simply because it has a lot more built-ins that I use a lot -- like queues, notifications, auth/oauth via passport, telescope(logging), etc... Haven't used rails in awhile though maybe they've added those natively, but the new ignite plugin for logs in laravel is amazing.
All my own opinions.