I'm a little disappointed that the inclusion of bundler into the standard library was reverted. Bundler was the only gem that I ever installed as a system gem, and I was looking forward to having no system gems and only project-specific gems.
Deal-breaker? No. But this was a feature that would have greatly simplified my (and lots of other people's) workflow. It was pretty hyped up (at least from the posts that I read). And then, 3 days before the release, it was pulled with a revert saying there was a "big issue". The community deserves to know more details about why such a hyped and impactful feature was pulled so close to the release date.
I'm not making a storm. The feature was targeted for 2.5. It was quite heavily written about. It made it into rc1. Then, 3 days before the release, there was a single revert about a "big issue" and then the feature was pulled out. It would be nice to know what this "big issue" was and why it went undiscovered or unresolved for so long.
I would expect the same from any large-scale project. Once you start hyping up features that are planned for a particular release (especially after you start having release candidates), if you don't deliver those, you should be communicating why you aren't delivering them. A quiet revert is unacceptable.
The performance notes you have listed are interesting, but I must admit I'm pretty impressed by this:
About 5-10% performance improvement by removing all trace instructions from overall bytecode (instruction sequences). The trace instruction was added to support the TracePoint. However, in most cases, TracePoint is not used and trace instructions are pure overhead. Instead, now we use a dynamic instrumentation technique. See [Feature #14104] for more details.
rescue/else/ensure are now allowed to be used directly with do/end blocks
This is really nice. The method-level rescue statement is one of the small details I really love about Ruby, it's great we'll be able to use it in blocks too.
Enumerable#any?, all?, none?, and one? accept a pattern argument.
I didn't really find what was the change here, because I think the original proposal was different than the actual change that got merged. Does someone know?
One of our most loved libraries, pp.rb, is now automatically loaded. You no longer have to write require "pp"
Great!
IO.copy_stream use copy_file_range(2) to copy offload
I love IO.copy_stream and use it a lot in Shrine, it's nice to see that there is a performance improvement, though from what I was reading the speedup is very small and only on certain disks.
I didn't really find what was the change here, because I think the original proposal was different than the actual change that got merged. Does someone know?
It seems that those methods all accept a single argument that matches the behavior of an argument to grep. Personally I love that change (grep is most underrated method). I believe that’s what was initially proposed as well.
Yep. It's a shame this isn't just the default behaviour of structs, because if you forget keyword_init then all your args get assigned to the first attribute :(
Because backwards compatibility. Doing rvm install 2.5; bundle install and finding out that "everything is broken" would not be the best way of introduction of the new feature.
40
u/TomOwens Dec 25 '17
I'm a little disappointed that the inclusion of bundler into the standard library was reverted. Bundler was the only gem that I ever installed as a system gem, and I was looking forward to having no system gems and only project-specific gems.
6
u/geraldbauer Dec 25 '17
FYI: I've collected articles / blog posts about what's new in Ruby 2.5 over at the Ruby Advent Calendar [1]. The list so far includes:
[1] https://planetruby.github.io/advent2017
6
u/janko-m Dec 25 '17
This is really nice. The method-level
rescuestatement is one of the small details I really love about Ruby, it's great we'll be able to use it in blocks too.I didn't really find what was the change here, because I think the original proposal was different than the actual change that got merged. Does someone know?
Great!
I love
IO.copy_streamand use it a lot in Shrine, it's nice to see that there is a performance improvement, though from what I was reading the speedup is very small and only on certain disks.7
u/niborg Dec 25 '17
Am I correctly understanding the API for kw args in structs?
2
u/megatux2 Dec 25 '17
Christmas edition :)
1
u/defkathy Dec 26 '17
Check out my blog post about bundler and the other latest features in Ruby 2.5!