Introducing Rubinius X

Re:Introducing Rubinius X by Argorak on Tuesday October 15, 2013 @12:35PM (#6554342)

Twitter is a one-in-a-thousand company with traffic amounts that most of us here will dream of ever achieving. Even the more people that don't take specific interest in running large scale deployments.

Even writing you frontend in Java first would (most likely) not have helped you coping with the new-found challenges in that heights.

[ Parent | on HN ]

Re:Introducing Rubinius X by spullara on Tuesday October 15, 2013 @01:13PM (#6554665)

Perhaps on the efficiency side. On the performance side it would be true even on a small site (unless it was all static, cached content).

http://www.techempower.com/benchmarks/

[ Parent | on HN ]

Re:Introducing Rubinius X by danieldk on Tuesday October 15, 2013 @04:19PM (#6556038)

Twitter is a one-in-a-thousand company with traffic amounts that most of us here will dream of ever achieving.

And not every low-traffic site is simple CRUD. If you do image processing, applying machine learning, natural language processing (or a thousand other things that are CPU intensive), it's nice that you can directly use one of the many high-performance libraries available in the Central Repository in your webservice.

[ Parent | on HN ]

Re:Introducing Rubinius X by Argorak on Tuesday October 15, 2013 @04:28PM (#6556080)

You probably won't reasonably run most of these applications in your frontend framework either.

Also, the example was the Twitter frontend. So I respond to Twitter frontend. Don't derail.

[ Parent | on HN ]