One the other hand, you have VS Code which is becoming a “no-brainer choice” code editing tool for many people. You need to pay, the IDE is not very fast, a little bit bloated, specialized in Python. One one hand, you have P圜harm Pro that has an extensive support of Django out of the box. Let's say you're a beginner and need to pick an IDE today. I'd answer that to make a good framework, you need a community, and to attract new people, you need marketing. You could argue that marketing is not the way to make a good framework. As a guy who still uses RSS feed rather than twitter, I'm not saying that Discord or Github issues are necessarily better or more suited tools, but come on! If you're a 22 years old student, you probably never used and will never use IRC.ĭjango looks like the 40 years old guy who feels "in" using Facebook, while everyone else is already using Instagram or TikTok. On the getting help page, I see links to Django IRC channel to ask for a question, and Ticket tracker to report a bug. I'm not whining and saying everything is bad (that's not the case at all), I'm just comparing with newer tools and can't help thinking it could be way better. You'll find good looking documentation, clear navigation menus, instant search powered by algolia, accesible easily from Google. I'm not whining about this, but the comparison hurts. The best process for me to find relevant Django doc today is googling, finding a Stack Overflow post, and having someone pointing to a Django doc. Searching within the Django website is not better, the results are rarely what I expect.Django documentation SEO seems to be broken, I don't know why. Documentation is scattered between versions and you often get results from older versions, with absolutely no reason. Searching from Google, it's really hard to get relevant results.So like many people I guess, I use search. Navigation from one page to another seems unclear to me. But it's more an opinion than a fact, lot's of people love that documentation is often self-sufficient to understand everything, unlike other tools in which you need to read blog posts to truly understand.įor me, in documentation, the main issue is not about the "what", but the "how".Īfter many years of using it, I'm still not sure how it's organised. No efforts are made to modernize tooling Outdated Documentationĭjango is known to be extensively documented, and it's true, and I would even dare to say sometimes it's too documented, and the important stuff 90% of people are looking for is hidden by details that are relevant to 10% of people. Let's now browse my main frustration points. If something is wrong or inaccurate in this post, please just tell me and I'll edit the mistake. I'm just the guy who waits for new versions with expectations, reads changelog, and keeps being disappointed. I'm talking from an external point of view, I'm not an expert knowing exactly what's happening inside the Django Teams and I don't read many tickets. I loved Django and still love it, but sometimes can feel a little bit frustrated by what Django could have evolved towards but did not, purposefully or not. The purpose here is not to blame anyone for this because Django is a foundation, and without volunteers or funds, nothing can happen. Lots of developers are choosing to shift to node.js based backends (even if sometimes I think it's not a wise choice, but this would deserve another post to explain). Since Django 2.0, version numbers use a loose form of semantic versioning, which gives the feeling there are many new features because there are new versions, but it's not the reality. Let's face it, it’s not very exciting to be a Django developer today.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |