6 ms·

For what it's worth, I contributed to the article and I call myself a programmer.

• henning 18y ago
  Do you and Arrington have some kind of confidential knowledge about Twitter's implementation that allows you to conclude that its problems are directly attributable to Rails itself and not how it was implemented, or something that has nothing to do with the programming language at all (the hosting facility they use, their operating system, ...)? Or are you just trolling?
  • hwork 18y ago
    Yeah I think your question is a fair one. But I don't think it's ridiculous to assume that the stability and operational functionality of a website is primarily dependent on the web framework the website uses. The data center is probably the second to blame, but I don't think that Twitter's problems are related to continual issues with their hosting (though i'm sure some are). I doubt the blame lies on Debian, or whatever their using.
    • ericb 18y ago
      Actually, that is ridiculous to assume.
    • henning 18y ago
      It is possible to write buggy, unstable, unreliable, unscalable applications in any framework or language and just because you use a certain technology doesn't mean anything about whether you'll create an app with a good experience. Handing a sniper rifle to someone does not make them a sniper. Snipers have personal qualities and training that make them what they are; their weapons are just tools that help them realize their inherent abilities as well as possible. Why are you and other TechCrunch people so eager to assign blame when you don't actually know anything about what you're assigning blame for?
      • hwork 18y ago
        Just to keep the conversation going: what do you think Twitter's main issues are ? (Or do you think their downtime is not worth mentioning?)
        • ashu 18y ago
          What the parent says is that a proper assessment will require an in-depth knowledge of how it is actually implemented. Taking random shots like this article does is like a blind man trying to grope an elephant.
          • jamesbritt 18y ago
            " Taking random shots like this article does is like a blind man trying to grope an elephant." Groping an elephant seems like a bad idea even for the sighted.
            • DanielBMarkham 18y ago
              I would like to second the call for an immediate stop to elephant groping. Elephants are a dear and treasured species. This continual assault by blind people and various other gropers have too often left our Loxodonta Africanan friends cowering in terror. As for RoR, I'll simply quote a good friend of mine. "RoR rocks! Scaling isn't that big a deal. Took us over six months to get the stack just right for a recent customer." Ugh.
        • ericb 18y ago
          Scalability problems are usually endemic to a particular setup. There is always another bottleneck. The way you're viewing scalability is different than the reality of it. My previous company (a web testing company) did a load test for a large tax return company. When testing started, their app could support 3 simultaneous users. When the bottlenecks were removed, one by one, the same app (framework, codebase, language and all) supported north of 10,000 users. As you test, there is usually something like a database lock problem, high cpu from a loop that needs to be optimized, bad query/data layout, memory usage maxing out, or something you are running out of, one way or the other. The people who point out that twitter is not a standard web app and might be better served by messaging have a point also.
    • deleted 18y ago
      [deleted]