Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Is Ruby Dying?

jmoses.co

Post reply on HN
Print view View original

41–50 of 159 posts

Re: Is Ruby Dying?

#41

Post by dham »

NodeJS, been there done that. Even with generators it makes doing task synchronously a royal pain(have you ever tried to write sql update code with transactions?). Until something comes a long to replace Ruby(https://github.com/mirah/mirah looks promising), I'll still use it. Ruby is a great scripting language, and it has one of the best(if not the best), web frameworks out there.

I definitely think MRI will die, and Ruby will live on in the JVM. I've been really impressed with JRuby and the advances they have made on that project.

Plus you also have projects like RubyMotion and the promising Opal(Ruby to JS).

Re: Is Ruby Dying?

#43

Post by hahainternet »

sim0n wrote: post #39
bmj wrote: post #32

Earlier quoted context omitted.

What about Catalyst? Or Mojolicious? Or Dancer? If it's just used in legacy code, why are there still healthy frameworks being produced (granted, these aren't as popular as Rails, but, Perl on the web is hardly in legacy mode)?

I personally haven't seen any new code being written in Perl during either my time in England or in the Bay Area. I don't really see a reason to use Perl when there are languages like Python and Ruby out there with easier learning curves and which are just as, if not more powerful (would be happy to learn some good reasons, though).

I am in Manchester. I write new Perl code. Python is Perl with a little nicer syntax and a shitload of baggage from overly opinionated people. Ruby is Perl with a little nicer syntax and no other advantages.

I have found no compelling reason to switch, and lots of annoyances that don't seem to exist in Perl.

Re: Is Ruby Dying?

#44

Post by Confusion »

sjtgraham wrote: post #14
nathos wrote: post #8

Earlier quoted context omitted.

http://en.wikipedia.org/wiki/Betteridge's_law_of_headlines

Citing this is such a knackered HN cliché it should mean an instant hell-banning.

Complaining about a "knackered HN cliché" is itself a knackered HN cliché. Recurse.

Re: Is Ruby Dying?

#45

Post by mitchty »

thomasfedb wrote: post #25

Ruby is only dying in the sense that C is dead. It's not that exciting, but instead is widely used, including by companies. Additionally, I doubt gem releases correlate with language 'vitality'. Fewer releases may simply indicate library stability.

Too true, I'm writing more C lately than ruby. Then again I'm not a rails fan and I need to interface with ioctls more than oauth or whatever. So C fits much better in my domain space.

That and command line apps in ruby, well there like perl with cpan modules, sheer pain to manage across systems. Versus static link in archive files and make a package.

Re: Is Ruby Dying?

#46

Post by bgilroy26 »

makomk wrote: post #28
jerf wrote: post #4

You just may not be used to Ruby not having the exciting fire of initial hype. That is dead. But that's good. Languages can't live like that forever. Sooner or later they need to stop the wild experimenting, find some best practices and things that work, and settle down and ram home the things that work. Ruby has entered final maturity. It will be in that phase until such time as it really does die, which could well…

I think Perl has already reached the state where it's mostly used in legacy code, at least for web development.

NYC financial firms are starting new projects all of the time where Perl is the main tool for feeding information here from over there.

Re: Is Ruby Dying?

#49

Post by mortyseinfeld »

Sanddancer wrote: post #13

First off, popularity of a language shouldn't be as important as you seem to make it in starting a project. Finding the right tool for the job should be much much more important, new kid in town be damned. Second off, number of package releases doesn't tell much about maturity of packages, developer involvement, or anything. Ruby's a mature language. It's quite feasible, and arguably desirable, for package releases t…

First off, popularity of a language shouldn't be as important as you seem to make it in starting a project

Very wrong. There are languages that I believe I would be very productive in, but can't justify the time investment because the community is so small that the related tools/libraries/frameworks aren't there.

Re: Is Ruby Dying?

#50

Post by riffraff »

Glyptodon wrote: post #16

I didn't start using Ruby (or Rails) until this year. The language is nice and makes my top 3 language list. That said, I find both Python/Django and Node.js both more productive than Rails for quickly building API-driven web-apps. More so this has to do with Rails, which has a number of warts and a tendency to require excessive configuration for all its pretty much patently false 'convention over configuration' spie…

> patently false 'convention over configuration' spiels

such as ?

Rails has plenty of warts but models still live in /app/models, classes are named after tables and all CRUD routes are defined with a single two-token line.

You are probably forgetting to consider what the world was like before this.

Post reply on HN