glebd

Another sad example of how Microsoft manages to overcomplicate things. This is DLL hell, reloaded.

While this is in itself very good news, there is a worrying phrase in the announcement. IE8 passes Acid2 test *in IE8 Standards mode*. This _may_ mean there is another mode that doesn't render Acid2 correctly and must be some sort of compatibility mode. I appreciate the need for such mode in MSIE, but only as long as it is not set as the default upon release of MSIE8.

androidi wrote:

gvs wrote: I would like some more attention to mono-spaced fonts.

Second that!

I read that the new set of fonts for Longhorn will contain a fixed font called Consolas. I don't know if it will be a full family (Regular, Bold, Italic, Bold Italic) or a single font as Lucida Console is now. The problem is that with a single font you cannot really use it with Visual Studio's syntax highlighting when bold face is used for keywords. A lack of proper Bold variation of the font you use breaks source code column alignment. To see what I mean, try using VS with Courier New (nice columns) and Lucida Console (ugly, columns broken).

So where does this leave the Windows search feature available from the Start menu? Would it be better to update that one instead of fragmenting the search feature by introducing another tool?