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/ …
2 replies 0 retweets 1 like -
1 reply 0 retweets 0 likes
-
I don't think you're trolling. Serious Q: How much of Ruby is touched by what Rails does.
2 replies 0 retweets 0 likes -
From the outside it looks like as Rails goes so does Ruby.
2 replies 0 retweets 0 likes -
e.g. If Rails is pushing people to migrate people will do it to avoid losing compat with Rails.
2 replies 0 retweets 1 like -
but we had to make the leap with Rails and it wasn't an easy call.
1 reply 0 retweets 0 likes -
Rails 3 definitely didn't push hard (I was there). For reference, 3.0 released Aug 2010, 4.0 June 2013pic.twitter.com/F0xp3Ck63w
1 reply 0 retweets 0 likes -
so Rails didn't drop support for 1.8 until mid-2013, which is when I'd call the transition "complete"
1 reply 0 retweets 0 likes -
I didn’t have time to write a tweet so I wrote this longer thing instead: https://gist.github.com/ubernostrum/14441f4af5683f2015b56d3bf5f6b4d8 …
2 replies 0 retweets 0 likes
btw I'd also say that I quite enjoyed the discussion with @dstufft and @eevee, despite being skooled multiple times :)
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.