Fool's Garden

前几天，Google管Search的老大Matts Cutts接受ReadWrite Web的访问，在谈到语义识别在下一代互联网中的应用是，他是这么说的：

Richard: What do you think about semantic technologies (like for example Hakia)? How important is natural language understanding for search and is Google doing anything in this direction?

Matt: We do pay a lot of attention to a lot of different technologies, so I would define Google's approach as very pragmatic. And we keep an eye on the entire space and we try to say, ‘ok what are the areas that are most promising for users?’ Historically it's always interesting to view the progress of semantic technologies. For example if you do a search like: 'how many states are in America?'. Some search engines that claim to be semantic won't do a good job in delivering the right results, whereas Google can do a very good job - even if you think, ‘ok how can they handle natural language, or how can they handle the semantics of that search.’ And I think what Google benefits from is the sheer size of the Web and the sheer amount of data, and it really does help us understand the meanings of words and synonyms. So we do have a pragmatic approach and we don't necessarily place all our bets on one particular way of doing things. We are exploring a lot of different things all at once.

红字那部分，大概是这么说的，“举例来讲，如果你搜索‘美国有多少个州’，有些号称可以处理语义的搜索引擎返回的结果并不好，然而Google却可以做得很棒，即便你会想，‘他们是如何处理自然语言的，或者他们是如果处理搜索语义的呢？’

结果，有人真的做了这个实验，把"how many states are in Aemerica"作为搜索关键字，下面是Google和Windows Live Search得到的结果：

这样鲜明的对比，让我不禁想起，当年百度的那个广告，“我知道你不知道我知道你不知道我知道你不知道”。

In general, PocketPC supports high-DPI and Low-DPI (192 and 96 respectively) display modes. As you know, image with fixed resolution will be displayed in a smaller size on Higher DPI screen. For example, images on 192 DPI screen will have as 1/2 size as on 96 DPI's. To maintain a consistent image size in both High and Low DPI mode, PocketIE introduces Pixel Doubling, which simply doubles the pixels used in High-DPI display. Just like an auto zoom out on every image pIE is browsing.

Pixel Doubling also affects address bar and status bar. The heights are doubled accordingly in the High-DPI display.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mobilesdk5/html/wce51conpixeldoubling.asp

We know that WinCE 5.0 supports 32 processes running simultaneously at most. Each process resides in a continuous 32M virtual memory space, namely Slot. The 32 processes slots range from Slot 2 - 33, plus a specific one: Slot 97 for NK.exe. And we also know that Slot zero is special enough to be occupied by the process context that current thread is executing. But why? Why this design choice was made?

The answer is quite simple. We use the same PE format for both desktop and device applications. But because every desktop process gets a 4GB memory space which always counts from 0. So any process running in WinCE is designedly mapped to Slot 0 and then they can share the same memory architecture with desktop couterparts and achieve the compatibility in PE.

星期六的晚上，我捧着一盒爆米花，坐在电影院里面，看着金刚为了爱咆哮，追逐，死亡。在回来的路上，我问同行的朋友，金刚对Ann究竟是什么样的爱？像慈父？像挚友？像情人？

在现实世界里面，知道自己爱上一个人并不困难，难的是区分出自己的爱，哪一样更多一些。这也就是为什么那么多人在爱面前犹豫、徘徊、退缩。就像电影里面那位话剧女演员说的那样，"他总是不肯说出那三个字，他认为一切尽在不言中。男人们自认为足够强大，可以征服世界，但却任凭真爱从指尖溜过..."

反过来，Ann对金刚的爱再一次说明了，样貌不是问题，身高不是障碍，女人要的可能也就是安全感这么简单。

In Win32, every single thread has a priority ranging from 0 (lowest priority) to 31 (highest priority). The priority value is determined by both thread priority level and process priority class. GetThreadPriority returns priority level only, you still need to call GetPriorityClass before figuring out the thread priority.

But things are quite different on device side. WinCE 5.0 is designed to support 256 thread priorities but no priority class any more. Both CeGetThreadPriority and GetThreadPriority can be called directly to retrieve a thread priority. Depending on which thread that being queried, the return value of CeGetThreadPriority could range from 0 to 255. Nevertheless, GetThreadPriority only supports application thread with priorities from 248 to 255.

GetThreadPriority is preserved for backward (before WinCE 3.0) compatibility reason. You can safely forget the legacy function and use CeGetThreadPriority instead unless you are porting the applications to desktop, or vice versa.