>>You can use plain JSON in memory and store that in localstorage or session storage for local persistence - it really doesn't get much easier (except for browser storage size limitations that affect all storage tech).

I used to regard local cursors that can span to disk as an important VFP advantage, especially in days when the NET typed dataset was memory bound and the browser was all about data snapshots and round trips.

In hindsight we were all privileged to be part of the world's move from early Fox days when my first development machine had 1 meg RAM and a 20 mb drive (yes mb not gb, younger folk!) towards modern phones/devices that make no great distinction between RAM and persistent storage, with my current phone coming with 64GB and allowing another 256GB SD. These numbers are high enough that memory/storage barely features in consideration for business apps in 2018.

Except that it's not always easy to harness all this vastness except via native apps- that still lack a killer IDE IMHO. The youthful exhuberance of Borland, Fox and even MS seems to be replaced by slow bulky consensus (lowest common denominator) and Rube Goldberg fascination with complexity.

Meanwhile I find myself going back to the future: having been an early adopter of the cool web, current strategy is to bring apps that involve detailed user interaction rather than just data viewing, back towards Windows GUI to be exposed widely via RDS or cheaper alternatives now cropping up. Easily hosted and managed by clients, or Azure ticks the box for those expressing interest in SaaS.