As always, the answer to posts with a question as the title, is no.
Is Ruby Dying?
111–120 of 159 posts
Re: Is Ruby Dying?
#112Earlier 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.
The Rails team generally provides patch files for security updates, specifically so that if upgrading Rails is not possible for you, you can just patch your Rails. Especially thanks to Bundler, it's quite easy: http://blog.steveklabnik.com/posts/2012-10-04-run-rails-with...
It's true that if you're running a _very_ old version of Rails, you may not get a patch. There are community projects like Rails LTS that help with this, though.
Re: Is Ruby Dying?
#113Earlier quoted context omitted.
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.
Which financial firms? Citations? What are they doing? Sorry guys but if they are doing finance systems with perl that's a fraud.
Re: Is Ruby Dying?
#114Earlier 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 ;)
Remember we are comparing to Perl ;)
Re: Is Ruby Dying?
#115Earlier quoted context omitted.
By this measure, C, or C++, or Ruby must be dead, since I've not seen any new code written in it during my 13 years in the industry. That said, I suspect there are fewer people picking up Perl for the first time for a project these days. My experience with it has always been driven by some degree of "legacy"--someone on the team has experience with the language, and has leveraged CPAN to solve problems. Perl is still…
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?
Re: Is Ruby Dying?
#116Earlier quoted context omitted.
I think Perl has already reached the state where it's mostly used in legacy code, at least for web development.
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)?
>What about Catalyst? Or Mojolicious? Or Dancer?
Yes, what about them? First time I heard of them, and I frequent more than 5 tech sites such as HN.
>If it's just used in legacy code, why are there still healthy frameworks being produced
Because it's very easy to produce a web framework, everybody and his dog has created one (that, or a blog engine). That doesn't make those freameworks "healthy").
Re: Is Ruby Dying?
#117Earlier quoted context omitted.
C# is held back by windows "The enterprise" (for the most part) isn't held back by Windows. That's just reality.
> "The enterprise" (for the most part) isn't held back by Windows. Or, rather, much of "the enterprise" is committed to being held back by Windows, so a language being tied to windows doesn't hinder enterprise adoption.
Except Windows Server works fine.
Re: Is Ruby Dying?
#118TIOBE 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…
I used to look at the TIOBE index all the time, until I saw Visual Basic .NET jump a bunch of spots this year. I then started to question either TIOBE index or the people that are using Visual Basic.NET
Not sure what to say about TIOBE. It bases its results on search engine trends.
They can't really tell the difference between Ruby(The stone) and Ruby(The language). Or Python(The snake) and Python(The language).
Re: Is Ruby Dying?
#119Earlier 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.
For any categorical statement like that, there will be hold-out niches where it doesn't apply yet . Hell, I'm sure there are some banking types who are starting new projects in COBOL.
Except that programming is such a large domain, you could easily classify web development as a niche itself.
Vast majority of the programming community doesn't have to ever deal with a HTML tag ever.
Re: Is Ruby Dying?
#120Earlier quoted context omitted.
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).
>>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.