>>>>>>>>So how does .NET differ from, say, VFP ?
>>>>>>>It's in the philosophy of application. Either local compute, storage, communication, or remote.
>>>>>>So how do they differ ?
>>>>>>The same choices are available for both platforms.
>>>>>Look ahead, Viv. It's in .NET's design. If you can't see it ... I can't help you.
>>>>
>>>>Why not?
>>>
>>>
>>>It's one of those things you either see and understand, or not.
>>
>>And there was me thinking that the idea of UT was that people who understand things can explain them to people who do not :-{
>
>People who understand things can. People who bloviate and pontificate in areas where they have great faith and are in the comfortable position of not knowing what they don't know can only fall back on the truism that if you do no understand what they are saying they cannot explain it to you ;:-)
>
>As people who have actually working with the technologies know, "the cloud" is a marketing strategy and an option but is in no way part of the decision to design using WebAPI services etc. It is just another way to store and maintain data just as a web hosting service (or a remotely maintained leased server ) can be a cost effective alternative to in house web servers. It is a marketing strategy, I believe, more than it is part of the design to stamp us with The Mark of the Beast.
>
>Whatever one thinks of .NET or the abandonment of VFP by MS, developers' decisions to leave VFP can hardly be seen as part of a Satanist plot to set more lucrative strategies ( like open-source stacks :-) or be the result of the developers in questions not having a true appreciation of the wonder that is VFP ( want to do a "Where are they now" of the best VFP developers of 10 or 15 years ago? )

All true.
'Bloviate'
Had to look that one up. But, to be fair, it did say it was an Americanism :-}