7 ms·
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
by jerf 13y ago
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!
- polysics 13y agoWhat do you reckon could not be legacy code in 15 years? C family, Java, maybe Erlang?
- pionar 13y agoI 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.
- danso 13y agoThat'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.
- delluminatus 13y agoNot 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.
- eropple 13y agoC# - 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.
- delluminatus 13y agoIn 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.
- pswenson 13y ago"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.
- Systemic33 13y agoRumor 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.
- jerf 13y agoI 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.
- ollysb 13y agoThis 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.
- taude 13y agoWait 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.
- steveklabnik 13y agoThe 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-custom-patches 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.
- ollysb 13y agoI 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.
- makomk 13y agoI think Perl has already reached the state where it's mostly used in legacy code, at least for web development.
- bmj 13y agoWhat 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)?
- sim0n 13y agoI 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).
- hahainternet 13y agoI 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.
- Demiurge 13y agoFollowing 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.
- kamaal 13y ago