News for hackers. Stuff that matters.
Re:Why Nobody Should Use Rails by mbesto on Tuesday August 06, 2013 @04:57PM (#6169120)
Twitter stopped growing because it chose to use Rails.

Facebook stopped growing because it chose to use PHP.

Pinterest stopped growing because it chose to use Django.

Tumblr stopped growing because it chose to use PHP.

Instagram stopped growing because it chose to use Django.

StackOverflow stopped growing because it chose to use .NET.

37Signals stopped growing because it chose to use Rails.

Groupon stopped growing because it chose to use Rails.

</sarcasm>

Can we end this debate already?

Re:Why Nobody Should Use Rails by el_bhs on Tuesday August 06, 2013 @05:19PM (#6169254)
I don't think anyone is arguing that companies fail to grow because of these languages. It's merely that they would grow more quickly once at scale if they didn't have to spend several years rearchitecting while adding few innovations in the meantime (this is what happened at Twitter, for example).
Re:Why Nobody Should Use Rails by shousper on Tuesday August 06, 2013 @05:37PM (#6169359)
Hmm, I didn't think it took any of them years to rearchitect per se? Regardless, somebody has to do it =) I for one am grateful for these giants pushing our current platforms and languages to their limits. On top of that, they've gone and found solutions, all in their own ways to solve the problem of scaleability. No?
Re:Why Nobody Should Use Rails by el_bhs on Saturday August 10, 2013 @10:38PM (#6193604)
It really did take twitter many years to rearchitect and break their most problematic dependencies on Rails, yes... my understanding is that it was a 4-year process.
Re:Why Nobody Should Use Rails by nivertech on Tuesday August 06, 2013 @05:45PM (#6169405)
From this list only 2 companies aren't VC-funded. StackOverflow raised VC funding later, when it got significant traction.

And I think ASP.NET has a good performance comparing to rails (not sure if they used C# or VB, C# obviously not a dynamic language).

The other one - 37Signals obviously experts in Rails - so they knew how to scale it. And even they took external funding later.

I think that dynamic languages like Erlang/Elixir, Clojure (and maybe Go) offer a good performance/productivity ratio.

Anyway, I think that Rails is OK for paid B2B web applications, not so much for free consumer stuff.

Re:Why Nobody Should Use Rails by renownedmedia on Tuesday August 06, 2013 @05:14PM (#6169218)
I don't see Node.js in that list.

</troll>

Re:Why Nobody Should Use Rails by vbsteven on Tuesday August 06, 2013 @06:00PM (#6169504)
Are there any companies of that size out there actually using Node in production?
Re:Why Nobody Should Use Rails by aaronbrethorst on Tuesday August 06, 2013 @08:12PM (#6170063)
Re:Why Nobody Should Use Rails by Oculus on Tuesday August 06, 2013 @07:08PM (#6169807)
Google, I remember reading they use it internally like crazy.
Re:Why Nobody Should Use Rails by edwinnathaniel on Wednesday August 07, 2013 @01:20PM (#6174147)
aaron's link seemed to disprove this.
Re:Why Nobody Should Use Rails by bpicolo on Tuesday August 06, 2013 @07:13PM (#6169835)
I believe eBay said they used it for some things?
Re:Why Nobody Should Use Rails by AdrianRossouw on Tuesday August 06, 2013 @06:44PM (#6169701)
linkedin ?