The Decline of Django
151–160 of 173 posts
Re: The Decline of Django
#152Eh, "[insert stable, mature MVC framework] is dying/dead/etc" articles are a dime a dozen on the Web. I suppose it could be considered a badge of honor for a framework to have some internet punter declare the framework as "dead". But, just to nitpick... > Bad Official Admin GUI UX For anyone reading, Django's admin tool is designed for situations in which you need to stand up a quick admin or build some internal admi…
Every time someone declares Wordpress dead 10 more sites launch using it. It's like that old saw from Strousstroup: "There are two kinds of programming languages. The ones people complain about and the ones nobody uses".
I'm sure you're off by several orders of magnitude.
Re: The Decline of Django
#153> Django looks like the 40 years old guy who feels "in" using Facebook, while everyone else is already using Instagram or TikTok. wow fuck ageist bullshit like this. everyone knows I'm no big Django advocate but what is the point of a blog post like this? I'm not seeing how effort spent on writing articles like this makes the world better for anybody, including the author. Go create something? >But what if tomorrow,…
NestJS exists. I use it in production and it’s fantastic. https://nestjs.com/
What other frameworks have you used professionally?
Re: The Decline of Django
#154Seems like a strange bit of feedback to me. My company uses Django as the backend for our REST API and it's simply phenomenal. Django isn't a complete solution out of the box, but that's why things like Django REST Framework [0] exist. It supports JSON-based views and has an excellent serialization layer that can map directly to the ORM models. This setup does NOT help with serving our frontend app, but we're using R…
I typically use DRF + Django for the backend and then have one “view” that renders an index.html with a context bridge (passed via a global JS variable) so I can bootstrap the front end with enough server side state to load quickly (and do feature gating and whatnot). Seems to be a great combo to me - you get all the awesomeness of Django/DRF and none of the more archaic html temperate rendering stuff. The only bad b…
Re: The Decline of Django
#155Earlier quoted context omitted.
I really like the Genshi templating language, which TurboGears uses by default. Genshi is a descendent of the Kid templating language, but it uses a (debuggable) streams-based api instead of compiling templates to (undebuggable) Python code. You can use Genshi with Django, of course. https://en.wikipedia.org/wiki/Genshi_(templating_language) https://pythonhosted.org/Genshi/templates.html https://genshi.readthedocs.io…
I like the templating languages that remain valid HTML. It makes it much easier to integrate with other tools like HTML formatters or HTML plugins for JavaScript bundlers.
Templating languages that use almost-but-not-quite-entirely-unlike-XML or -HTML don't work well with standard XML and HTML tools, because they don't recognize XML-or-HTML-with-some-magic-non-standard-syntax-sombody-nailed-on-to-the-side.
Re: The Decline of Django
#156Re: The Decline of Django
#157As a Drupal developer, I understand what this article is saying. The issue is that these systems are built for an older paradigm and not meeting the needs of today's developers. It's taking time to adjust existing code to the new ways, and the developer crowd that built them is interested in new things. Some projects need the rapid development capability of a CMS, but want the front end flexibility of a js app. The p…
You are right they were both invented for the full html page generation on every request paradigm.
Django's concepts are much simpler though. Building a headless, API only, back-end feels very natural. You just skip the html templates. You don't even need special libs like Django rest framework.
Drupal was invented imho, to solve a much different problem set: the community-built CMS. This is where there are many different class of users going from anonymous to full admins that can perform wide range of write actions. It probably excels in this niche. Django can do it, but using custom code/calls where you'll implement most of the logic. Drupal exposes configurations that you can tweak (and have to manage).
You hint on the combinating nature of Drupal modules where every thing can override anything. That is, for me, largely the reason I stopped using Drupal. The Drupal best-practices back in the days (6-7-8), led to awfully unmaintainable code bases for anything remotely complex.
Re: The Decline of Django
#158Earlier quoted context omitted.
> in my opinion I have yet to see any project have better documentation than Django I'm partial to Symfony. Good "getting started", per component documentation and links to cookbook-style articles for things people tend to want to do.
Symfony is a great project, I just feel like, in comparing it to Django, there are so few people who would choose PHP over Python that it's not really a fair fight.
Re: The Decline of Django
#159-40 year old guy
Re: The Decline of Django
#160some decline: https://insights.stackoverflow.com/trends?tags=django Would django benefit from a marketing refresh? Of course. Unfortunately, unlike rails, it isn't a passion project for an independently wealthy person. At the risk of self-promotion, htmx is making all of these excellent, mature server side frameworks relevant again. They are very good at producing hypermedia and, if you don't try to turn them into du…