Earlier quoted context omitted.
You forgot about PHP going to v8
have you a link handy?
Ruby: We have decided to go forward to 3.0 this year
31–40 of 134 posts
Re: Ruby: We have decided to go forward to 3.0 this year
#32Are they going to make non-backward-compatible changes, or is this just a marketing move?
Ruby 3 is expected to introduce new concurrency primitives that evade the global interpreter lock (guilds / isolates) and type definitions for the stdlib for optional typing support. This should be a big release for ruby!
Re: Ruby: We have decided to go forward to 3.0 this year
#33It appears that Ruby 3 might come short of their 3x speedup goal [1][2] ... has anyone tried out Graal/TruffleRuby? Graal/TruffleRuby has shown some massive perf increases [3] [1] https://pragtob.wordpress.com/2017/01/24/benchmarking-a-go-a... [2] https://pragtob.wordpress.com/2020/08/24/the-great-rubykon-b... [3] https://www.reddit.com/r/ruby/comments/b4c2lx/truffleruby_be...
Look for tenderlove’s comments on TruffleRuby. The performance is at the expense of memory.
Re: Ruby: We have decided to go forward to 3.0 this year
#34Re: Ruby: We have decided to go forward to 3.0 this year
#35Earlier quoted context omitted.
You forgot about PHP going to v8
JavaScript really does take over everything.
Heh. More seriously, I think maybe deno[1] should be on that list, as a nodejs 2.0 / event loop for js 2.0?
Re: Ruby: We have decided to go forward to 3.0 this year
#36It appears that Ruby 3 might come short of their 3x speedup goal [1][2] ... has anyone tried out Graal/TruffleRuby? Graal/TruffleRuby has shown some massive perf increases [3] [1] https://pragtob.wordpress.com/2017/01/24/benchmarking-a-go-a... [2] https://pragtob.wordpress.com/2020/08/24/the-great-rubykon-b... [3] https://www.reddit.com/r/ruby/comments/b4c2lx/truffleruby_be...
Look for tenderlove’s comments on TruffleRuby. The performance is at the expense of memory.
Which comments?
Re: Ruby: We have decided to go forward to 3.0 this year
#37It appears that Ruby 3 might come short of their 3x speedup goal [1][2] ... has anyone tried out Graal/TruffleRuby? Graal/TruffleRuby has shown some massive perf increases [3] [1] https://pragtob.wordpress.com/2017/01/24/benchmarking-a-go-a... [2] https://pragtob.wordpress.com/2020/08/24/the-great-rubykon-b... [3] https://www.reddit.com/r/ruby/comments/b4c2lx/truffleruby_be...
Look for tenderlove’s comments on TruffleRuby. The performance is at the expense of memory.
[deleted]
Re: Ruby: We have decided to go forward to 3.0 this year
#38What 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!
The Crystal programming language might also reach 1.0 this year too.
Towards Crystal 1.0:
https://crystal-lang.org/2020/03/03/towards-crystal-1.0.html
Re: Ruby: We have decided to go forward to 3.0 this year
#39What 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!
Python3 has really been the norm since 3.4, which was released in 2014. After that it took another year until most major packages were updated to Python3, but that happened at some point in 2015. By 2016 there weren't many packages left that weren't Python3 compatible, or that didn't at least have Python3 replacements.
Re: Ruby: We have decided to go forward to 3.0 this year
#40Earlier quoted context omitted.
Are you sure it’ll be awful? Sorbet ( https://sorbet.org/ ) is pretty popular already. It can statically check your whole project and dynamically check it at runtime. It also doesn’t add that much overhead so I’m not sure what you’re on about...
Sorbet looks really cool, too bad they developed their own typing system that keeps types in a totally separate file instead of adopting it.
Sorbet was developed before the details of the new Ruby type system were locked in. They’re working on providing some convergence in upcoming releases.