Good god, you will try to twist this your way no matter what .. I only offer facts.
Remember (second correction), I said Windows not anything else. PHP and Windows. Maybe I should start combining facts from .NET with Foxpro to also try to confuse the issue like you're trying to do..

>rearranged...
>
>> (I DID NOT SAY PYTHON OR ANY OF THE OTHERS, thank you) :
>no you did not. But was mentioned in the post you answered - and I generalized it to "backend scripting". You are welcome.
>
>>Sure, on Windows, VFP is better than PHP because
>
>>VFP uses ISAPI (PHP uses FASTCGI and discourages ISAPI for stability reasons)
>correct.
>
>>VFP can truly multi-thread using a VFP MTDLL and can spawn a background thread (PHP cannot. PERIOD)
>
>That way I would consider hackish and as PHP can use COM as well the most tested ways of scaling
>using other processes are available.
>
>>VFP has had memory garbage collection for quite some time (I believe this is a fairly recent addition to PHP)
>So what ? Others reach vfp/get better, vfp stagnates.
>
>>VFP compiles to intermediate bytecode (PHP DOES NOT!)
>But you can compile PHP with the facebook-compiler down to C level,
>obliterating vfp's P-Code lead, if it is necessary
>
>>VFP has a built-in and integrated database. PHP does NOT!
>For a web backend of moderate to high usage most people will argue for a real SQL backend.
>PHP can use them or SQLite if a lower-end backend is enough.
>Cursors are great client side, but on a web server ? Not really.
>
>>VFP is almost guaranteed to work better on Windows because of Microsoft's long involvement with it
>Read up on SMB2 and file based db ;-)
>
>>I mean, get real. If you've got existing VFP code
>
>That is the reason I gave which will trump most arguments
>
>>and experience
>
>That point is to at least some degree lazyness on the programmers part.
>
>> It sounds like you're getting caught up in the PHP fanboy syndrome.
>
>You could not be further off base... JR is happy using it, I will demand mental hazard pay if I have to code in it.
>But vfp - if not used for data exploration or enhancing existing apps - is not playing in the same
>league of scripting languages like JS and Python any more.
>Look at MI, Generators, Mixins, Monkey Patching methods as well:
>vfp has not grown much compared with that. even the last additions CA and event binding were only "me too".