Wikipedia 裡,有這樣一段:

According to the Hitchhiker’s Guide, researchers from a pan-dimensional, hyper-intelligent race of beings, construct Deep Thought, the second greatest computer of all time and space, to calculate the Ultimate Answer to Life, the Universe, and Everything. After seven and a half million years of pondering the question, Deep Thought provides the answer: "forty-two."

"Forty-two!" yelled Loonquawl. "Is that all you’ve got to show for seven and a half million years’ work?""I checked it very thoroughly," said the computer, "and that quite definitely is the answer. I think the problem, to be quite honest with you, is that you’ve never actually known what the question is."

當別人答不到你的問題時,可能是因為自己根本不清楚問題是什麼。

這是我近來看、不認識的人的Blog(和其中一些特別的文章):

  • Sorting It All Out [經常有關於Unicode的文章]
  • 關於 Sorting
  • 關於 ¥ 和 ₩
  • The Old New Thing [經常有關於MS Windows歷史和Programmer常犯錯誤的文章]
    • 關於命名
  • 關於 Samba
  • 關於 Performance
  • 關於 Programmers 的(非)專業性
  • Neil’s World [一個平凡人?]
    • Random Queries [就是很 Random 的東東吧?]
    • MovableType [就是這個網用的軟件]

    跟據 IEBlog , Microsoft今天推出了 IE7 Beta 2 版。

    真奇怪……我一直以為之前的Preview就是Beta 2……

    在 Tom Kyte 的網站上,不止一次提到 Oracle Index 不應被 Schedule Rebuild。但認真地想時,發覺這問題實在是太複雜。實抵上是不能被明白的。Tom所持的意見似乎是Data Access Pattern裡頭有一種Hidden Structure,即使Rebuild了,最終也會回到本來的狀態。這個我也不反對。

    但,Rebuild Index的Cost是否真的太大?不Rebuild又有什麼解決辦法?這兩個似乎是不能問的問題。 

    學期尾……很多事發生。自己的功課、小組的Project……誰也不想得失。自己,應該如何?

    在 JeremyK 的 Blog 看到這個…… Don’t believe everything the debugger is telling you!!! (aka Rootkit)

    這樣的東西……即使有能力去看得懂,也不會有心力去跟踪……

    上星期收到一封Email, 是關於舊網頁的日記。
    覆了後卻沒有回音,到底……

    已經有一段時間沒有記起這sdiz.net 網管何時到期。一直都以為到期時會收到一張renewal的帳單,誰知道……

    原來在3月頭已經夠期。這家網管不單沒有給我帳單,也沒有停我的帳號。直到我提出這個問題,他們才趕忙給我帳單。這種公司,我想早晚要轉。
     

    已經有一些日子是這樣:沒有什麼動力;時間好像不由得自己去管理;早上總沒有辦法起床。

    自己想去做該做的事。好像好久沒有看過一本好書了,因為電腦太方便?因為電腦太霸道?

    Bruce Wallace in OnJava.com demostrate how to solve a non-exist problem:

    Implementing Mutual Exclusion for AJAX

    With the increasingly popular AJAX paradigm, a browser page can make requests for server data in the background while the user interface continues to be active in the foreground (hence the "asynchronous" in AJAX). However, the problem exists that these two activities are typically accessing common JavaScript and DOM data structures simultaneously. The classic solutions to this concurrent programming problem are not supplied by JavaScript. This article describes the author’s new adaptation of a proven mutual exclusion mechanism that works around the limitations of JavaScript.

    Let’s list out some facts: 

    1. All DOM-related operations are done in the UI-thread.
    2. JavaScript is essentially single-threaded. It’s event-pooling.
    3. Someone say ActiveX in IE may preempt. If this is true, busy-waiting would just deadlock.
    4. If JavaScript is multi-threaded, his Map() would just break because accessing complex object can’t be atomic.