It has been asserted that a reason for Friendster's demise was in part internal technical problems that manifested themselves in high page response times, often to the point of being unusable.
Though, much of this was exacerbated my management's insistence on implementing a myriad of side jobs to bring revenue while deliberately ignoring the main part of the website being unresponsive.
"technical difficulties proved too pedestrian for a board of this pedigree. The performance problems would come up, but the board devoted most of its time to talking about potential competitors and new features, such as the possibility of adding Internet phone services, or so-called voice over Internet protocol, or VoIP, to the site."
Comments
It has been asserted that a reason for Friendster's demise was in part internal technical problems that manifested themselves in high page response times, often to the point of being unusable.
Though, much of this was exacerbated my management's insistence on implementing a myriad of side jobs to bring revenue while deliberately ignoring the main part of the website being unresponsive.
That's interesting. Thanks for pointing it out, after you mentioned that, I had to look it up:
http://highscalability.com/friendster-lost-lead-because-fail...