>And you think that developers really have a choice after the wheels are in motion.

Yeah I do. If a product really sucks and can't cut it, you bet that developers will get a say. As it is developers are quick to point at technology that sucks and without developer support a product like .NET would have never gotten of the ground.

Microsoft caters to developers and tries to win their support with marketing and incentives and other tricks, but at the end of the day if the product was really inferior, it would still fail.

The problem <g> is that .NET is not an inferior product. Sure it has its rough edges and there are plenty of people who don't know the weaknesses and have signed off on them anyway. But the reality is that .NET is being used not because it's crammed down developers throats but because developers have chosen to use it and there is support behind it. Go to a conference like TechEd or PDC and check out the enthusiasm at these conferences. It's something you will not find at Fox conferences any longer unfortunately. It was not that long ago (in the late 90's) that this was the case.

These are not people following the party line because their management told them to but these are people who want to be doing this stuff. The same can be said for the Java community so this is nothing unique about .NET. But it is something that's generally lacking in the VFP community.

This place right here is about the most active VFP community around, but beyond that it's a wasteland.

>1. Sequential execution
>2. Repetitive execution
>3. Conditional execution
>
>Nothing new in that department for many years.

I don't agree with that. Especially if you look at ASP.NET and how the engine works it doesn't fit that model at all. Although the end result may be the same, the development approach is much more logical than the typical Web development approach. Add to that the superior design of the platform that was designed from the ground up for scalable Web development and you have something that is very different from the tools we have to use (COM) with VFP (or VB6 etc.).

There are more than one way to skin a cat and some ways are just more efficient and easier to deal with.

+++ Rick ---


>
>Like you said "What are the other options?"
>
>You also said that VFP did'nt get the attention it deserved because of the language. It's not better or worst than other languages or dialects.
>
>The only difference is that VFP is fully geared toward data-centric apps. Besides that it's the same as all other languages:
>
>1. Sequential execution
>2. Repetitive execution
>3. Conditional execution
>
>Nothing new in that department for many years.
>
>It's all in the marketing. It's just a matter of how hard you can push it. And MS can push harder than many enterprises <g>