TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Django Developers Survery Results

113 点作者 neokya将近 10 年前

10 条评论

mianos将近 10 年前
It's quite interesting that the ORM comes in first in the question on value. Ahead of routing and views. Once I learnt and used SQLAlchemy, I think the Django ORM is lesser component than the routing/view processing, which I find much of a much-ness in terms of the other major frameworks. That said, in django, batteries are included, and spares, and rechargables, and a charger!
评论 #9794272 未加载
评论 #9793382 未加载
throwaway77632将近 10 年前
Missed the survey but going to express my feelings here hoping that they will still be read. I like the opinionated, batteries included approach of Django a lot. My major gripe with it is that it only takes you so far. There&#x27;s a ton of ever expanding documentation out there how to make your first app. Whether it&#x27;s the official tutorial, another one or a workshop. But when looking to build something less trivial—not just bigger, but more complicated—I don&#x27;t know where to look for in-depth guidance. Compared to Rails there really aren&#x27;t too many books out there. I should give an honorable mention of Two Scoops of Django, but the style of many loose bits of good advice still doesn&#x27;t help me with the bigger picture. Getting Started with Django made me hopeful, but somehow it never got past the first few episodes which again cover just the basics. Where to go after that? Just asking questions doesn&#x27;t cut it. If the question is too broad, you&#x27;re referred to the documentation, or the answer is too broad as well. And asking a specific, answerable question is hard when you&#x27;re not comfortable with the technology yet. Either way, it takes too long to ask all the questions that arise and wait for the variety of answers that might follow, compared to reading a book with well-worked examples or so that form a coherent whole. I&#x27;m starting to feel that the only way to get fluent in Django would be to get a job in an experienced Django shop, which IMO should not be the case. On IRC in particular I sense an off-putting attitude that &quot;we experienced Django developers know how to do it right&quot; without really making that knowledge accessible to others. The documentation isn&#x27;t by far as opinionated as the framework itself. As a result, I end up trying things that in the end can&#x27;t be made to work well.<p>TLDR; I would like Django to be more accessible not just to beginners but especially to advanced starters.
评论 #9798500 未加载
评论 #9795120 未加载
owaislone将近 10 年前
I see some comments about static assets management, reactjs and webpack. If anyone is interested, I&#x27;ve written an app that integrates these things with django in a clear and easy way. Check it out: <a href="https:&#x2F;&#x2F;github.com&#x2F;owais&#x2F;django-webpack-loader&#x2F;" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;owais&#x2F;django-webpack-loader&#x2F;</a>
knes将近 10 年前
I see a lot of feedback about how difficult it is to use websockets or add real-time features to an Django app. I work at Pusher (<a href="http:&#x2F;&#x2F;pusher.com" rel="nofollow">http:&#x2F;&#x2F;pusher.com</a>) and this is exactly what we do. We make it dead simple for any developers to use websockets and handle the scaling and maintenance for them.<p>We even have custom libraries for Django such as Django-pusherable <a href="https:&#x2F;&#x2F;github.com&#x2F;pusher&#x2F;django-pusherable" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;pusher&#x2F;django-pusherable</a><p>Associated blog post at <a href="https:&#x2F;&#x2F;blog.pusher.com&#x2F;django-pusherable&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blog.pusher.com&#x2F;django-pusherable&#x2F;</a>
评论 #9793395 未加载
评论 #9794444 未加载
评论 #9793481 未加载
nchelluri将近 10 年前
Just a quick and minor note, the title of this link has a spelling mistake, &quot;Survery&quot;.
Ciantic将近 10 年前
I&#x27;ve used Django a lot, however for past few years I&#x27;ve wanted to transition to type safe languages. Python should get serious about static analysis, e.g. mypy or some such, they provide a great way to increase productivity, and help you refactor if something changes.<p>I tried with Atom and (jedi) plugin, get this `CharField([Ctrl+Space]`, it fills me with `CharField( * args, * * kwargs)`, sigh.
评论 #9793017 未加载
评论 #9793042 未加载
评论 #9795729 未加载
jtchang将近 10 年前
This is an awesome survey. I am a avid fan of Django and have been using it for over 4 years.<p>I found it amusing people are split between 6 and 12 month for release cycles.
评论 #9791705 未加载
评论 #9791884 未加载
scrollaway将近 10 年前
I wonder, are the text replies on the agree&#x2F;disagree&#x2F;favorite&#x2F;least favorite sections exhaustive? I&#x27;m guessing they were filtered somehow since there&#x27;s so few, compared to the amount of replies (and the lack of people talking about their privates).
dwightgunning将近 10 年前
This is really interesting from a community point of view. Embarrassingly I didn&#x27;t hear about the survey and thus didn&#x27;t submit responses. Lots to learn from the answers though.<p>Does the Rails community do a similar survey?
评论 #9792166 未加载
simonlebo将近 10 年前
I&#x27;ve been starting a few Django projects during the last few years and I have had trouble finding packages that are compatible with the latest versions. Maybe their release cycle is too fast for all the 3d party apps to keep track?<p>Also I find that some of these 3d party apps use a notation like &gt;= Django 1.X but that&#x27;s not really true because of backwards incompatibility. A clearer way to know what exact version Django apps are compatible with would already be really helpful.
评论 #9792565 未加载