21–30 of 93 posts
It does have graphQL which can get a little tricky, but the constantly rebuilding dev environment and GitHub hook driven deployments make running a site a breeze.
Still Django. It's in a weird state where it's starting to show its age, but everything else is at least 10 years away from catching up. So still the best bet if you're starting something new today.
I usually end up with fairly succinct code and it's never difficult coming back to a project that is 5-6 years old. Can always understand what's going on in the project and get my mind back and running quickly with it.
Using it with GraphQL (graphene) makes it feels a bit more like one of the newer frameworks out there.
Really happy I learned it years and years ago. Nice to invest time into a framework that is still going strong so many years later.
I'm building a new application this year and I'll be using Go for the backend and Flutter for the frontend (both web and mobile).
It can do anything you could possibly want to do with a standard web app and if you really want to do crazy Javascript things you can always just use it as an extremely powerful backend for whatever the frontend framework of the day is. The admin site alone has saved me weeks of work and I keep finding amazing features in it that often just seem like magic (formsets!!).
Earlier quoted context omitted.
Can you share a bit more about how it's showing its age? (I'm not a web dev, but played around with Flask recently and in general find the giant ecosystem of different frameworks fascinating.)
> Can you share a bit more about how it's showing its age? 1. There are some bugs that can't be fixed just because they break backwards compatibility. E.g. usernames are stored to the database incorrectly by default, but the dev team isn't going to change it. So if you don't know that it works the way that it does, it can cause issues. 2. Most people now use a js frontend and a REST backend. Django can do this well,…
If i saw this sentence out of context I would have bet a decent amount of money you're talking about C++. This describes C++ to a T.
So why not use Rails?
There is your answer!
But for anyone with a decent amount of programming experience in a mainstream high level language like C# / Java / JS / Python / Ruby etc. it's probably best to stick to your own language and pick it's stack, if it is dev speed you are after. Some might be easier to set up than others, but there are plenty of example github repos you can clone to get started anyway.
For (what I'll call.. sue me) "systems" languages C, C++, Haskell, Rust, GO etc, I'd probably move over to one of the mainstream stacks for getting things done fast, as they will have a better ecosystem. Also if you already know one of those languages you can easily work with the mainstream ones!
Python => Django
PHP => Laravel
Ruby => Rails
Node/JS => ExpressJS
Elixir => Phoenix
My personal opinion on building web applications the quickest way. I mostly use Laravel.