5 ms·
We've got a more complex application (Pathwright) running Django, and we're currently going much more heavy client side. Nothing about Django keeps you from doi
by gtaylor 13y ago
We've got a more complex application (Pathwright) running Django, and we're currently going much more heavy client side. Nothing about Django keeps you from doing this, and there are some excellent third party apps that actually make it very easy (django-rest-framework is awesome).
> Django have a bright future in a world that's moving heavily client side, or will it be relegated to a relatively bland corner of the web world?
This is one of those questions seeking controversy where there is none. Django seems to get out of the way even more when you shift to a heavier client.
- zalew 13y agohe's probably referring to the ever-recurring topic of django not integrating front-end libs out of the box (which I in particular support).
- jonknee 13y agoI support that too, but I think Django should provide some default API endpoint support (like Django Rest Framework).
- gtaylor 13y agoI'd be pretty miffed if they did this. You need only look at the comments contrib to see an example of something that was OK'ish when it was incorporated, but has languished since then. Now I question the need to even have it in contrib. We don't have to bake components in for them to be excellent. rest-framework in particular moves ridiculously fast, and being separate from Django lets them do that. Also, if in the future something even better comes out, I can easily switch to it.
- spookylukey 13y agoThe 'comments' app has now been deprecated and will be finally removed from contrib in 1.8
- gtaylor 13y agoGood catch, I had no idea. Glad to see this!
- moneypenny 13y agodjango-rest-framework looks good, been years since I used Django in any seriousness, so will have to give it another run. As an aside, what's the scoop on Python 2.7.X and 3.0 never likely to meet? It makes me uneasy...
- acjohnson55 13y agoI'm not seeking controversy--I really enjoy Django development. It's just that I don't often hear about startups choosing to build in Django (well, besides mine), instead, going with Rails, which seems to have a more active and forward-looking developer community and more aggressive, or flashy new-school stuff like Node/Scala/Go/whatever. I guess what I'm trying to ask is, what is holding Django back? Is it just fashion, or are there more serious perceived shortcomings?
- gtaylor 13y ago> I guess what I'm trying to ask is, what is holding Django back? Why do you think it's being held back? I'm just not seeing the barriers in using newer tech. We stay pretty cutting edge, and haven't had any issues doing so with Django.
- acjohnson55 13y agoBecause you don't hear about it growing in popularity or being used in the hot new stuff on HN.
- adamauckland 13y agoMTV Video use it. Yahoo use it. Django is massive, but it's like toilet paper or condoms. If you use it, you probably aren't going to blog about it because it's just doing it's job. Plus, it's not hot new stuff, they largely attempt to make upgrading easy. Django to me is what .Net is to C#. It's the libraries around the Python language that make it useful.
- po 13y agoI don't think Django is being held back at all. It's healthier than it has ever been. Consider that the reason you don't hear about it isn't due to it not being used but instead to a cultural difference in the people who choose it. I don't think Django developers are particularly good at blogging and self-promotion compared to other projects. They communicate through mailing lists, IRC, twitter, email and documentation. I'm ok with that. When I started my project, I evaluated a lot of different options and chose Django. One of the big factors was a cultural commitment to documentation and slow measured changes with lots of thought put into backward compatibility. Blog posts about hot startups that are using it is low on my list. (and if you do your research you will see that a surprising number of hot new startups are in fact using it)