Well, my last post on Delphi for .NET did raise some eyebrows....Was I to hard on Delphi because it was just a beta ? Personally I don't think so, it was not my first disapointment with Borland .NET stuff. And a beta should behave better than what I saw, especially if the release is anounced to be in 2003. Thats 2 weeks to go... Another reason for being hard is something I blogged about before in a comment on this. Imho Delphi people should be more critical to their own tool. I used to be like that as well. Actually I still am, only the direction has changed. My personal history goes back to Turbo 2 on my first PC, I'm still emotionally involved. And emotion is not allways the best driving force.
I was wrong with strictly, it should be strict. Sorry, I did remember the word wrong. The main point I read from the comments is that Delphi for .NET aims at a great backwards compatibility. Nick has a point when he mentions projects which are started now, targetting Win32, and will be ported to .net sometime in the future. Using Delphi is a smoother ride then, and still nothing beats Delphi when it comes to Win32. But what will happen after the project migrated ? You can mix tools on the .net platform by definition. And Delphi with a dispose method named destroy and a visibility specifier private which actually means some kind of internal would raise some other eyebrows. Looking back it it al made sense but what about the future ?
blog on,
Peter