I feel like I'm drowning in ignorance and the only lifeguard around won't even throw me a damn life preserver.
<<
Please, talk some more. You're hilarious. >>
Ahh, how sweet
<<
Man, you're rich. >>
Am I? I was being facetious. Perhaps my humor becomes less evident later in the day. Hard to convey the appropriate level of facetiousness over these forums.
<<
Core OS functionality, bawhahaha. How is Win2k anything more than a 1.0 revision to NT 4? The kernel is pretty much the same, the interface is pretty much the same. All they did was enough tweaking to bring it from NT 4.0 to 5.0. You read too many MSDN articles my friend, you are brainwashed. >>
I'll answer you, dwell, as I actually respect your opinion, and you've always been well informed (even if we are sometimes on the opposite side of the fence). To answer your questions:
We can't argue that even a "pretty much the same" change denotes a great deal of work for the transition. I'm not saying this warrants an entire rerelease of the product, but a "minor change" to a project as large as Win2k is a gross oversimplification.
It's a little more than "tweaking." True, they've basically directed their regurgitation into a new area and slapped a new label on it, but it benefits us as developers. There are many reasons why my target platform is Win2k (especially since my last target was NT4

), but since COM+ essentially integrates MTS into the core services, I'm happy. There are MANY benefits, development wise, that COM+ brought on the table. True, a lot of them were available in RM's, service packs, technology previews, etc., but Win2k brings a lot to the board as well. I'm not a MS marketing rep (although I may at times sound like it), so I'm not going to repeat the list of reasons I choose Win2k as my target platform.
Yes, I do read too many MSDN articles, but not out of arbitration.
[edit]Note about the MSDN articles. These aren't articles on how MS is the panacea of all developer woes, these are (usually) articles that give insight as to how things are implemented, design patterns, etc.. I find these resources to be incredibly advantageous. This isn't a religious argument, but an argument of opinion. My work is brought to fruition, thus my comments are based off the empirical, not theoretical.[/edit]