>>Just as an added comment: although possibly any tool can be used to handle stateless app development, including VFP, not every development tool is built to help manage the process for the developer by providing an intuitive IDE for managing server or client side coding issues. For example, (1) Putting a button on a form in WebDev and opening the associated code window for it provides the developer with joined coding windows offering server-side code to run or client-side code to run. And (2) the server side has an engine to manage the users connected to it, just to name these 2 features. VFP doesn't have any of that. So yes you might do it in VFP, but, no, its not designed for that. WebDev is.
>
>True. For client-side stuff (namely, .js and .css files) I use a text editor, not VFP (I could use VFP's editor, but this one has some neat formatting features, and it cost only about $25).

WebDev does a lot more than just help build a website. For example, you build and test your website in WebDev and then you can upload it to your server and it implements it on the server. If you make a change to your website on your machine you can just ask WebDev to upload that change to the web server and WebDev will implement it. WebDev automatically generates Ajax code from your WinDev cove and you can add in PHP or Javascript or whatever alongside your WinDev coding. You just cannot compare this type of IDE to writing code in a text editor and then manually uploading all your work. Just because you can, doesn't mean you have to :)

Disclaimer: I am not a WebDev or WinDev expert :)