Ruby: We have decided to go forward to 3.0 this year

mfontani wrote: post #4

What a year! Python 2.x dying; Python 3 becoming the norm; "Perl6" renamed to raku & Perl5 thinking of bumping to v7... and now Ruby going all the way to v3.0!

You forgot about PHP going to v8

Re: Ruby: We have decided to go forward to 3.0 this year

#7

Post by maxpert » Mon, Aug 31, 2020, 3:38 PM UTC

Did we get JIT?

Re: Ruby: We have decided to go forward to 3.0 this year

#8

Post by ilikepi » Mon, Aug 31, 2020, 3:38 PM UTC

sacado2 wrote: post #5

Are they going to make non-backward-compatible changes, or is this just a marketing move?

It might be a little of both. I did come across this change to keyword arguments[1] recently, but I'm not sure how impactful it is since I don't personally leverage keyword arguments right now.

[1]: https://www.ruby-lang.org/en/news/2019/12/12/separation-of-p...

Re: Ruby: We have decided to go forward to 3.0 this year

#9

Post by anonova » Mon, Aug 31, 2020, 3:39 PM UTC

splitrocket wrote: post #3

ricardobeat wrote: post #2

Context? What changes are in v3?

The goal of Ruby v3 is to be 3 times faster than v2. https://blog.heroku.com/ruby-3-by-3/ Unclear if that goal has been achieved.

From benchmarks [1], 2.8.0 (with jit) is ~2x faster than 2.0.0p648 [2].

[1]: https://pragtob.wordpress.com/2020/08/24/the-great-rubykon-b...

[2]: https://pragtob.wordpress.com/2017/01/24/benchmarking-a-go-a...

Re: Ruby: We have decided to go forward to 3.0 this year

#10

Post by anonova » Mon, Aug 31, 2020, 3:42 PM UTC

maxpert wrote: post #7

Did we get JIT?

Yes, it was introduced in Ruby 2.6 (2018): https://www.ruby-lang.org/en/news/2018/12/25/ruby-2-6-0-rele...