and despite trying to keep on top of this, I have never found a canonical description of the current 3/
reading through this -- no strong statement of what to do. modernize + six seems like the right porting default
-
-
in Ruby, one of the hardest things was getting C libs updated. http://yehudakatz.com/2010/05/05/ruby-1-9-encodings-a-primer-and-the-solution-for-rails/ …
-
I don't think you're trolling. Serious Q: How much of Ruby is touched by what Rails does.
-
From the outside it looks like as Rails goes so does Ruby.
-
e.g. If Rails is pushing people to migrate people will do it to avoid losing compat with Rails.
-
but we had to make the leap with Rails and it wasn't an easy call.
-
Rails 3 definitely didn't push hard (I was there). For reference, 3.0 released Aug 2010, 4.0 June 2013pic.twitter.com/F0xp3Ck63w
-
so Rails didn't drop support for 1.8 until mid-2013, which is when I'd call the transition "complete"
- 7 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.