Recently, I actually started to learn the Ruby spec because I was offered a well paid work in Ruby for many months to come, and I thought it would be cool to work in something new. Besides web dev, my past is C/C++, then many years of Java, and recently Node.js. I turned the Ruby project down because very early down the spec I realized that I don't want to work with technology belonging to 5 (or at least 2) years ago, language design-wise. I'm now on Node and I have great fun. The JS community is great, the Node.js subset even greater. The NPM repository is exploding with new libraries. You can see a new framework literally every week, but you also have tested ones to rely on. Good patterns are taken from anywhere, anytime, and new ones are being created. I'm not saying this to bash Ruby, it's just my personal story. I approached Ruby with optimism, but what I saw was a badly designed language. I can understand it being so popular compared to Java, I know I would be Ruby coder today had I discovered it during my Java days. But today I have Node.
You refused a ruby job because the language (Ruby) was "5 (or at least 2) years old language design wise" and instead you went for.... node.js? Technology based on a language designed...17 years ago!? (God that makes me feel old)
I feel there is a flaw in your reasoning, or at least other reasons which you are not going into.
EDIT: I know ruby has been around a long time. Just found it first appeared around the same time as JavaScript.
I turned the Ruby project down because very early down the spec I realized that I don't want to work with technology belonging to 5 (or at least 2) years ago, language design-wise.
Ah, so you don't want to work with mature, proven technologies, language design-wise, that bring benefits to the company and the user base.
Good thing that you don't WANT to work with this kind of technology, because I too don't think you SHOULD be working anywhere near client projects with that mentality.
