What's New in Ruby 2.1 [pdf]

#1

Post by gcv » Wed, Nov 27, 2013, 2:58 PM UTC

Re: What's New in Ruby 2.1 [pdf]

#2

Post by conorh » Wed, Nov 27, 2013, 3:24 PM UTC

I really like the ObjectSpace.trace_object_allocations addition. I had a quick look at the 2.1 docs for ObjectSpace and there seem to be all sorts of interesting methods in there reachable_objects_from(obj) and memsize_of(obj) for example. It looks like understanding memory usage and tracking down memory leaks will get a lot easier with 2.1.

http://ruby-doc.org/stdlib-2.1.0/libdoc/objspace/rdoc/Object...

Re: What's New in Ruby 2.1 [pdf]

#3

Post by taylorfausak » Wed, Nov 27, 2013, 4:12 PM UTC

I'm looking forward to `def` returning a symbol (page 11).

    private static void def main(args) ...; end

Re: What's New in Ruby 2.1 [pdf]

#4

Post by cmaggard » Wed, Nov 27, 2013, 4:15 PM UTC

It's unclear from the intro summary, but I'm assuming from the lack of further explanation that refinements are just GONE, and not just "no longer experimental"?

Re: What's New in Ruby 2.1 [pdf]

#5

Post by matsadler » Wed, Nov 27, 2013, 4:16 PM UTC

conorh wrote: post #2

I really like the ObjectSpace.trace_object_allocations addition. I had a quick look at the 2.1 docs for ObjectSpace and there seem to be all sorts of interesting methods in there reachable_objects_from(obj) and memsize_of(obj) for example. It looks like understanding memory usage and tracking down memory leaks will get a lot easier with 2.1. http://ruby-doc.org/stdlib-2.1.0/libdoc/objspace/rdoc/Object...

#reachable_objects_from was added in 2.0, and I think #memsize_of was introduced in one of the 1.9 releases. The documentation is new though.

I wrote a little about them here: http://globaldev.co.uk/2013/03/ruby-2-0-0-in-detail/#id6

Re: What's New in Ruby 2.1 [pdf]

#6

Post by jameskilton » Wed, Nov 27, 2013, 4:19 PM UTC

cmaggard wrote: post #4

It's unclear from the intro summary, but I'm assuming from the lack of further explanation that refinements are just GONE, and not just "no longer experimental"?

Nope, by "no longer experimental" they are now officially in the core language. More information here: http://rkh.im/ruby-2.1

Re: What's New in Ruby 2.1 [pdf]

#7

Post by cmaggard » Wed, Nov 27, 2013, 4:26 PM UTC

jameskilton wrote: post #6

cmaggard wrote: post #4

It's unclear from the intro summary, but I'm assuming from the lack of further explanation that refinements are just GONE, and not just "no longer experimental"?

Nope, by "no longer experimental" they are now officially in the core language. More information here: http://rkh.im/ruby-2.1

Ah, well that's something then. Thanks for the clarification.

Re: What's New in Ruby 2.1 [pdf]

#8

Post by danso » Wed, Nov 27, 2013, 4:44 PM UTC

Everytime I read a Ruby version announcement/explanation, it reminds me that I've been a coder working and thinking exclusively in English, but my current programming language of choice is prominently steered by non-English speakers...and somehow things work pretty peachy. But it always makes me wonder how much more in-depth and richer the discussion of Ruby amongst its Japanese maintainers, before they translate it for us in English?

Re: What's New in Ruby 2.1 [pdf]

#9

Post by thinkbohemian » Wed, Nov 27, 2013, 4:49 PM UTC

Koichi is gives some of the best presentations. It is hard enough to be funny in one language, yet to be funny and understandable in two is quite an accomplishment. If you're ever at a Rubyconf, go to his talks. Also love the speed work he's been doing with generational GC. For a primer, Pat Shaughnessy has a great talk you should check out, also Ruby Under a Microscope is a good dive into Ruby.

Re: What's New in Ruby 2.1 [pdf]

#10

Post by ngcazz » Wed, Nov 27, 2013, 4:59 PM UTC

taylorfausak wrote: post #3

I'm looking forward to `def` returning a symbol (page 11). private static void def main(args) ...; end

That slide was a bit confusing for my underslept mind. Is that meant as an example of calling methods which work over the result of defining main (in this case static and void)?