In this post, Stan Lippman writes about the syntax for Param Arrays in VC++ Whidbey. And while I don’t do much C++ anymore, I’m reading his piece with rapt attention, just like I read all of his writing. However, one throw-away statement in this blog entry spoke to me particularly:
“If I had felt a larger space of available time, I would have motivated the presentation, pointing out the analogy with the existing uses of ellipsis, pointing out alternative designs and the associated problems, and in general leading the reader to an appreciation of what was chosen.”
When I write, I’m always striving to motivate, point out analogies, point out the alternatives and the associated problems and lead the reader to an appreciation of what was chosen (although I never could have stated it as clearly as Stan did w/o even trying). Apparently, I’ve been a Stan Lippman wannabe for years. Who knew? : )
Intel decides to follow along after AMD's success in adding 64-bit support to the x86 instruction set that Intel invented. Without AMD, we'd all be paying way more for chips, plus we'd all be buying Itaniums whether we wanted them or not. Thanks AMD. Thanks capitalism.
In general, I love Eric Sink, so it’s a surprise when there’s something he’s written that I haven’t seen. In particular, at the bottom of his Geek Guantlet (which is nice all by itself), there’s an addendum called Top Eight List: Clues that You Might be a Geek. My favorite:
“You know at least one person whose computer has less RAM than your video card.”
If you don't already know the basics of .NET's Code Access Security model, you shouldn’t wait any longer. Not only is CAS key to No-Touch Deployment today, but it's key to ClickOnce deployment in Whidbey, which will also be a huge part of the Longhorn deployment story tomorrow (or maybe the day after tomorrow : ).