How We Went from 30 Servers to 2: Go

Re:How We Went from 30 Servers to 2: Go by sabat on Tuesday March 12, 2013 @09:09PM (#5366147)

Not quite. He's saying that people who think Ruby is slow are often people who have no idea how to performance-tune it.

[ Parent | on HN ]

Re:How We Went from 30 Servers to 2: Go by bpicolo on Tuesday March 12, 2013 @10:38PM (#5366458)

Well, more of the time it's because Ruby actually is, in fact, slow.

[ Parent | on HN ]

Re:How We Went from 30 Servers to 2: Go by pjmlp on Wednesday March 13, 2013 @03:43AM (#5367324)

I though the implementations were slow or fast, not the languages.

[ Parent | on HN ]

Re:How We Went from 30 Servers to 2: Go by codygman on Wednesday March 13, 2013 @04:54AM (#5367477)

Typically a language is considered slow or fast based on it's most popular implementation, sadly.

[ Parent | on HN ]

Re:How We Went from 30 Servers to 2: Go by ajanuary on Wednesday March 13, 2013 @06:45AM (#5367722)

True, though language design can have implications on how fast things can be implemented.

[ Parent | on HN ]

Re:How We Went from 30 Servers to 2: Go by pjmlp on Wednesday March 13, 2013 @08:20AM (#5367939)

Agreed, but it is still an implementation issue, because one can eventually discover ways to optimize such cases without changing the language.

[ Parent | on HN ]

Re:How We Went from 30 Servers to 2: Go by sabat on Saturday March 16, 2013 @05:03PM (#5386796)

Ruby is not, in fact, slow. This myth has been debunked so many times that I'll just leave the googling to you as an exercise.

[ Parent | on HN ]