| Welcome to Samsara | |||||
|
Huh? What?
Subscribe
Links |
Fri, 10 Nov 2006 I noticed Charles Nutter (one of the JRuby developers) mentioning that the fork() method in JRuby will most not likely be supported: We would strongly prefer to avoid any implementation that requires fork, since we can't really support fork in JRuby. While I can understand the difficulties in the Java VM giving lots of hell trying to handle something like fork() I feel it's a shame since it means if you use fork and quite a few process related calls in Ruby it will not be portable in JRuby. For a sysadmin, handling processes is one of their jobs so personally, I hope they can come up with some way to handle it somehow. But JRuby's strengths might not be in a scripting language for sys admins but providing a way to integrate rails with the monster that is J2EE. How cool would it be to develop a rails application all in the context of a java web application that you can just deploy right into a Java application server? I think this could be JRuby's little nitch (besides being an integration tool for java devs) Fri, 27 Oct 2006
If you're a Debian or Ubuntu user you'll find that the Ruby standard distribution is split into lots of little packages so doing something like apt-get install ruby only gives you the ruby binary and a subset of the libraries for Ruby. You'll need to add more packages if you want to utilize more of Ruby's standard library. This is all in order to comply with Debian packaging Guidelines. That is all well and good but a little frustrating when you 'just want to do work'.
For example, I wanted to install
sys-proctable
(Something I really believe should be in Ruby's standard distribution)
however ran into the following:
To get around this you will need to install ruby1.8-dev (or ruby1.6-dev or whatever version of ruby you're running) to get mkmf.rb which is listed in the Ruby Standard Library. I'm sure most Ruby hackers worth their salt consider this a 'duh' thing but not of all of us can be shining stars in the Ruby community
How I fixed it...
Bruce Eckel of Thinking in Java fame takes a second look at Ruby. This time he has far less harsh words than his previous look at it (Note that the original post that Eckel made on Ruby seems to be MIA on his website. I'm a little miffed at that...) His second time around he seems a little more impressed but I have to agree with some readers who pointed out that if he bothered to read the Pickaxe book he would have found a good portion of these features in Ruby. Although for a counterpoint, I've tried reading some comparisons of Python and Ruby and most of them end up in a 'mine is bigger' argument rather than try to really see what is different. Mr. Eckel has spent some time summarizing the differences. The reason it's easier to believe him is because he is staunch follower of Python. Tue, 17 Jan 2006
I had a problem with a windows-based install of Ruby with RubyGems kept screwing up my cygwin-based installation of Ruby. Seems this is a 'well-known' problem in the Ruby community. The symptons look like this
$ irb Really annoying. To fix this unset the RUBYOPT environment variable in your cygwin shell's setting. The manual way to do this in bash is shown:
$ unset RUBYOPT |
||||