Slashdot Mirror

← Back to Stories (view on slashdot.org)

DjangoCon 2016 To Be Held In Philadelphia In July (defna.org)

Posted by yaelk on from the django-news dept.

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.

19 comments

  1. First! by Anonymous Coward · · Score: 0

    Posted from my Windows Phone!

  2. News for Nerds by ohnocitizen · · Score: 1, Insightful

    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.

    1. Re:News for Nerds by Anonymous Coward · · Score: 0

      booo its not news

    2. Re:News for Nerds by Anonymous Coward · · Score: 0

      It's news to someone, and it's a (very specialized) nerdcon.

    3. Re:News for Nerds by Anonymous Coward · · Score: 0

      Not really.

      Django sucks and FlipperPA is an obvious shill.

    4. Re:News for Nerds by Anonymous Coward · · Score: 0

      Shut up faggot. I'm gonna fork you with my big dongle!

    5. Re:News for Nerds by Anonymous Coward · · Score: 0

      Sorry. I got Django (I don't actually know if it's any good or not) confused with Joomla (which definitely sucks).

      FlipperPA is still a shill.

    6. Re:News for Nerds by whh3 · · Score: 1

      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.

      --
      remove nospam. to email!
  3. Django killed Ruby on Rails and Node.js. by Anonymous Coward · · Score: 1

    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 awakening. They finally realize that Python offers them everything they wanted all along, and that Ruby and JavaScript were just barriers holding them back from being truly productive.

    Like the old saying goes, once you do Django you can't go back. It becomes physically painful to use Ruby on Rails or Node.js after you've used Django and Python. You feel guilt for not having switched to Django and Python sooner, but you also feel relief because you have finally made the switch and are now infinitely better off that you were before.

    1. Re:Django killed Ruby on Rails and Node.js. by alvinrod · · Score: 1

      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 in the ass and it was easier just to rewrite the whole things from scratch than to muck with fixing all the problems. Conceptually it wasn't that much different from Rails, which I'd previously toyed with one just to see what the fuss was about, but Python is infinitely preferable to Ruby in my opinion so it does have that going for it.

      Hopefully they've got a fairly stable API by now, because I'd hate to use it if they're still tweaking things that break backwards compatibility. Perhaps there was something better I could have done at the time, but I wasn't turning up anything online so it seemed like a rewrite was in order. Fairly easy to use, but changing the API and essentially breaking old code left a bad taste in my mouth.

    2. Re:Django killed Ruby on Rails and Node.js. by __aaclcg7560 · · Score: 1

      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*

    3. Re:Django killed Ruby on Rails and Node.js. by Anonymous Coward · · Score: 0

      I really don't think Nodejs is in flailing health at all or being killed by another platform like Python/Django.

    4. Re:Django killed Ruby on Rails and Node.js. by Chmarr · · Score: 2

      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 give you security and data-loss-bug updates, but won't give you new features. If you wan't those, then you need to track the current version. If you really are stepping through 3 or more versions (or fewer, if it was already using a deprecated feature) then the best bet is to go through the deprecation documents and convert things over... or just re-write. Sometimes that IS simpler. And, of course, target a LTS if that's appropriate.

  4. DjangoCon by Verdatum · · Score: 2

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

    1. Re:DjangoCon by Earthquake+Retrofit · · Score: 1

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

      --
      Fifty years of Yippie! 1968-2018
    2. Re:DjangoCon by FlipperPA · · Score: 1

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

  5. SJWs? by Anonymous Coward · · Score: 0

    Are SJWs going to be at the event? If so, why bother going? These people are cancer.

  6. This isn't C, C++ or Perl by Anonymous Coward · · Score: 0

    I'm a Slashdotter, why should I care about anything else in the software world if it doesn't pertain to C, C++ or Perl?

  7. Yes, but.... by mythosaz · · Score: 1

    Will Tarantino attend?