From: "NARUSE, Yui" <naruse@airemix.jp>
To: Ruby developers <ruby-core@ruby-lang.org>
Subject: [ruby-core:72622] Re: Ruby 3.0 in 2017?
Date: Thu, 31 Dec 2015 04:00:09 +0900 [thread overview]
Message-ID: <CAK6HhspyzHNCwxMHYXKtox15jvSNXD6PQE39JsuZSZC=rg9w9w@mail.gmail.com> (raw)
In-Reply-To: <20151227044537.GA31924@dcvr.yhbt.net>
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 <normalperson@yhbt.net>:
> 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: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
--
NARUSE, Yui <naruse@airemix.jp>
prev parent reply other threads:[~2015-12-30 18:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-27 4:45 [ruby-core:72503] Ruby 3.0 in 2017? Eric Wong
2015-12-30 19:00 ` NARUSE, Yui [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAK6HhspyzHNCwxMHYXKtox15jvSNXD6PQE39JsuZSZC=rg9w9w@mail.gmail.com' \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).