Hacker News Reader

Comment by brianmurphy | Hacker News Reader

My biggest problem with all of the new libraries coming out is that it leaves me with the feeling that nobody want to improve upon what is already out there. I understand that paradigm shifts may require a rewrite. But nobody is shifting every 2 weeks and getting anything done.

When selecting technology, I want to make a decision that will grow with me over the next several years. When perception is that each library of the day will be thrown out in 3 months, falling back to jquery/php is a really attractive option.

View on HN

This exactly. Sometimes I feel like an old fart still using Django (or Flask if the project is small) instead of some new hotness.

But Django has the DSF behind it moving point releases, bugfixes and major releases in a very sane way. The same absolutely cannot be said for angular (major rewrite in progress!) or a lot of similar projects in the Node.js community.

None of this means Node.js is bad, just that there is something to be said for consistency in development. Now watch as Python/Django devs slowly morph into what Delphi devs used to be ;)

You shouldn't feel like an "old fart" using Django or Flask. I think both are awesome, relevant, and will stick around into the future.

One of the great things about being a programmer is that we know how to program in general. If we have to adopt a new syntax or learn the intricacies of some new methods that's ok, and not nearly equal to the amount of effort we expended to learn how to write code in the beginning.

Keep writing your Django apps. I agree that it's great that DSF is backing a stable and productive framework like Django.

I was working the last year on a Django app. First I hated it, but slowly I started enjoying programming with it. This year I worked mantaining an app with all of this http://teropa.info/blog/2015/09/10/full-stack-redux-tutorial... This supposed to be a simple Web app but, it's a complete mess. I miss Django so much right now.

There are very few people that have the philosophy you describe. In the JS world, I think the Ember team has decided to do that. They have and are improving Ember with new technologies (virtual dom, server-side rendering) but it's still Ember and they take care of backwards compatibility (for the most part).

The most important part of Ember's development philosophy is "Stability without Stagnancy."

Ember is a very under-rated framework.

Looking at Angular 2, for example, I feel they should name it something else. It's misleading. There's no continuity from 1 to 2.

I like the 1 branch, and will be happy to continue with it for a while.

Reply on news.ycombinator.com