When Rails came up, it's "new way" of developing a webapp fast and without much hassle was exciting. In addition, Ruby is a really nice language, and switching to it may give you massive productivity boosts, depending on where you come from. Plus: the amount of high-quality libraries ("gems") is very high. But i forecast a massive decrease of Ruby usage in startups. I'll explain why in the following sentences:<p>Startups are not picking _Ruby_, they are picking _Rails_, which happens to be written in Ruby. Seriously, the language doesn't matter that much nowadays it's all about the ecosystem around it. You need one or more nice frameworks, as light or heavy as you want, and a bunch of libraries for common stuff you have to deal with (never invent the wheel again if not absolutely neccessary!).<p>But time goes on. I was a ruby zealot, but this changed over the last 2 years. Most of the webframeworks of other languages integrated the "rails way" in one way or another. To be clear: Rails hasn't special benefits or is "cool" any longer (i say this as an currently employed rails developer). In addition to this, Ruby itself is showing it's age:<p>- excessive metaprogramming (like eg. in ActiveRecord) makes these things nearly unreadable/un-understandable today.
- parallel processing in MRI is not possible, Rubinius 2 didn't finish/change for the last 2 years (especially unicode support is the showstopper in non-english countries), JRuby brings the disadvantages of the JVM to the table (the startup times in short TDD-cycles are annoying).
- Ruby is still one of the slowest scripting languages in use. In addition, stuff like ActiveRecord kills performance even more, some expressions (no exact number) take hundred times longer than writing the raw sql statement in the rails app. The "convenience" of AR comes with price. (and as i mentioned, the "under the hood" isn't that easy to understand either).<p>To be fair: other languages have their problems, though.<p>- python: the frameworks are similar to the language in their inception: quite good, but not mind-blowing, boundary-pushing or just "hip". I'd say most usage of stuff like Django results from "yeah, i know python, let's use a python web framework" if you know what i mean. Indeed, there's nothing wrong with that. Also: Python3-transition-hassle, GIL like Ruby prevents parallel processing, similar hassle like with the different ruby implementations.<p>- PHP: cheap. hosting is cheap (most customers are happy with near-garbage hosting since they won't get _that_ much traffic). developers are cheap and everywhere available. developing is cheap because of the massive amount of high-quality "frameworks" (not only coding-frameworks, but also stuff like drupal, typo3, wordpress, wiki, ...). But: you get what you pay for. Innovations happens everywhere except in PHP, folks there are just playing catch-up. If you have to develop something new, where you don't have the skeleton in place, PHP isn't the best choice. Like Ruby, performance is not that good, especially when you target modern webapps with thousands of concurrent small requests. PHP isn't made for this.<p>- Perl: slowly fading away. May become "cool" again, similar the way old clothes become "retro" and cool again. No pun intended, i personally like perl. And CPAN is just insane. Everything you'll ever need (and more) is available.<p>- Scala: very interesting (but also complicated and not beginner-friendly) language. Biggest drawback last time I used scala: the "package manager", the single most important thing of every modern language, the thing that defines how the ecosystem will behave, was just garbage. There (as i know) is no place like "rubygems.org" and just "gem install myawesomelib". It _may_ be that SBT has involved into something great over the last year, i don't know. The whole "JVM Ecosystem" has quite a learning curve, too. Not startup-friendly and you'll need _great_ developers (my experience).<p>- ASP.NET MVC/C#: This is my personal opinion: i would never use it again or recommend it to anyone. Not only C#, but the whole .NET stuff or other microsoft-centric technologies. It has fanboys for sure, but not only i hate to work with every single piece of the microsoft "stack", MS is fading away slowly. Even silverlight was abandoned, ehrm i mean, "open sourced". The only way to write C# code in a productive way is in Visual Studio. Oh, you'll need the features of the "ultimate edition"? Have fun shelling out thousands of $$ for your developers. Use MS-SQL Server? Look at the license costs. Whatever, i don't want to start flamewars here. Actually i (european) see C# stuff outsourced to indian offshore businesses more and more (no pun intended). C# Development is just "stuff that needs to be done" in some businesses, there is nothing really innovative or exciting going on and developers are cheap.<p>All this said and done, there is one outstanding "stack", and this is... javascript. We all know the language and the "fame" of javascript and how it evolved over the years. But today, things have changed.<p>- JS is the only player in the browser. "unfair" advantage. Every softwarestack above have to deal with JS today.
- Node.js brings JS to the server. While not suited for anything, it is just _perfect_ for many apps today.
- NPM (the "rubygems" for JS/Node) is quite "better" than rubygems and seems way more active today.
- Kickstart from scratch with express/mongoDB is <i>really</i> fast and perfectly suited for agile development.
- "Big Frameworks" are evolving rapidly the last months.
- Desktop- & Mobile-Apps tend to be written in HTML5/JS more and more.
- Databases like MongoDB use JS as their query language.
- if you don't like JS, there are preprocessing-languages like coffeescript which compile to JS. Write in the style you want, that's it.
- The raw Speed of the V8 VM is amazing.<p>=> if you want, you can have a Stack with JS-pieces only today. From database to the UI, everything can be javascript, which makes development of modern client-heavy apps a breeze.<p>So, to conclude: The future question will not be "why ruby?", but "why not javascript?".