Hacker News new | past | comments | ask | show | jobs | submit login
So, Why is Twitter Really Not Using Cassandra to Store Tweets? (highscalability.com)
56 points by helwr on July 11, 2010 | hide | past | favorite | 18 comments



Answer: this person doesn't know.


You spoiled it


Kinda funny that people are still admiringly quoting Joel's criticism of Netscape for going with the big rewrite, now that that rewrite has turned into Firefox.


Technically, I think Firefox is the rewrite of the rewrite.


So it's doubly wrong?


i think spolsky was saying in the context of a company. firefox started as an open source initiative, it's a different construct.


It's been a while, but iirc the rewrite of Netscape's browser started soon after they opensourced it, when they were still a going concern. Later Firefox came along and repackaged the core code.


Why? He was still right. Netscape is dead. The company didn't survive the rewrite even if some of the software eventually did.


Netscape probably would have been dead anyway, rewrite or not.


The "rewrite" didn't help them, though. If you think people complain about IE6, it's got nothing on Netscape Communicator 4.


How long did it take to get to the halfway decent (and I do mean halfway) browser that it is from the rewrite? How long would it have taken to get there /without/ the rewrite?

EDIT: If you're going to downvote at least explain why...


Not really - Netscape still had more marketshare (as a percentage of people who use the internet) than Firefox has today.


You know how you think you're 90% done with a project, and there's a ton of little details, so that in reality, you're actually a long way out? That's where Cassandra is at.


I think the author was just looking for an excuse to post that flowchart.


I think there problem is that they are already riding on the edge in terms of service stability and availability, trying to conduct a large scale migration now would probably just add to this. I don't think they can really afford extended downtime now just when they're beginning to implement their monetisation strategy.


summary: if it works, don't fix it.


Unless if you have to go back and keep on fixing it again and again and again and again... until one day, the cost of fixing (please also include the cost of re-testing) can't be justified any longer.

Anyhow, that's why software should be developed in modules/components.


Or more accurately: if it works, don't fuck with it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: