Twitter Shifting More Code to JVM, Citing Performance and Encapsulation

Re:Twitter Shifting More Code to JVM, Citing Performance and... by petenixey on Monday July 04, 2011 @03:52PM (#2727646)

I wonder if the reason Twitter never sees any significant evolution in product is because they've weighed themselves down with too much iron cladding on their services or if they've had more time to iron clad their services because they never evolve the product.

Neither may be related but for a large company with very little product they seem to produce astoundingly little.

[ Parent | on HN ]

Re:Twitter Shifting More Code to JVM, Citing Performance and... by akronim on Monday July 04, 2011 @06:38PM (#2728090)

They may have very little functionality, but do it at scale. e.g. even searching tweets (which doesn't seem to work that great...) is a massive undertaking (not astoundingly little) that they're obviously still working at.

[ Parent | on HN ]

Re:Twitter Shifting More Code to JVM, Citing Performance and... by petenixey on Tuesday July 05, 2011 @07:51AM (#2729473)

That's a fair point and I don't trivialise the engineering however I am taken aback by the just how little product they produce. In a similar timeframe Facebook had created vast swathes of product and dealt with far greater user numbers than Twitter.

[ Parent | on HN ]