News for hackers. Stuff that matters.
Re:Is Ruby Dying? by jerf on Tuesday December 24, 2013 @09:14AM (#6959390)
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 be 10-15 years. Or more, though, honestly, I doubt that in 2028 we'll be considering Ruby anything more than legacy code... that's not because of Ruby itself, but rather the language category it is in. I expect we'll be looking at Python and Perl the same way.

Oh, and kudos for running numbers before simply writing the "Ruby is dying!" blog post!

Re:Is Ruby Dying? by ollysb on Tuesday December 24, 2013 @09:35AM (#6959476)
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 every job but it's damn good at what it does. If the noise has died down it's because we're busy knocking out great apps.
Re:Is Ruby Dying? by taude on Tuesday December 24, 2013 @11:06AM (#6959853)
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.

Re:Is Ruby Dying? by steveklabnik on Tuesday December 24, 2013 @11:44AM (#6960055)
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? by ollysb on Tuesday December 24, 2013 @04:18PM (#6961159)
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? by makomk on Tuesday December 24, 2013 @09:36AM (#6959480)
I think Perl has already reached the state where it's mostly used in legacy code, at least for web development.
Re:Is Ruby Dying? by bmj on Tuesday December 24, 2013 @09:44AM (#6959504)
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)?
Re:Is Ruby Dying? by sim0n on Tuesday December 24, 2013 @09:55AM (#6959541)
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).
Re:Is Ruby Dying? by hahainternet on Tuesday December 24, 2013 @10:04AM (#6959580)
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? by Demiurge on Tuesday December 24, 2013 @10:29AM (#6959692)
Following this logic, every language is Perl with a bit of this or that. Perl was one of the first of the kind, but people saw obvious problems with it and so they innovated with 'little nicer syntax' or 'little better object system'. You might not want any of this, but you can't deny most people are happier with Python or Ruby.
Re:Is Ruby Dying? by aaronem on Thursday January 02, 2014 @03:48PM (#7002164)
I'd say it's more like Perl is every language with a bit of this or that. A sufficiently "skilled" Perl hacker can write everything from bad C, to bad Lisp, to bad Fortran, in Perl -- and most certainly can write plenty of bad Perl in Perl, too. It's writing good Perl that's hard.
Re:Is Ruby Dying? by hahainternet on Wednesday December 25, 2013 @02:16PM (#6963896)
You're not wrong, but I wrote that from my perspective, as someone who primarily writes Perl and needs a compelling reason to switch. Obviously someone who was writing code pre-Perl will probably see things a different way.
Re:Is Ruby Dying? by kamaal on Tuesday December 24, 2013 @11:01AM (#6959827)
This is true for all language that do things right the first time.

If you learn C well, everything else(C based languages) look the very same.

Perl enjoys that first movers advantage.

Re:Is Ruby Dying? by collyw on Wednesday December 25, 2013 @08:06AM (#6962925)
There was a talk by Guido Van Rossum effectively saying that Perl, Python and Ruby are the same language.
Re:Is Ruby Dying? by dasil003 on Tuesday December 24, 2013 @11:10AM (#6959874)
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.
Re:Is Ruby Dying? by hahainternet on Wednesday December 25, 2013 @02:17PM (#6963900)
It's the only major detail to me, because I can do the majority of what I would use in Ruby, in Perl. Nicer syntax is something I can't do though.
Re:Is Ruby Dying? by dasil003 on Thursday December 26, 2013 @10:02AM (#6966430)
If you can constrain yourself a reasonable OO system in Perl why can't you constrain yourself to a nice subset of the syntax?
Re:Is Ruby Dying? by hahainternet on Thursday December 26, 2013 @10:21AM (#6966489)
I can, I can deal with overly verbose maps or shifting variables off @_ but Ruby provides some similar features to Perl 6 right now. That is an advantage on its part. It's just not compelling enough to make me switch as Perl can do most of the rest just fine.
Re:Is Ruby Dying? by chromatic on Wednesday December 25, 2013 @04:04PM (#6964238)
See the CPAN module Moops.
Re:Is Ruby Dying? by hahainternet on Wednesday December 25, 2013 @06:39PM (#6964715)
I'm thinking more of things like the p6 arrow. Moops is part of the first part, things I can already do in Perl that are in Ruby.
Re:Is Ruby Dying? by lowmagnet on Tuesday December 24, 2013 @01:40PM (#6960557)
Ruby also now has a VM, which people may or may not find more useful. I for one prefer Ruby 1.9.x to 1.8.x.
Re:Is Ruby Dying? by ossdev1 on Tuesday December 24, 2013 @11:41AM (#6960036)
If Ruby has nice syntax then Smalltalk should be the syntax of the Gods ;)
Re:Is Ruby Dying? by orclev on Tuesday December 24, 2013 @02:00PM (#6960633)
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? by dasil003 on Tuesday December 24, 2013 @11:47AM (#6960066)
Remember we are comparing to Perl ;)
Re:Is Ruby Dying? by rubiquity on Tuesday December 24, 2013 @10:58AM (#6959819)
Having written some Python I agree. Having written a lot of Ruby I disagree.
Re:Is Ruby Dying? by delluminatus on Tuesday December 24, 2013 @11:11AM (#6959877)
Can you elaborate on Python's baggage? I'm simply curious.
Re:Is Ruby Dying? by hahainternet on Wednesday December 25, 2013 @02:19PM (#6963909)
I wouldn't characterise myself as any sort of expert so really I'm just talking about minor things like ternary operators, ugliness with super, scoping, the annoyance of PEP8 being overly specific etc. Just decisions taken for the sake of 'correctness' that end up being annoying.

Python isn't so bad, decorators and importing is all very swanky. I find that in general though things tend to be less elegant than intended but the delusion of perfection is maintained. I oppose Python's core philosophy and having used a bunch of Django, that also soured me a bit.

Re:Is Ruby Dying? by bmj on Tuesday December 24, 2013 @10:37AM (#6959726)
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 my go-to "glue" and tooling language, but that's just because what I know. Would Ruby work? Yeah, probably, but I've not found it to be worth it to learn that language yet.

Re:Is Ruby Dying? by sim0n on Tuesday December 24, 2013 @10:55AM (#6959803)
I see C and Ruby code being written every day in San Francisco.
Re:Is Ruby Dying? by bmj on Tuesday December 24, 2013 @11:49AM (#6960071)
So the bellwether of a language's health is whether it is being used in San Francisco?
Re:Is Ruby Dying? by orclev on Tuesday December 24, 2013 @02:05PM (#6960653)
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? by smonff on Wednesday December 25, 2013 @09:34AM (#6963050)
Just ask http://www.builtinperl.com/ for the reasons why. For exemple don't you know that DuckDuckGo is using a lot of Perl ?

Another one, that is huge : YouPorn (itself) is using Catalyst. YOU-PORN!

In my opinion, the main Perl's strength is the cpan.org :

  Stop reinventing wheels, start building space rockets
  
  The Comprehensive Perl Archive Network (CPAN) 
  currently has 128,529 Perl modules in 28,883
  distributions, written by 11,129 authors, 
  mirrored on 266 servers.
  
  The archive has been online since October 
  1995 and is constantly growing.
Re:Is Ruby Dying? by Mic92 on Wednesday December 25, 2013 @12:35PM (#6963526)
Actually youporn, rewrote all their code in PHP:

http://highscalability.com/blog/2012/4/2/youporn-targeting-2...

Re:Is Ruby Dying? by smonff on Wednesday December 25, 2013 @08:30PM (#6964943)
Damned ! Here is an information that should be uploaded to Wikipedia.
Re:Is Ruby Dying? by kamaal on Tuesday December 24, 2013 @11:31AM (#6959988)
>>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 must use Perl. In short, nothing really gets work done as Perl does. That one fact hasn't changed since the past 26 years of Perl's existence.

Re:Is Ruby Dying? by elbear on Tuesday December 24, 2013 @12:06PM (#6960133)
What does power represent to you? Simplicity and readability offer power as far as I'm concerned.
Re:Is Ruby Dying? by collyw on Wednesday December 25, 2013 @08:02AM (#6962921)
Just because Perl can parse line noise, doesn't mean you can't write readable code. I have seen very unreadable code in Python.
Re:Is Ruby Dying? by kamaal on Tuesday December 24, 2013 @12:35PM (#6960242)
In that case Assembly language programming should be sufficient right? That's as simple and readable as it can get.
Re:Is Ruby Dying? by lowmagnet on Tuesday December 24, 2013 @01:56PM (#6960607)
Except for the cognitive load you have to keep in your head.
Re:Is Ruby Dying? by coldtea on Tuesday December 24, 2013 @11:51AM (#6960081)
>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? by bgilroy26 on Tuesday December 24, 2013 @10:07AM (#6959597)
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? by regularfry on Tuesday December 24, 2013 @10:11AM (#6959615)
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.
Re:Is Ruby Dying? by kamaal on Tuesday December 24, 2013 @12:05PM (#6960129)
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? by ossdev1 on Tuesday December 24, 2013 @11:46AM (#6960063)
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? by vadman on Tuesday December 24, 2013 @03:31PM (#6961028)
Internal reporting for example. Perl is often used as a "glue" between different systems.
Re:Is Ruby Dying? by Moto7451 on Tuesday December 24, 2013 @12:10PM (#6960147)
I work at a Perl based startup and we're writing new code and designing new systems all the time. There seems to be quite a few Perl shops in LA though most of them have been around for a long time.
Re:Is Ruby Dying? by jboggan on Tuesday December 24, 2013 @01:38PM (#6960552)
Perl's my mother tongue (started in bioinformatics) but I've been doing a lot of Ruby at my current gig in LA. That being said, I miss Perl's syntax and autovivification. I did a hackathon project with Perl at work, and my punishment for winning was porting it to Java for production.

Drop me a line Moto7451, I'm always interested in meeting local (Perl) hackers.

Re:Is Ruby Dying? by polysics on Tuesday December 24, 2013 @09:16AM (#6959395)
What do you reckon could not be legacy code in 15 years? C family, Java, maybe Erlang?
Re:Is Ruby Dying? by jerf on Tuesday December 24, 2013 @09:40AM (#6959487)
I expect the JVM to still be going; at least one of Clojure or Scala will probably continue growing for a long time, and there's room for both. It's also possible another Algol-esque language that isn't Java, but is syntactically closer to Java, making people more comfortable, will arise. At some point one of them may even become the "primary" JVM language, with Java hanging on as legacy, but due to the fact Java just compiles to the JVM, there won't be any reason to get rid of it, as the maintenance effort is virtually 0. I expect C# to probably still be going. I'm not sure anything can actually kill C, even though something really should.

C++ I can see going either way; it is a freakishly complicated language (and getting more complicated with every standard that comes out) that IMHO was primarily kept aloft by being the "default" language in Windows for a very long time. I expect Rust will be most of the way through eating it alive in 15 years. Or something like Rust, but Rust is looking pretty solid. And if you want a multithreaded systems language... and you will... I suspect in practice it's going to be an order of magnitude easier to program in than C++ in another three or four years. Maybe Rust will even be eating C. (About damn time!) Someone will probably be writing an OS kernel in Rust. Possibly one that is driver-compatible with Linux, or even just straight-up a Linux-compatible kernel.

If Google doesn't drop the ball, Go will probably be mature and still going, and probably the primary reason why Ruby and friends are considered legacy code. Go even today very nearly replaces the scripting languages in flexibility (though definitely not quite), but brings back stronger typing and better performance. A few more tweaks to it over the next 5 years and it'll be hard to see why I'd start a new project in a "scripting" language. (Part of the reason I think this is that I observe that in the past 15 years, no language has penetrated into the A-list without some sort of major corporate backer. While there's plenty of other possibilities from a technical point of view, and while Google is not very aggressively pushing Go, I still think it's more support than any other language has or is likely to have in the near future. Even if they just passively continue to do little more than employ the authors, this is likely to continue floating up the ranks.)

And I still sort of expect something to come up that is not Haskell, but is closer to Haskell than anything currently existing. Or possible Haskell simply keeps plugging along and manages to become a very solid B-list language. I doubt it'll ever break into the A-list "nobody got fired for choosing C/C++/Java/C#" level of popularity, but it might settle firmly into where "it's pretty hard to get fired for choosing Python/Ruby/PHP" is today. (It's brushing B-list status now, but it's got a ways to go before I'd call it solid B-list.) I also think there's a good chance it will acquire a reputation as being the tool of choice for tackling truly complicated systems. (Though Rust will eat into the bottom end of that a bit too, they're currently retreating from some of the tools that Haskell has that may allow it to acquire this reputation. I think Haskell will still retain a strong advantage here.)

And finally, some sort of wildcard. 15 years ago I doubt anybody would have predicted Haskell being where it is now, even Haskell users (if you can even call it the same l. New languages shall continue to bubble and froth, but at least one and probably two will either emerge from the froth and become a B-list language. Probably at least one of them will be a aggressively "practical" language that will be a reaction to the success of "excessively-academic" Clojure, Scala, Rust, and the Haskell-like I hypothesize above, and follow a hype curve very similar to Ruby or Node.

It occurs to me I'm looking more like 10 years into the future here than 15. Oh well. Close enough. I'm also well aware I'm just talking out my ass; I completely expect to look back and laugh at this in 10 to 15 years. Oh well again.

Re:Is Ruby Dying? by danielrhodes on Tuesday December 24, 2013 @10:51AM (#6959785)
I like Go, but in my opinion it is not an appropriate language for building web applications. It makes for great sub-components of a larger stack which are focused and do relatively low-level tasks (networking, file serving, caching, etc.). It is also great for scripting where you need easy out-of-the-box concurrency.
Re:Is Ruby Dying? by rubiquity on Tuesday December 24, 2013 @11:09AM (#6959867)
This times a million. I think Go is awesome for a little bit of systems programming but I'd pull my hair out trying to make a robust Web application with it. I feel the same way about Node.js. I wouldn't use either of these for a public facing HTTP application but if I needed some hyper performant internal system using RPCs then I would use them.

Ruby's DSLs for writing things that Web application's need (serving HTML) are bar none the best. If I'm writing something that is serving HTML, I'm using Ruby all day, every day.

Re:Is Ruby Dying? by patrickaljord on Thursday December 26, 2013 @05:11AM (#6965831)
Have you given martini a try?https://github.com/codegangsta/martini
Re:Is Ruby Dying? by lstamour on Tuesday December 24, 2013 @10:45AM (#6959758)
For a Google-backed language to replace Rails, Golang has less of a shot IMHO. Mainly because the popularity of Rails stemmed initially from TextMate in the original screencasts. It'd be silly to say that's all that mattered so I'm going to merely strongly imply that without additional books or cookbooks, screen casts, etc. it's hard to see Golang taking off in a community that isn't already invested in learning it. Those looking for more stability will pick a JVM-based language, which includes JRuby, and call it a day.

If I had to then pick a replacement, I would argue for Dart. Dartlang has a much stronger set of novice documentation, nodejs-like magic of running in client and server, but advanced Google mojo like support for SIMD. All Dart really needs is Chrome support and a decent "Rails" clone to popularize server-side development. We're a few years off, but Dart could be quite exciting. Or it could end up running on the JVM like everything else :p

Re:Is Ruby Dying? by jerf on Tuesday December 24, 2013 @10:58AM (#6959818)
"For a Google-backed language to replace Rails"

It's not "replacing Rails", it's replacing new projects in what are today scripting languages (Perl, Python, Ruby, PHP, etc.).

I see fewer people talking about Dart than I see doing things with Go. That said, I did finally beat Google Trends into producing [1], which is interesting. It was hard to convince Trends to show Dart as growing as quickly as Golang, though, so there may be a selection effect (of the several graphs I produced with Dart well behind Golang, this is the only one that shows them even tied), and it still shows Dart as tied with Go, and Go's growth being more steady. I'm still not sure Dart is growing like Go is.

I suppose I should point out that the predictions were my best guesses about what will happen, and do not simply reflect what I "want" to happen.

[1]: http://www.google.com/trends/explore#cat=0-5-31&q=dart%2C%20...

Re:Is Ruby Dying? by lstamour on Tuesday December 24, 2013 @11:13AM (#6959888)
Go's been out 4 years while Dart just hit 1.0 and requires a runtime as it's a bit less portable. Once Dart lands in Chrome, I can easily imagine it becoming the first choice of developers who prefer to develop code in their browser. A niche market now, but interesting to contemplate.

I'm a bit more flexible when it comes to trying to predict the future than my posts indicate. I'm just offering an alternative hypothesis: Dart has many more screencasts and supported libraries from Google, including Angular.dart than Golang ever had, and it's only just hit 1.0. Golang has been fantastic for me to develop with, particularly on Google AppEngine and it's true Dart hasn't hit server-side popularity yet. But if we're predicting the future, based on JS and node.is alone, I'd suggest Dart has plenty of room to gain popularity quickly.

Re:Is Ruby Dying? by jerf on Tuesday December 24, 2013 @11:18AM (#6959921)
Oh, I see, that makes sense.

For me, I was making broad predictions. No matter how exciting the web client dev is, it is and will remain still a niche, and Dart faces a huge challenge in the next 5 years as asm.js will relatively suddenly introduce it to competition from every other mainstream language in existence. Dart probably won't "die" for a while, but I'm not sure it won't end up "just another" one of the enormous pile of languages that it will be possible to do client-side programming in.

Re:Is Ruby Dying? by lstamour on Tuesday December 24, 2013 @01:10PM (#6960407)
I've learned to not bet against the ingenuity of Google engineers, particularly those building web browsers and development tools. :) Given that they've added very basic support for editing to Developer Tools in Chrome already, once Dart lands in Chrome, I could see a push to make Chrome the editor-of-choice for Dart, if not web-based editors in general. And it's true, there's more to development than type-and-run interactive shells, but that sure makes web development easier, doesn't it? asm.js benefits Dart as well, since they can target the same approaches for their JS target code gen.

The real question is when will Google add development alternatives to Android? Chrome's nice, but it takes a mobile platform to sustain an ecosystem of client-side developers these days. Perhaps Chrome-on-Android will eventually become the new PhoneGap?

Re:Is Ruby Dying? by dham on Tuesday December 24, 2013 @10:49AM (#6959771)
AFAIK Dart still does not have generators. I want to like Dart but if puts me in the same boat as Javascript does on the server, then NO.
Re:Is Ruby Dying? by steveklabnik on Tuesday December 24, 2013 @10:51AM (#6959781)
> Someone will probably be writing an OS kernel in Rust.

There are two or three of these, at least at the stage where kmain is Rust code. I'd be really excited to see this develop further.

I just don't have time for ever project I'd like to do :/

Re:Is Ruby Dying? by jerf on Tuesday December 24, 2013 @11:09AM (#6959868)
By that prediction, I did not just mean that someone wrote something in Rust that can boot and do kernel-y things... I mean that there will be a kernel project in progress that is not merely "intended to be serious competition someday", but something that you can seriously use for real, production projects as your computer's (or server's, or cell phone's, or something's) primary kernel/hypervisor/the thing actually running on the hardware. Indeed one of those projects may someday even become the kernel I am predicting, but I'd be very surprised if they are something anybody would seriously make their primary runtime today.

In other words, this is an extreme statement of confidence on my part that Rust is very likely to succeed in their goals of being a true system language replacement. (Contrast this with Go, which initially started out saying it was going to be "system" language, but they've clarified they mean something more like a serious application language rather than something you'd write an OS in. "Nobody" is going to write a kernel in Go.)

Re:Is Ruby Dying? by steveklabnik on Tuesday December 24, 2013 @11:41AM (#6960037)
Absolutely, I agree. I was just trying to say that hopefully, there's some intrepid coder out there trying to do this, and that we have a few people who have started. We'll see where they are in a few years. :)
Re:Is Ruby Dying? by jeffdavis on Tuesday December 24, 2013 @11:17AM (#6959910)
You seem down on both C and C++, but there will always be demand for languages that allow you to control memory.

Rust looks promising, but it's way too early to tell if it can really replace C/C++.

Re:Is Ruby Dying? by pionar on Tuesday December 24, 2013 @09:27AM (#6959440)
I think what jerf means is that, being mostly used as a scripting and web language, it's easy to create legacy code in it. Remember ColdFusion? PHP 3?

However, more to your point, there's legacy C and Java code, but that's because those languages have evolved heavily in their time, so late 90s Java looks little like modern Java, and techniques used in C in the 80s would get you laughed at today.

Hell, even in my main language of work, C#, the difference between most code just 4 or 5 years ago and "modern" C# is vast.

Re:Is Ruby Dying? by danso on Tuesday December 24, 2013 @09:31AM (#6959459)
That's pretty fascinating...I studied C in college and didn't hate it (in fact, I'd like to go back to C some day)...but my perception since has been that not much has changed because not much needs to change. I'd love to see a paper or article looking at innovations or change in practices in these older languages.
Re:Is Ruby Dying? by delluminatus on Tuesday December 24, 2013 @09:31AM (#6959454)
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 -- extremely compact scripting language.

* C - still used in system-level programming

* C# - C# is replacing Java as the OO language of choice for big enterprise systems.

Re:Is Ruby Dying? by eropple on Tuesday December 24, 2013 @10:16AM (#6959647)
C# - C# is replacing Java as the OO language of choice for big enterprise systems.

I'm skeptical of this one. C# requires Windows Server or putting up with Mono's shit. The former sucks; the latter isn't great either. I'd bet that iterations on Java, as well as other JVM languages, will probably retain a significant edge long-term.

Re:Is Ruby Dying? by delluminatus on Tuesday December 24, 2013 @11:07AM (#6959857)
In my experience (admittedly limited to only 3 specific instances), large orgs. have absolutely no problem with using Windows Server (often alongside Linux servers as well). B2B technology is remarkably Windows-centric even now, and I expect it will only become more so as time passes and Microsoft improves its server software and the .NET ecosystem, which is still pretty immature compared to the JVM.
Re:Is Ruby Dying? by pswenson on Tuesday December 24, 2013 @10:22AM (#6959670)
"C# - C# is replacing Java as the OO language of choice for big enterprise systems."

C# is held back by windows. I know there is mono, but enterprises aren't going to bet on mono. So I have to disagree with that.

Re:Is Ruby Dying? by Systemic33 on Tuesday December 24, 2013 @11:01AM (#6959829)
Rumor goes that MS will likely make C# cross platform or open source entire .NET runtime, so that they can run Dynamics on Linux as well. In my opinion, if they did this, I would expect C# to get significant growth, and eclipsing Java.
Re:Is Ruby Dying? by mortyseinfeld on Tuesday December 24, 2013 @11:09AM (#6959869)
C# is held back by windows

"The enterprise" (for the most part) isn't held back by Windows. That's just reality.

Re:Is Ruby Dying? by dragonwriter on Tuesday December 24, 2013 @11:26AM (#6959964)
> "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.

Re:Is Ruby Dying? by mortyseinfeld on Tuesday December 24, 2013 @11:51AM (#6960083)
Except Windows Server works fine.
Re:Is Ruby Dying? by jeffdavis on Tuesday December 24, 2013 @11:22AM (#6959944)
Why group rust and go? Rust allows control over memory and go does not, which seems like a huge difference.
Re:Is Ruby Dying? by actsasbuffoon on Tuesday December 24, 2013 @02:19PM (#6960702)
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? by nemothekid on Tuesday December 24, 2013 @11:28AM (#6959976)
What makes you think Google won't be around. If they weren't, I'd put Mozilla on the chopping block as well.

[1]http://thenextweb.com/insider/2013/11/21/mozillas-reliance-g...

Re:Is Ruby Dying? by rubiquity on Tuesday December 24, 2013 @11:05AM (#6959842)
"* 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."

Unfortunately I imagine that Google has enough money to be around at least 20-30 years.

Re:Is Ruby Dying? by patrickaljord on Thursday December 26, 2013 @05:25AM (#6965853)
Unfortunately? Yeah Google deserves to die, self driving cars, actual robots, Google glass, android, search, map reduce etc. Who needs this useless company that doesn't contribute anything to the world, right?