Hacker News new | ask | show | jobs
by dragonwriter 4643 days ago
> If I recall, Rails got the bad rap early on because Twitter thought it was the cause.

IIRC, it got a bad rap because of one blog post by a Twitter dev that seemed to suggest that Ruby and/or Rails was the cause, which was later followed by a more in depth explanation from Twitter of their reasoning, which didn't place the blame there, but by that time Ruby/Rails haters had permanently latched on to the "Rails was killing Twitter and that had to leave to survive" meme and facts were no longer relevant.
1 comments
randomdata 4643 days ago
They also had that big huff about ActiveRecord not supporting more than one database system in a replicated environment. Humorously, someone from outside of the organization supplied a patch a few minutes later.

To make matters more complicated, Twitter publicly abandoned Starling, their Ruby-based message queue, for something written in Scala. People took that to mean they abandoned Ruby and Rails completely.

As far as I know they are still using Rails to generate the HTML pages. If not, it is a recent change.

link
dragonwriter 4643 days ago
> As far as I know they are still using Rails to generate the HTML pages. If not, it is a recent change.

I think they recently moved that part to the Scala, but it was much later than the other thing.

link