To: Tom C who wrote (5022 ) 8/12/2000 2:45:56 AM From: Kashish King Read Replies (1) | Respond to of 5102 I really don't think C# make sense for Microsoft because it is a too-little-too-late attempt to answer Java using Intel as the reference platform versus a VM. Java has one problem worth bitching about and that's performance running desktop applications. In a distributed environment, particularly if a lot of database round trips are involved, the performance could be characterized as too fast: you're never waiting on Java, you're always waiting on the network and the services with which you are communicating. That Java runs at 1/3 C++ speed is not an issue, in that environment. Now, let's add garbage collection, security features, class loading, introspection and so on to C++. Don't think you'll see that running any faster than Java. Fast forward to C#: same deal. So this is really just a ploy on Microsoft's part to throw a monkey wrench into the Java gears. If they were interested in innovating they wouldn't be ripping off Sun with a poor man's Java. How do they explain to the legions of veebeesters that they need to throw away that system and start from scratch with a new language? They led them down the garden path and now they're leaving them standing at the alter waiting for the puppet master to issue the next command -- how's that for mixing metaphors. C-Flat is going nowhere, slowly. I won't even waste my time with a demo it. I cancelled my MSJ subscription six years ago so I won't even read about it. That reminds me, where's my JDJ?! Java went from absolute zero to white hot and they are crushing Microsoft in distributed application development, to wit, the Internet. J2EE is THE standard. Java is putting Microsoft back in the Applications box where they belong.