>OK, now if we let the dust created by all the BS you just wrote the simple answer would have been nothing.
>
>>>Applications for other platforms.
>
>You are in the same boat here, or you have problems understanding client and server side. Your application on the client side is just HTML + JavaScript + JQuery and controls, nothing that can't be done with Foxpro on the server side and both require Windows in there, only the client platform can be anything in both cases.

Let's design a simple web application and you do it using VFP9 SP2 and I'll do it in ASP.NET shall we? You do yours in the VFP IDE and I'll do mine in VS2010 or VS12RC (oh yeah - they're still making new versions!). We'll use the Northwind database (use MDB or SQL or put it in VFP database - developers choice).

Lets give a user the ability to pick a customer and then show him all his records in nice sortable grids. Let him edit current records and add new ones. Lets publish to a convenient webserver.

How much effort is there to do that in VFP9 SP2?

How much do you think there is in ASP.NET?


>
>>Applications customers will foot the bill for.
>>
>>Applications IT shops will let you deploy.
>>
>
>Those are not technical issues thrown in the conversation to mud the waters.

And absolutely valid issues.

>
>>Applications using a far better development environment than VFP had. Better debugging, better intellisense, better testing, better Source Control integration, better...
>
>And missing better local data handling, better dynamic programming etc (and I recognize both, yours and mine, things are subjective)

.NET has local data handling if needed (generally it is not). I have found no reason macro substitution was a necessity.

What else?