Live data from Hacker News

Ruby 1.9.3 released

blade.nagaokaut.ac.jp

11–20 of 45 posts

Re: Ruby 1.9.3 released

#11
I've never been so excited for an unstable release. 1.9.2's require was painfully slow without the patch.

edit: by "unstable", I mean a dot.uneven number.

Re: Ruby 1.9.3 released

#12
post #11

I've never been so excited for an unstable release. 1.9.2's require was painfully slow without the patch. edit: by "unstable", I mean a dot.uneven number.

A 'point release' might be the phrase you are looking for.

Re: Ruby 1.9.3 released

#13
post #9

Earlier quoted context omitted.

Yeah! I plan on to start learning Ruby.

[deleted]

Well depends on the purpose. For general tasks it's really vastly superior to most other languages.

I personally don't like some things about the syntax but that's just my personal opinion :)

Re: Ruby 1.9.3 released

#14
post #6
post #2

Does this include the "fast require" functionality that many people were patching into their Ruby 1.9.2 installs?

Maybe there was something wrong with my 1.9.2, but when working with rails projects (rake, rails console etc), this feels a few orders of magnitude faster.

Here's the whole story behind this speed-up: http://www.rubyinside.com/ruby-1-9-3-faster-loading-times-re...

Re: Ruby 1.9.3 released

#15
post #11

I've never been so excited for an unstable release. 1.9.2's require was painfully slow without the patch. edit: by "unstable", I mean a dot.uneven number.

A 'point release' might be the phrase you are looking for.

Actually, Ruby used to follows the "unstable odd, stable even" versioning scheme but they seems to quit doing that since 1.9.1 (since both 1.9.1 and 1.9.2 are declared stable[1])

[1]: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/...

EDIT: provide a source about Ruby 1.9.1

Re: Ruby 1.9.3 released

#16
post #11

I've never been so excited for an unstable release. 1.9.2's require was painfully slow without the patch. edit: by "unstable", I mean a dot.uneven number.

1.9.3 is not an unstable release. Ruby uses the third version number to represent a point release, i.e. you can expect 1.9.3 to be more stable than 1.9.2 over time.

I think that the versioning policy did work the way you describe it at one point, but it's no longer the case.

Re: Ruby 1.9.3 released

#17
post #15

Earlier quoted context omitted.

A 'point release' might be the phrase you are looking for.

Actually, Ruby used to follows the "unstable odd, stable even" versioning scheme but they seems to quit doing that since 1.9.1 (since both 1.9.1 and 1.9.2 are declared stable[1]) [1]: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/... EDIT: provide a source about Ruby 1.9.1

Good to know! I didn't realize 1.9.1 was considered stable.
Post reply on HN