>>You are advocating the "fools rush in" approach, but to high tech "he who
hesitates is lost" is often more appropriate. Some examples:

This is really what the problem is at this point. THere's nothing to rush to. I've been playing with the CLR stuff for the last few weeks and it's been a drag because the docs are inadequate, things don't work the way they're supposed to and things are unstable right now. And from what I've heard a lot of things are not nailed down yet, so that anything you build right now may no longer work when a beta rolls around.

I think the problem with all of this is only that MS should have waited to do this 'promo' blitz when there was something more to show. Like something that would be actually usable...

If you talked to the people who did the .Net presentations you know how hard they had to work to make those demos work with multiple versions of the stuff running on different machines just to find one that works...

For a typical developer I think it would be a waste of time to play with this stuff in its current state...