Entering the world of Visual Basic after three years with Delphi

I have worked with the Delphi Windows programming tool as long as it has been on the market. However, since one month I have VB on the screen.

What is the difference. Is the enemy better or worse?

Well, it is different. Very different. And also very much the same of course - the products always upgrade with the best from the other and the Windows API blood runs in both.

The first weeks were tough, keeping back irritation over what seemed to be a very irrational cousin from the country. But it is ok now, it feels more like a challenge.

What is good with VB? Well, it is the flexibility of the platform. Abundance of solutions, many for each problem, many smelling Microsoft lack of elegance, but still working. No piece of code would dare not to obey Bill Gates in the end.

Debugging tools are really good, the most amazing trick is the ability to move back the execution point in the source code and take a new turn past the corrected part of the code.

The really professional inheritance/component workshop of Delphi is absent, but the interface device and some other things could compensate a little. Delphi 4 has copied many good things for the desktop/debugging situation, but VB still has more of visual construction aids and wizards.

The VB code lacks elegance and the printouts lack basic typographical qualities, although it can be nice thing not to have to declare everything in an interface section.

What really turned me on was the MS-integrated (Rose)-reengineering modeling tool. It really works - after a couple of days I regularly define and extend my project in the modeling tool with graphic overview and implement the body of  the code parts on the VB desktop. And then do the reengineering again to add any new property, method, etc.

An of course Delphi-4 has the same, I found it on the web when I looked for it.