Marc Clifton wrote: First off, the guy lures you into the idea that incredibly powerful tools waste time because they're so hard to learn, having so many features. Right, he even comes along with a software development process (Extreme programming) and compares it with a tool (a debugger). People use a tool for a specific reason. It's just a tool. It does not say anything about programming abilities. In 1989 when i was programmming 68k assembly, you basically had step, step into, run-to-line, print exp, etc.. these commands haven't really changed since then. ______________________________ Java: The living proof Moore's law won't solve all your problems

Kannan Kalyanaraman wrote: I think its a conspiracy from MS to pull some of the c++ developers towards the new language(c#) and I think they have some success on that. :-))) I do not believe in such a thing as a 'conspiracy', but there are definetely strategic reasons for that move. Seriously, with Stan Lipmann in Microsoft and Managed VC++ being the only optimising Language for the .NET platform right now, I feel very content. They have done a really nice work in migrating 'classic' C++ and legacy applications into .NET, leaving the choice up to us. Just see what happens, if you build a language, a platform, a marketing system, a monopoly and fundamentalism: Java - some developers get really tied to that whole look-and-feel programming thing. So it is a great idea to leverage the huge amount of Java-programming people to the .NET platform AND building and own army of C# fanatics ;-) After all, I feel more free on the .NET side: I have more choices, My code is not broken, and I know the MFC code will be supported for a long time, I know Microsoft really puts significant efforts on the platform, I do not live on an isolated island where everything has a "J" in front of everything's names, and people believe Moore's law will eventually solve all their efficency problems. I personally decided to do managed extensions for C++ exclusively, GUI plumbing done in C# only. Also,i was wondering is there a plan from MS to build something like a mfc framework for .net. If MS doesnt do this, I think some 3rd party will eventually do ( Chris Sells is doing one but not sure if its commercial). We should not pollute (sorry for that) the .NET framework with something as ugly (but stable and practical) as MFC...

Com+ is fundamental in distributed computing, whether you use .NET or not, the services provided by Com+ are the fundamental thing (like distributed transactions, object pooling, the easy thread development architecture, etc..), which were not supplanted by any new technology (yet). In .NET you can write Serviced Components (this are the Com+ components that we write today in Visual C++, Visual Basic,..), these will run inside Com+ and can take advantage of the services provided by it. Right now there isn't support for statefull components, in the sense of J2EE, but microsoft it's working on a new technology that permits something like this, I can't remember the name (something like "Object Space" or so). The idea of statefull componentes is just the opposite to the spirit of Com+, where one of the rules is "do not maintain state" (see Transactional COM+: Building Scalable Applications by Tim Ewald http://www.amazon.com/exec/obidos/ASIN/0201615940/qid%3D1013822174/ref%3Dsr_11_0_1/103-4000867-4379823) Hope this clarify a bit. (and sorry about my english :) Andres Manggini. Buenos Aires - Argentina.