DjangoCon 2016 To Be Held In Philadelphia In July

New submitter FlipperPA writes: It has just been announced that the 2016 vintage of DjangoCon US will be held in Philadelphia at The Wharton School of the University of Pennsylvania from July 17th through 22nd. DjangoCon US is a 6-day international community conference for the community by the community, held each year in North America, about the Django web framework. From its humble beginnings in a newsroom in Lawrence, KS, Django now powers some of the better known web sites on the planet, including The Washington Post, Mozilla, Instagram, Disqus, and Pinterest. Considered by many to be the "batteries included" web framework for Python, Django continues to attract new developers across the globe.

News for Nerds

[ohnocitizen]

Seeing articles like this on Slashdot makes me happy. It's important to keep up with the news, but seeing conferences (especially if they are in places I can travel to) is a nice change of pace that honors the original intent of the site.

Re:

[whh3]

I don't have moderator points, so I'll have to reply: Completely agree. I'm surprised we haven't seen more of this type of "news" before. Of course, it has the potential to backfire if they are taking payments to "advertise" conferences. But, like the book reviews that have an affiliate link, I don't think that there's anything wrong with paying the bills.

Django killed Ruby on Rails and Node.js.

[Anonymous Coward]

The most critical thing to know about Django is that it's responsible for the downfall of Ruby on Rails and Node.js.

Django showed just how lacking both Ruby on Rails and Node.js really are. If you've been stuck using Ruby on Rails or Node.js for some time, using Django is like a breath of fresh air. Django offers a frictionless experience, unlike the very rough experiences that Ruby on Rails and Node.js deliver.

Programmers who use Python after only ever having used Ruby or JavaScript also report a sense of

Re:

[alvinrod]

I have slightly different experiences, but I'm not a web developer so this is more of a one off remark.

I ended up getting handed a website some years ago that someone else had done using Django and that was in need of some updates. The version of Django it was using was completely out of date and there were some major changes to the API in between that and the newest stable version which broke a lot of the old site. It was pretty easy to use, but lack of support for a smooth upgrade path was a major pain

Re:

[__aaclcg7560]

but lack of support for a smooth upgrade path was a major pain in the ass and it was easier just to rewrite the whole things from scratch

*cough* Joomla! *cough*

Re:

[Chmarr]

Django's upgrade/deprecation policies are pretty well documented, but if a project is going to be unmaintained for a long time, and you're trying to, say, upgrade a Django 1.6 app to 1.9, you're going to be in for some pain, as in three versions a feature will go from supported, to quiet-deprecation to noisy-deprecation to absent. If a project is not going to be maintained to track the "latest" Django, it should target one of the LTS releases - 1.8 currently - which will have support till 2018.

That will gi

DjangoCon

[Verdatum]

This conference is gonna be off the chain! Unchained, as it were.

Re:

[Earthquake Retrofit]

Personally, I rather go to a Django Reinhardt conference but what do I know. I still use Pascal.

Re:

[FlipperPA]

Da-ding! https://docs.djangoproject.com/en/1.9/faq/general/#what-does-django-mean-and-how-do-you-pronounce-it

Yes, but....

[mythosaz]

Will Tarantino attend?