11–20 of 134 posts
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.
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...
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.
Earlier quoted context omitted.
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...
It sure does blow up your logs if you're using rails with 2.7.1.
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!
Are they going to make non-backward-compatible changes, or is this just a marketing move?
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.
Are they going to make non-backward-compatible changes, or is this just a marketing move?
looks like they're adding an optional type system, which means you get the worst of both worlds- no guarantees AND no compile-time type checking (think: what happens if type-checked code calls non-typed code?) so I have no idea how they're going to make that fast since all types will still have to be checked at runtime
Are they going to make non-backward-compatible changes, or is this just a marketing move?
looks like they're adding an optional type system, which means you get the worst of both worlds- no guarantees AND no compile-time type checking (think: what happens if type-checked code calls non-typed code?) so I have no idea how they're going to make that fast since all types will still have to be checked at runtime
Earlier quoted context omitted.
looks like they're adding an optional type system, which means you get the worst of both worlds- no guarantees AND no compile-time type checking (think: what happens if type-checked code calls non-typed code?) so I have no idea how they're going to make that fast since all types will still have to be checked at runtime
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...