剛從TEDxKL回來, 現場看的氣氛真的完全不一樣! 這是我第一次出席TEDxKL,、第一次去到Publika - Solaris Dutamas. 雖然不完全認同有些演說但那些畢竟是他們人生最精彩的縮影,的確是『聽君一席話勝讀十年書』。而且,一次過觀賞了12席話,吸收了12位成功人士的精華。開闊了思想,也增長了見聞。這類型的演說太有營養價值了,錯過的人明年一定要出席啊!
可怜的Linux普通用户
L: Linux很好但不够人性化也是它不争的事实...
L: Linux出现太多variations了..
W: 不像Windows...学一次终身受用.
W: 我在98SE年代买了一本《白痴学Windows 95》.
L: 我在2002年买了Red Hat 7的使用手册...
W:虽然人人大骂Windows Vista/7对UI做了很大的改动但到现在我还能顺畅的对Windows进行基本操作无需重新学习...反正在Windows不是yes就是no...就是那么简单.
L: 2004年Ubuntu开始盛行...短短两年我又要重新学会怎样用Linux, 又需要买另一本使用手册. 什么KDE, GNOME的...麻烦死了...那是普通用户需要去烦的吗?过后Ubuntu 每年推一个新版...每个新版都说比旧版好...我这个可怜的普通用户每年都得花上不少时间重新适应.... 囧
L: Linux出现太多variations了..
W: 不像Windows...学一次终身受用.
W: 我在98SE年代买了一本《白痴学Windows 95》.
L: 我在2002年买了Red Hat 7的使用手册...
W:虽然人人大骂Windows Vista/7对UI做了很大的改动但到现在我还能顺畅的对Windows进行基本操作无需重新学习...反正在Windows不是yes就是no...就是那么简单.
L: 2004年Ubuntu开始盛行...短短两年我又要重新学会怎样用Linux, 又需要买另一本使用手册. 什么KDE, GNOME的...麻烦死了...那是普通用户需要去烦的吗?过后Ubuntu 每年推一个新版...每个新版都说比旧版好...我这个可怜的普通用户每年都得花上不少时间重新适应.... 囧
Firefox setInterval passes Random number as parameter bug
I was working on a web development project. Until 30 minutes ago, I had discovered something strange with my code. It worked well on IE and Chrome but it created random results on Mozilla Firefox version 3.6.12. So i did some quick alert()s to find out whats went wrong. Surprisingly, I found out that if you pass a callback function that can accept parameter into setInterval. It will pass random numbers into the callback function when it wasn't suppose to. I tried to start Firefox in safe mode and run the test again. Unfortunately, the bug still exists.
If you're geeky enough to watch the bug live in action just head over the demo page to reproduce the bug.
Update #1: I just tested the code with setTimeout() it seems like setTimeout() is affected as well.
Update #2: I just filed a report at Bugzilla@Mozilla.
Update #3: It was my mistake. :P It isn't a bug but an inconsistency between browsers.
If you're geeky enough to watch the bug live in action just head over the demo page to reproduce the bug.
Update #1: I just tested the code with setTimeout() it seems like setTimeout() is affected as well.
Update #2: I just filed a report at Bugzilla@Mozilla.
Update #3: It was my mistake. :P It isn't a bug but an inconsistency between browsers.
订阅:
博文 (Atom)