YAG;

Gee – I had this image of you guys in cubicles throwing cream pies at each other! You broke the illusion! :)

Tom



>LOL - this isn't a turf war thing - it's a customer base thing. FWIW, I spend a good portion of my week with Eric Gunnerson from the C# team. And Herb Sutter from the C++ team. It's not like we're firing bullets at each other, or even don't spend time together - heck we're all in the same building.
>
>The way it works is simple - every group comes up with ideas based on internal and external feedback. Each team ranks their ideas. The ideas are shared across every team. Each team then takes ideas from others and re-ranks them. Some teams rank differently than others. Doesn't mean we dislike the ideas - just that they may not make sense.
>
>Here's an example. VB6 developers want Edit and Continue. That's gonna be our #1 priority for the next major version of the product. C# gets to decide where that stands on their list. So does C++. Why can't a central team enable it for all of us? Because even though a core team does the basic underlying work, there's a lot that has to go into the compiler for each language that implements it as well. Think of it as a C-layer and an I-layer from a Codebook perspective. We're committing to that work. Other teams have to as well. Because we commit to that work, we may not be able to commit to something else for that release. That's just the way things work with finite resources. FWIW, that's why VB provides better editor intellisense and bug catching - we spent time doing the work to make our compiler work fully in the background. C# elected not to.
>
>So, while we are "singing off the same sheet", we want to sing in harmony - not the exact same note. <g>
>
>yag
>
>
>>>>> Everything in the framework should be accessible to all languages - however, another truth is that each product team has a finite set of resources, and each has their own community that prioritize feature sets differently. So, each team has to prioritize their work accordingly. Therefore, you may find one team doing something before another, or them doing the same thing together. <<
>>>
>>>Understood, but shouldn't the overall Visual Studio management group insure the teams working on VB.NET, C#.NET, et al are singing off the same sheet of music? I am thinking of the people who are identified as part of the VS team rather than the VB.NET team and the other teams which fall under the VS umbrella -- Robert Green, David Lazar, people like that. I may not be up to date on the specific individuals (Robert and David may be more involved with marketing than product development) but you get the idea -- VS management. Letting .NET language teams fight turf wars and proceed on their own agendas would seem to sabotage the promise that the .NET language we use is just a "lifestyle choice."
>>>
>>>Mike
>>
>>Mike;
>>
>>Good point and that is how I see it. It is as if it is Access vs. VB vs. VC++ vs. VFP all over again. If Mozart were the composer of this "piece of music", all the voices would be in unison and not screaming for "self dominance". My team is better than your team or whatever.
>>
>>Could this be Microsoft’s answer to Japanese Marketing? A marketing strategy used by the Japanese for VCR’s as an example was very interesting. There were four VCR manufacturers in Japan. Each one made ten different models and completed units were stock piled in a warehouse. The top four sellers from each manufacturer were manufactured in quantity and the remaining units were disposed of. The market was established based upon sales and not predetermined requirements from users.
>>
>>Marketing in the United States traditionally used “Market Research” to determine what customers want before anything was built. So are we going to see which division of Microsoft wins the battle? Seems almost like Frito Lay chips. Sooner or later you may eat one of their products and then it is too late! It the mean time you may have bought more than one not knowing which flavor was the “best”.
>>
>>Tom