改變 BURG 主題的圖示
外遊二週
Realistic blog usability
Many moons ago, Jacob Nielsen wrote an entry about 'blog usability',which I reacted to at the time . But as Inoted back then, Nielsen's advice seemed aimed mostly at what I called'commercial' blogging, and ever since then I have had simmering in mymind the idea that it misses the true usability issues for typical blogs(then and now). Today I feel like letting things bubble over and finallywriting down my thoughts.
To start, let's ask two important questions
戀愛經驗
我的戀愛經驗極其貧乏，因為我老婆是我第一個女朋友（老婆看了必會說：「第一個？」是，第一個正式的女朋友，之前只和另一個出了兩次街，不算），識於十七、八歲時，不敢
Bio Hazard Outbreak / Resident Evil Outbreak 破壞 (Destruction)
| 武器 | 固定傷害值 (狙擊無效) |
|---|---|
| 殺蟲水、自製火炎放射器 | 無效 |
| 肢體攻擊、三種刀 | 40 |
| 各種9mm手槍、Daylight發射器 掃把、鐵棒、彎曲鐵棒、松葉杖、長棒、木棒、矛、電擊棒 扳手、嚴重彎曲鐵棒、 |
我說，因為我認真
從亞當和夏娃的肚臍說起
Why I'm Switching Back from Chrome to Safari 5.0
Chrome was great. It was Safari , with a little more speed, better tabs, and a cool status bar that would only show when it needed to.
But I'm switching back, for the following reasons:
- Safari 5.0 is just as fast as Chrome.
- Safari's tab system is nicer looking than Chrome. Not a biggie.
- Safari can read PDFs without opening up an external application, and without downloading it to your Downloads folder. I hate having to clear out my Downloads folder every day
Making the Linux kernel shut up about segfaulting user programs
Relatively modern versions of the Linux kernel on some architecturesdefault to logging a kernel message about any process that receivesvarious unhandled signals. The exact details depend on the architecture,but I think it is common for the architectures to log messages aboutunhandled SIGSEGV s, ie segmentation faults.
(Most architectures are capable of logging these messages if the featureis turned on, but not all architectures turn it on by default. Itappears that x86 (both 32-bit and 64-bit) and SPARC