Nick Ball wrote: > Have a read of... > > http://www.codeproject.com/dotnet/WhyDotNET.asp?df=100&forumid=49724&exp=0&select=901792
Not very convincing. I think the main problem for me is I have a _MASSIVE_, optimized library of code already written in C++ with features not available in .NET. I'd feel naked. I feel naked using Delphi and VB too (I do most of my dev. work in C++). It isn't that I wouldn't be able to write code, I would just be missing most of what I already rely on. The only things I don't have in my massive library are SOAP/WSDL stuff - which is the only thing that would cause me to interface with .NET...and I'd probably wrap the functionality up so I wouldn't have to touch .NET more than one time. Others here seem to be expressing similar problems/concerns. They are concerned about productivity issues. All the stuff they are familiar with has to be re-learned or ported. Both take time. Time usually better spent working on the next feature or project. -- Thomas Hruska CubicleSoft President Ph: 517-803-4197 *NEW* VerifyMyPC 2.4 Change tracking and management tool. Reduce tech. support times from 2 hours to 5 minutes. http://www.CubicleSoft.com/VerifyMyPC/
