Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Decline of Django

david-dahan.com

Post reply on HN
Print view View original

71–80 of 173 posts

Re: The Decline of Django

#71

Post by ianai »

dc-programmer wrote: post #47
TameAntelope wrote: post #39

1) Documentation is too verbose 2) Onboarding new developers lacks IDE specific tooling for free 3) Admin GUI isn't great 4) Async support is still incomplete 5) Static types aren't used in Django 6) Django is MVC which isn't useful if you just need a light V 7) People ignore other, newer tech because Django exists What??? 4 and 5 are legit complaints, the rest is literally the nittiest of picks, in my opinion. You d…

Number 1 isn’t a show stopper in any way but is it pretty annoying. The primary django docs are very textual and place more emphasis on developing intuition and understanding context, than something that can be quickly referenced. Also a lot of the method parameters are either not documented or not explained. I think Django would benefit from a more technical and complete but less dense secondary reference.

“ more technical and complete but less dense secondary reference.”

Isn’t that basically just reading the source code? Like I get that’s probably not right to throw everyone toward, but reading source code is a staple task for working with FOSS.

Re: The Decline of Django

#72

Post by uyaij »

devwastaken wrote: post #9

If I were to have a Django backend and only be serving Json responses, what combination of methods/libraries are commonly used for that? Such as input validation, client side request sending, etc.

I've recently started using Django Ninja at work, and I really like the FastAPI-like request/response schema handling.

[1] https://django-ninja.rest-framework.com/

Re: The Decline of Django

#73

Post by yxhuvud »

mtberatwork wrote: post #44

Eh, "[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…

Nothing you wrote invalidate the point he makes about admin UX. Internal pages may not need to be fancy, but realizing that expectations change over time and that it may be a good idea to polish the UX a little isn't something that should be ignored by saying that only internal people will use it.

If the claim had been about ugliness, then you may have had a point, but it was not, it was about UX.

Re: The Decline of Django

#74

Post by olorton »

arkh wrote: post #57
mtberatwork wrote: post #44

Eh, "[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…

> 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.

I've used Symfony for years, and Django for 2 years full-time, and I have to say that I find the Symfony documentation is much easier to learn from.

Re: The Decline of Django

#75

Post by sillycube »

SaltyBackendGuy wrote: post #62
mtberatwork wrote: post #44

Eh, "[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…

> Bad Official Admin GUI UX As bad as it is, it enabled our team of all backend devs to stand up a functioning infrastructure management tool that was mission critical to the business's success in the early stages, for relatively low effort. I guess it just depends on what you're using the tool for.

Yes, and it's responsive. I am so happy as a solo founder. I can get my admin with almost no effort at all

Re: The Decline of Django

#76

Post by jmugan »

I don't understand why a Python programmer would move from PyCharm to VS Code. PyCharm is pretty perfect as far as I can tell. I've tried to move to VS Code a few times to keep up with the cool kids, but I always seem to run into weird problems.

Re: The Decline of Django

#77

Post by zzzeek »

> 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, Microsoft launches a full-featured node/Typescript framework? You would get ... In my opinion, a framework like this would nail it

it's all you bro, *go write it* and show everyone how right you are!

Re: The Decline of Django

#78

Post by tedmiston »

fixmycode wrote: post #14
devwastaken wrote: post #9

If I were to have a Django backend and only be serving Json responses, what combination of methods/libraries are commonly used for that? Such as input validation, client side request sending, etc.

I think the only real option here would be DRF, it's a very mature library to switch Django from website builder to API backend

Agreed, Django + DRF provides everything you need for this use case out of the box.

Re: The Decline of Django

#79

Post by nicolaslem »

jonnycomputer wrote: post #48

Found lots of things rubbed me the wrong way about this post, though tbh I really haven't done Django dev; only Flask. I'll just nitpick on their bagging on Pycharm. Pycharm is great. Frankly, I like it better than VS Code; though I do grant VS Code has its strengths, especially as a lightweight capable code editor.

Frankly VS Code scares me. Just like Google Chrome, it went from nothing to being the IDE that everyone use. Just like Google Chrome it is backed by a corporation that does not have the user's best interest in mind.

Now I read an article that basically explains that Django is declining because of its poor support in VS Code, that cannot be a good sign.

Re: The Decline of Django

#80

Post by sillycube »

bwood wrote: post #36

Seems 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…

But the template renderer is so powerful. I can easily any print any data to the frontend. I do both Vue and Django in hybrid.
Post reply on HN