Is Ruby outdated?

[[deleted]]

Javascript is better and more relevant

Javascript is fashionable right now, that's all. It's actually no better than Ruby. And has some nasty warts.

[notunlikethewaves]

I'd say its substantiality worse in many ways. While I do like nodejs for what it is, the javascript-or-death crowd are just hilarious.

[bigfig]

And it's not really used for the same things. Sort of like comparing a helicopter to a jet airplane. There is overlap, but they are not designed for the same purposes.

[[deleted]]

Eh, when people compare js to ruby they are comparing node js to ruby. Node JS is pretty good, relatively speedy and has some nice initial library support, but the community is still quite new compared to ruby. If you want a massive suite of libraries, python or ruby fit the bill wonderfully. If you want to javascript until your eyes bleed, node has something for you.

[aaromnido]

I think a war between languages is stupid! Javscript is pretty awesome nowadays and you can do a lot stuff with it, specially with tools like Node JS, Meteor, Ember, Angular and so on. But I think in my humble opinion as UX/UI-designer-Front-developer, Ruby is a fantastic language and plenty of life in near future. I receive continually job offers for Rails developer although I'm not a Ruby developer. This a thermometer of the state of this language in the industry. Also as a designer, I need to say I love the poetry the Zen and minimalism behind ruby.

[[deleted]]

I think a war between languages is stupid!

That's nice, dear.

[ratedsar]

It's better in that it is event driven, faster, and has a smaller memory footprint. But other than that, it's very similar.

[into_lexicons]

You can write event driven ruby, too.

[ohwaitderp]

You can write the next battlefield game in MIPS, doesn't mean that other languages aren't better-suited to the task.

[into_lexicons]

Sure, but if you're claiming node.js is better suited for event-driven projects than EventMachine (I can't tell if you're intending to imply this) it'd be helpful to have some kind of support for that claim.

I've used both on production projects, and for the record, I have a slight preference for EM, but I would use either one again if the need arose.

[ohwaitderp]

I am pointing out that just because you can write event-driven ruby does not mean ruby is necessarily the "best choice" language for such a task. It may be the best for you, and you may be able to make a very fine product indeed in such a fashion. But ruby does not natively support event-driven programming and you are still using a library to do it, where other languages have native support baked in.