Live data from Hacker News

Is Ruby Dying?

jmoses.co

131–140 of 159 posts

Re: Is Ruby Dying?

#131
post #124
post #120

Earlier quoted context omitted.

What does power represent to you? Simplicity and readability offer power as far as I'm concerned.

In that case Assembly language programming should be sufficient right? That's as simple and readable as it can get.

Except for the cognitive load you have to keep in your head.

Re: Is Ruby Dying?

#132

Earlier quoted context omitted.

I'm actually a big fan of Perl, but your characterization of Ruby is wrong. Ruby is Perl with object-orientation first, nicer syntax is a minor detail after that.

If Ruby has nice syntax then Smalltalk should be the syntax of the Gods ;)

The language of the Gods is clearly Lisp. Unfortunately it's such a pain to work in that most of the time the Gods just use Perl anyway. Oblig. XKCD: http://xkcd.com/224/

Re: Is Ruby Dying?

#133
post #115
post #81

Earlier quoted context omitted.

I see C and Ruby code being written every day in San Francisco.

So the bellwether of a language's health is whether it is being used in San Francisco?

To be fair I see C and C++ used all over the place. Pretty much any game out there has at worst a 50% chance of being written in C++. C is less common, but is still used quite extensively in the open source world. Most devices with firmware are written in C (or at least their drivers are).

Re: Is Ruby Dying?

#134
post #7

Earlier quoted context omitted.

What do you reckon could not be legacy code in 15 years? C family, Java, maybe Erlang?

Not the OP, but I would expect to see still widely used: * Python - As a programming language for scientists and researchers, replacing Matlab and kin. * Go or Rust - A well-designed, modern language, easier to use than C++ but almost as fast, for enterprise applications or video games. Not sure about Google, but I hope Mozilla will still be around in 10 years. * Lua? - Not sure about this one... but it fills a niche…

I'm not so sure about Lua. I'm under the impression that it's primarily used as a scripting language for games and things like that.

The language is small, it's very fast as scripting languages go, and I've heard it's easy to integrate it with C and other languages. On the other hand, it has kind of weird syntax, breaks a lot of conventions (i.e. arrays are 1 indexed), and it's not a massively well known language.

JavaScript possesses a lot of the same benefits; it's a pretty simple language, boasts very impressive performance for a scripting language, and isn't very difficult to integrate with code written in other languages. As compared to Lua's downsides, it's a bit of a mixed bag. The syntax is immediately familiar to anyone whose used an Algol derivative, the language has some unpleasant quirks, but lots of developers are accustomed to them due to the language's substantial popularity.

I imagine Lua will still be a popular choice in 5 years, but I think it's going to lose some marketshare to JavaScript.

Re: Is Ruby Dying?

#135

Earlier quoted context omitted.

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

Which financial firms? Citations? What are they doing? Sorry guys but if they are doing finance systems with perl that's a fraud.

Internal reporting for example. Perl is often used as a "glue" between different systems.

Re: Is Ruby Dying?

#136
post #91
post #26

Earlier quoted context omitted.

This is it. I'm blown away by how productive I am with rails now. A couple of weeks back I replaced an entire backend, complete with an oauth provider, record versioning, caching etc. and it took 4 hours! And all done with the usual TDD etc. This is all thanks to the gems that are available. Most of them are 2nd or 3rd generation, they're focused, battle tested and well documented. It might not be the right tool for…

Wait until you have to update your rails and all your gems are no longer compatible. Edit: removed "update for a security patch" because it's just updated. Edit: to be fair, this is a common situation with many similar solutions.

I think it's fair to say that you have to rise with the tide a bit if you're going to use rails. The projects I work on tend to be continuously developed though so this has never been a pain point.

Re: Is Ruby Dying?

#137
I have been working with Ruby and RoR for a few years now after using C# and Java. I now can put together web apps or APIs in hours vs days and integrate it with about anything out there from other APIs, using gems wrapping them or other gems for integration like redis, rabbitmq etc you name it. I have never ran into issues of incompatible gems I could not fix myself in a short period of time. It's incredible productive and reasonable fast. I am dealing with data reads/writes in the ten thousands of records per second and when something smells like bottleneck you still can throw in a native extension or use jruby and call java libs. If you are building all you do with boilerplate activerecord or other ORMS you just don't use it right. Flexibly is key. I think every challenge has it's best tools. I tried grails, play, spring mvc and other frameworks but promise that I can beat every of these frameworks in terms of development speed. Ruby is far from being dead and has a huge community. Having that said its always good to also stay up to date with other tools. For many deploying rails apps is a pain so why not throwing in warbler and deploy a war file to an app server...seconds later, boom, online and scalable. I could go on for hours:) I am a fan and so are our shareholders.

Re: Is Ruby Dying?

#138

TIOBE index for December 2013 says otherwise: http://www.tiobe.com/index.php/content/paperinfo/tpci/index.... Ruby dropped 3 spots from this time last year (currently #13); if it is dying, it's dying slowly. For my work on the JVM, Scala in comparison is way down at spot #31; Groovy #47, and Clojure doesn't even break the top 50. Meanwhile F# is kicking some serious azz, soaring 27 spots in a single year to #20, impr…

> and whatever Groovy and Clojure have planned

Groovy's roadmap just added version 2.3, featuring "_Traits_", which were actually originally announced for version 2.2 [1], but were delayed so Codehaus could get a release of Groovy out the door in time for selling seats to their annual December GrailsXchange conference in London.

In June last year, Codehaus/Pivotal had also announced a new meta-object protocol for Groovy version 3.0 [2] to come after version 2.1, but that was postponed early this year to make way for version 2.2. I don't think Groovy really has anything "planned" as you put it, rather they're reacting to external conditions.

[1] http://groovy.329449.n5.nabble.com/Adding-Trait-to-Groovy-td...

[2] http://groovy.329449.n5.nabble.com/Groovy-3-tt5710334.html

Re: Is Ruby Dying?

#139
If there is one person working on the next version of ruby it is not dead.

jruby and rubinius close the performance gaps. (This is an arguement for only knowing one language.)

Re: Is Ruby Dying?

#140
post #120
post #107

Earlier quoted context omitted.

>>easier learning curves and which are just as, if not more powerful (would be happy to learn some good reasons, though). This may be true for Ruby to some extent. But Python as a design goal aims to provide as little power to the programmer as possible. In fact, the Zen of Python says almost anything that comes in the way should and must be sacrificed to achieve readability. One can probably write a book on why one…

What does power represent to you? Simplicity and readability offer power as far as I'm concerned.

Just because Perl can parse line noise, doesn't mean you can't write readable code. I have seen very unreadable code in Python.
Post reply on HN