dbanotes posted a photo:
就是这个吃着快餐的家伙在华尔街工作之余弄出来了 del.icio.us .
图片上传递出来的信息: Yahoo! 收购 del.icio.us 的价格是 3100 美金。最初 del.icio.us 运行在马克.安德森送给他的一台服务器上.
www.businessweek.com/magazine/content/06_33/b3997010.htm
Lao Hua has an interesting blog about a game he facilitates. The game is like this:
My Guess
I played the game for the first time yesterday. My guess was 8.2
I thought if everyone randomly chooses a number, the average should be 50, and 2/3 of it is 33.3.
I assume everyone should know this. If everyone knows it, people will try 33.3333, and the average is 33.33. 2/3 of it is 22.22
If everyone is as smart and think of this, people will irratate, and the number is becoming smaller and smaller, like this.
50
33.33333333
22.22222222
14.81481481
9.87654321
6.58436214
4.38957476
2.926383173
1.950922116
My brain started to hurt, and finally, I thought, at least it should be within 1-10, so I randomly chose 8.2
The Final Result
This is the guess from 12 people:
30
98.16
32
50
12
33.3
22
8
8.2
18
28.68
37
The average is 31.445, and 2/3 of it is 20.96333333. Finally, the person who guessed 22 won the game. I lose miserably.
I agree that world is not created by genius now.
在国内的 BSP 中, BlogBus 给我的印象是挺注重技术一家站点(比如搞一些搬家活动,虽然...但是还是会方便用户的)。不过从最近的数据恢复事故能看出来还是网站维护质量存在挺大的问题。
BlogBus 的公告板上写到:
事故原因:BlogBus于7月1日增加了两台新服务器用以解决网站负载问题,7月20日发现一台服务器可能由于Raid卡或硬盘出现故障,导致一个3G多的数据库文件损坏,致使7月1日至7月19日用户日志数据丢失。解决办法:由于BlogBus采用静态页面发布,所有已发布日志均生成静态页面保存,所以丢失数据可以由静态页面导回数据库——就是说丢失的数据可以反向导回恢复。
让我不敢相信, 将近 20 天的时间内,数据库没有备份?! 难道他们的数据库是不做备份? 解决办法是静态页面导回数据库,不知道要耗费多少人力劳动。就算是技术人员写脚本,恐怕也不是那么省时的事情。估计最后可能仍然不可避免的会丢掉少量用户的元数据。
我曾经感慨过 Web 2.0 应用服务稳定性仍然任重道远,现在看起来,Web 2.0 应用服务的可靠性也会逐渐成为用户担心的问题。
备份! 备份!
-EOF-