I agree, which is strange because I am the kind of guy who spends a lot of time with the new stuff. I've been spending most of my free time playing with Longhorn and Developing Whidbey stuff. However, I still get bugged when MSDN Mag arrives and it is nothing but Longhorn/Whidbey stuff. IMO, there are plenty of other places where you can find that stuff if you want it. But MSDN Mag is my "right now" content. Early Adopter's post/comment on what you said is also true. We *should not* ignore what is coming and it *should* have an impact on how we are designing today. However, I think that there are enough other places where you can find the future stuff out. I don't really care to have issue after issue of stuff I can't use right now. Perhaps a section of the mag devoted to future techologies, but not the entire issue.
That said, articles that are about future technologies - but show *how* to leverage that particular technology *now* or how to design your code so the transition/migration to that technology is easier when the time comes is pretty cool. I don't mind those as much.
Ryan: Then we are on the same wavelength :)
The thing that gets me is that a lot of the "experts" are actually clueless about other things going on in the larger community. For instance, there's no mention of MasterPages working for ASP.NET v1.*, and the same can be said about some of the other v2.0 things that have already been implemented now for v1.*.