Earlier quoted context omitted.
Have you tried Ruby on Rails. That's my experience with Rails. Everytime I've tried something else (for web dev), I just felt too spoiled with Ruby & Rails and went back. This includes Django and Phoenix (Elixir). Edit: The only thing that Rails lacks is a decent Admin UI included as part of Rails. I know that there are some external gems that can be used, yet that's something that should be part of the framework in…
Even before you get to the lacking Admin UI, the first thing Rails asks me to do is implement authentication. Coming from a true batteries-included framework like Django that feels like a complete non-starter.
Django 6
151–160 of 192 posts
Re: Django 6
#152Earlier quoted context omitted.
I just verified. You can install Python 2.7 on an up to date Windows install as well as an up to date Linux install. Python 2.7 hasn't received security updates (or really any updates) in years, but that does not mean it can't still work on an up to date OS.
The latest 2.7 seems to have a lot of CVEs (did not verify that manually though) https://www.cvedetails.com/version-list/10210/18230/10/Pytho... IIRC some commercial distros maintain patches for 2.7 but then you're paying for being 15 years behind the future.
Looking at the list, I'm actually kind of surprised there aren't more CVEs for python 2.7, but if you're only running it locally or on an intranet I could see letting it ride.
Re: Django 6
#153Earlier quoted context omitted.
It’s very likely that project is a security nightmare. Just an OS old enough to support 2.7 would be problematic.
wouldn't it be faster/safer to upgrade to latest django/python rather than rewrite it in React/Go?
Re: Django 6
#154Earlier quoted context omitted.
Rails tries to more tightly integrate with the front-end which causes a lot of turn over the years. Django projects from 10 years ago are still upgradable in a day or two. Rails does include some nice stuff though, but I much prefer Django's code first database models than Rail's ActiveRecord.
I do agree that Rails' asset stuff has been giant pain over the years and has not kept up well. On the other hand, some apps that adopted separate Rails APIs and a separate (for example, React) frontend have been fine. You're right though that their opinion here added more headaches that necessary!
Being able to sprinkle just enough JavaScript on server rended HTML works really well. That you can now use it iOS and Android apps too makes it a simpler alternative to React IMHO.
I still much prefer server rendering in a monolith than dealing with GraphQL, backend for frontend and the complexity of micro services and distributed transactions.
BTW Hotwire and Hotwire Native are also options for Django too.
Re: Django 6
#155Earlier quoted context omitted.
Why would they retire it? If it ain't broke...
"Fun" isn't the same thing as "functional." I remember having great fun in QuickBASIC. And my son enjoys Scratch. Django code is much more fun to work with than Node, but I can't imagine developing something competitive in it in 2025 to what I'm developing in Node. Node is a pain in the butt, but at the end of the day, competitiveness is about what you deliver to the user, not how much fun you have along the way. * I…
Re: Django 6
#156Can someone remind me how we ended up in the SPA era and why exactly? Was it about not seeing the loading spinner? Or there were more reasons to it?
Adding people to dev teams looks like an obvious way to scale productivity.
Then of course you need to organise them as the numbers grow and the frontend/backend split is the first, naive, place to start.
Re: Django 6
#157Earlier quoted context omitted.
That’s true as long as you are only talking about the backend. Frontend wise, Django is in the Stone Age. Look at Laravel or rails if you want a really complete full stack solution.
I feel very comfortable with Django on the frontend, what are you missing there? I usually use Tailwind or Bulma, with HTMX and AlpineJs. I feel like the experience can be very much React like, even if you leave out HTMX. The frontend game of Django really changed about 2 years ago (at least for me).
And I’m not going to get into the details of whether that stack would work for non backend developers, developers working on medium/large projects and/or medium/large teams. That’s a separate and unrelated discussion.
But compare what Django brings you (Stone Age templating system and that’s it) to what Laravel provides out of the box (or via official packages) like assets bundling, live reloading, an amazing and modern template system with proper “component like” partials or even if you need them, the “big guns” such as Inertia or Livewire. More or less the same is true for Rails with the Hotwire stuff.
There’s absolutely no point of comparison here. Even if that works for you, Django is not even in the same league.
It is still a great backend framework though, which was my point.
Re: Django 6
#158Earlier quoted context omitted.
wouldn't it be faster/safer to upgrade to latest django/python rather than rewrite it in React/Go?
Python 2 to Python 3 in a Django codebase ... may be a full rewrite anyway.
Re: Django 6
#159Earlier quoted context omitted.
I feel very comfortable with Django on the frontend, what are you missing there? I usually use Tailwind or Bulma, with HTMX and AlpineJs. I feel like the experience can be very much React like, even if you leave out HTMX. The frontend game of Django really changed about 2 years ago (at least for me).
Laravel's Blade templates are just absolutely phenomenal. The partial rendering, the integration with Livewire, the first class component paradigm. It's just far beyond stock Django / Jinja at this point and delivers some serious dev experience performance boosts. https://laravel.com/docs/12.x/blade
But what you say is true. Blade is amazing.
Re: Django 6
#160Earlier quoted context omitted.
The latest 2.7 seems to have a lot of CVEs (did not verify that manually though) https://www.cvedetails.com/version-list/10210/18230/10/Pytho... IIRC some commercial distros maintain patches for 2.7 but then you're paying for being 15 years behind the future.
Yeah, it's been 5 years (almost 6) since python 2.7 stopped receiving security updates, but it does still run on modern OS's. Looking at the list, I'm actually kind of surprised there aren't more CVEs for python 2.7, but if you're only running it locally or on an intranet I could see letting it ride.