Kevin,

>I'll grant you that when I first looked at .NET in 2001, my reactions were not totally unlike yours. But I was looking at it from the wrong angle, partly because I had fallen into the 'Fox-box', and (to use JVP's prior post), looking at things far too tactically and not enough strategically.

I understand your reasoning here. You had to switch from one way of thinking to another. From the FOX way to the .NET way. Sadly this is the only practical way you can do it.

Not only does it have implications of productivity here, but more worse is that you (not meaning you personally, but developers in general) accept. In fact you (again not you personally) accept that you've got work the way how the tool works, while the tool should work in they way you build solutions effictively.

This is the same with using standard software with tailor made software. With standard software you've got to adjust your work to the tool. With tailor made software, you adjust the software to how you work.

Simular, VFP's RAD capabilities alow you more to work how you want to work, as with .NET you have way more restrictions.


I expect the .NET team to adress these points in the future, or maybe another vendor with a .NET language will.

Walter,