>Thomas,
>
>> xBase++ (including their server-side web page generation) seem to offer little above vfp9+FoxIncloud for my use cases.
>
>I wonder what this means…

Basically for the use cases I code[d] for in vfp moving to xBase++ makes no sense.
Reasons: end customers have Win server licenses already, so building/supporting a Linux back end is not a great benefit to end user (read customer buying app from my employer). If Metin sells to thousands of restaurants at cheap price, cost savings from eliminating Win server cost perhaps are a stronger argument for him.

If Lianja had offered a native android client including embedded cursor engine, that would have been reason for me to stay there.
>
>Server-side web page generation is a 20 years old tech while FoxInCloud creates an interactive AJAX Web Application with thousands of controls and events out of an existing desktop application.

From what I gleaned, xBase++ is somewhere near asp.net in model, but following basically a "chatty" server directly controlling the browser on client device.

In new dev I (sadly) follow the same model in Java (less discussions if bought out, bringing other partners onboard, payed for by less snappy development), but as I follow "schema-driven" + "DB-first" development not that much slower compared to developing in vfp.

I personally aim for a tech stack with [dedicated] datastore usually instantiated on client (State or Vuex in Vue, Redux or MobX in React, mini-mongo in Meteor) or (if security demands it) on the server. Benefits: Targeting more PWA-like architecture, option of offline work, moving from "chatty" to "chunky" mode of client-server communication, as most GUI changes are fired directly on changes in client data store, not after server call....

That datastore should be "lean" IMO, comparable to vfp cursors, NOT ORM-generated object graphs, as those can suck up CPU cycles like crazy. Fat chance at the moment, I know....

Back to xBase: they claim to have more than PHP from turn of century: websockets able to drive RPC calls or XML/JSON endpoints done via compiled-to-machine-code (more secure/faster/non interpreted compared to classic asp) server pages - more ASP.NET than classic .asp.

Dynamic sites, data-driven sites, generated sites - but as I argue to stay in vfp and add FoxInCloud and NOT move to xBase, why go into detail?
Leave out areas where I consider xBase++ has benefits above vfp like multiple inheritance, ISAM on Postgres or Linux backend ?
Not my style ;-)

>
>How can you compare these, and what is above what?

You gather feathers in the hat / black eyes on both approaches, weigh and count them according to your use case and decide ;-))