The one thing that constantly impresses me in Django is how the devs handle changes. As much as possible they follow a deprecation schedule, provide opt-in sup

The one thing that constantly impresses me in Django is how the devs handle changes. As much as possible they follow a deprecation schedule, provide opt-in support for future changes ("load url from future" for the url template tag change was introduced in Django 1.3 for a breaking change set to be default in 1.5), and document these changes. For the most part they've not had to make huge changes because they've made good decisions at the beginning and resisted doing silly things in the core. Contrast with Rails and their scriptaculous past, which was dumped for coffeescript, which I'm pretty sure will be dumped soon (coffeescript is fading from the js mindset now for react/jsx/angular/typescript).