Ruby 2.1.2 is released

https://www.ruby-lang.org/en/news/2014/05/09/ruby-2-1-2-is-released/

by merrua • 12 years ago

73 25 12 years ago

ruby-lang.org

stanislavb2• 12 years ago

That's really good news. I hope the different GC issues that required tuning and patching of 2.1.1 have been fixed.

excid3• 12 years ago

Readline definitely got fixed so you no longer have to apply patches to get it to compile.

jrnkntl• 12 years ago

FYI this was released 10 days ago - https://news.ycombinator.com/item?id=7718581

stanislavb2• 12 years ago

Good point! I though I've checked ruby-lang last 10 days...

Pacabel• 12 years ago

Is there anything particularly notable about this release? The release notes make it sound quite minor, with a small handful of bug fixes.

chrisseaton• 12 years ago

These point releases are what the patch (-pNNN) versions used to be, so they are minor.

e79• 12 years ago

There are some GC bug fixes that address some edge cases.

timr• 12 years ago

It's more than just an edge case -- you're very likely to encounter the bugs that were fixed if you allocate large objects in a rails request handler. You should upgrade.

wbond3• 12 years ago

While I imagine that most Windows Ruby users already know this, I found it surprising that there still has not been an installer for Ruby 2.1 released for Windows. It appears there is at least one test failing on Windows that no one has had the time to fix.

Considering that we are almost half way to the 2.2 release date (Dec 2014), it seems like Windows support may end up becoming a second-class citizen.

venus4• 12 years ago

I'd say Windows has been a second class citizen for a long time for any of the unix-centric open source languages. Ruby, Python, even node - you're fighting an uphill battle trying to do anything on Windows.

I'm sort of amazed they've made it run at all, the systems are so different. I'd advise anyone trying to run any of these systems on Windows to use a linux VM.

toyg• 12 years ago

Ruby, Python, even node

Nope: Windows support in Python is good and well-maintained, afaik. It boils down to attention for neophytes, really, and applications in education... a field where Python has much more mindshare than Ruby or node (IMHO).

Jweb_Guru• 12 years ago

While this is true, Microsoft is making a big push to get Ruby working more equitably on its platform (for example, they had a heavy presence at Chef Conf), so I wouldn't expect this to continue indefinitely.

adrianlmm2• 12 years ago

That's why I'm switching to Owin + Nancy, It is really sad to see the lack of love Ruby on Windows gets.

threedaymonk• 12 years ago

The other side of the fence isn't much better.

Nancy's own wiki gives instructions for hosting Nancy on Ubuntu that start with downloading and compiling the latest version of Mono. They continue, "Open VS2012 and start a new console app NancyDemo.sln". Indeed, if anyone can successfully develop a Nancy application on Ubuntu, I'd love to know how. I spent two days yak-shaving NuGet (I even submitted a pull request to fix one bug) before concluding that it just doesn't work on Ubuntu.

petercooper• 12 years ago

it seems like Windows support may end up becoming a second-class citizen.

It won't end up being a second-class citizen, it already is. I wrote about this 6 years ago(!) http://www.rubyinside.com/is-windows-a-first-class-platform-... .. shortly after that I ran a panel at Euruko where I asked both the audience and Matz their opinions for Windows support and no-one really cared. It's only through the efforts of a relatively small and dedicated group of people that we have Ruby running on Windows whatsoever.

dragonwriter2• 12 years ago

It appears there is at least one test failing on Windows that no one has had the time to fix.

The failing test for test_float wasn't Windows-specific (it looks from the tracker [1] that other packagers were hitting it even though it passing on the CI system used by core, its just that Windows users are more likely to be dependent on the packager rather than building from source without running the test suite, so RubyInstaller treating it as a blocker meant more on windows than other packagers treating it that way would mean on other platforms.)

Also, there've been a number of apparent fixes (the issue was closed 5 months ago, and then again 4 months ago), before it was (hopefully, finally) resolved four days ago. Its not -- well, for the last half or so of the bugs life -- an issue of no one taking time to fix it

Considering that we are almost half way to the 2.2 release date (Dec 2014), it seems like Windows support may end up becoming a second-class citizen.

Irritating as it is for RubyInstaller users, this doesn't really seem to be a result of less attention being paid to Windows.

[1] https://bugs.ruby-lang.org/issues/8358

methehack• 12 years ago

Frankly, it should be a second class citizen. Look, MS started it by using the its lack of standards compliance as a business weapon. So, they made their choices. I'd rather see the precious resources be spent on other things.

Ruby 2.1.2 is released

Related Stories