From: "NARUSE, Yui" Date: 2015-12-31T04:00:09+09:00 Subject: [ruby-core:72622] Re: Ruby 3.0 in 2017? As far as I understand, 1. Matz decides the version to be released. 2. Current trunk is version 2.4, but it doesn't mean 2016-12-25's release is 2.4. It may change to 3.0 in 2016. 3. Ruby 3.0 must be 3 times faster than Ruby 2. (Ruby 3x3) This means 3.0 won't be released before it. 4. Ruby understands incompatibility needs sufficient benefit. 2015-12-27 13:45 GMT+09:00 Eric Wong : > It looks like we'll be working on Ruby 2.4 this year for a Christmas > 2016 release. So I guess we won't have Ruby 3.0 won't landing until > Christmas 2017 at earliest? > > For what it's worth, I do not look forward to ever having a > backwards-incompatible flag day for 3.0. Too much has been done > since 1.9 came out to break compatibility. > > From a non-Pythonist point-of-view, Python's 2-to-3 transition looks > like a complete mess. As a long-time (and still daily!) Perl 5 user; > I'm happy to see continued improvements to 5 and don't care at all > for 6, yet. > > Unsubscribe: > -- NARUSE, Yui Unsubscribe: