auto-translation wouldn't have worked for Rails and hasn't worked for Python. Single codebase is important.
the fact that Py3 started with a "breaking is ok" POV and had to ease into compat definitely didn't help things.
-
-
not much prior art for this. at the time i imagine it seemed that everyone would just port to py3 only and then we'd be done
-
btw this is how Ember handled the same kind of mistake http://emberjs.com/blog/2015/08/13/ember-2-0-released.html#toc_improved-release-cadence …
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.