actually does reflect the status quo wrt Django, which is in fact slowing adoption down quite a bit. 2/
this is pretty misleading. Here's a post from 2011 making the same point. http://sayspy.blogspot.com/2011/01/my-semi-regular-reminder-that-python-3.html …pic.twitter.com/vLyfqf2Qne
-
-
2009 + 5 = 2014. We're now at the end of 2016.
-
And the major libraries/frameworks basically got there by 2014 or earlier.
-
Rails supported Ruby 1.9 in 2011 but we didn't consider that "adoption", just the beginning.
-
OK. If you redefine adoption you get to be right. But I don't agree w/your redefinition.
-
Py3 got adopted fast by single-codebase method not by "we are only Py3 now" method.
-
-
Sure. But you want to take out of context as a way to try to nit-pick. If you go down that road I'm done with you.
-
You're jumping way too quickly to assume bad faith. I'm really not going down that road.
- 3 more replies
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.