From the outside it looks like as Rails goes so does Ruby.
my original point (which I stand by) is that Django 1.6 is culturally analogous to Rails 3.0.
-
-
and the timeframes are so wildly different that saying "nothing to see here" strikes many informed ppl as wrong
-
"None of this was hard for me to find out, by the way" is deeply misleading too. 1/
-
https://wiki.python.org/moin/PortingPythonToPy3k … is still the top hit when looking for advice and offers 3 choices. 2/
-
Many people know, but not everyone, and there's still a great deal of "defensiveness" 3/
-
I don't mean that in a bad way. It's natural and I've done it too over the years. But it's not productive 4/
-
That said, I don't really have any major quibbles with any of the factual statements in your post. 5/
-
So thanks for writing it up. It was helpful. 6/6
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.