>But what is the attraction of a solution involving a single source ( based on licensing I have to assume Lianja is not open source ) and a small community vs HTML5,jquery with knockout/knockback/backbone, a more robust collection of libaries than I could have imagined and an amazingly vibrant developer community and training resources, prepared to address pretty much any backend scenario ...

IMO the GUI stuff is overemphasized - but I know myself to be biased.
Controller/Router aspects should not be important, but implementation details.
But basic technology having an option to locally at least cache results in a database
is one thing that might make apps preferable to web clients, besides better device/screen utilization.

Almost all apps currently synch too much for my taste, resending already sent info.
Before Lianja I was considerng to develop a library layer to be used in different OS,
utilizing SQLite as datastore to offer callable clients side capabilities
similar to vfp's cursor/cursoradapter querying remote and local data
(after oracle shafted the WebSQL implementation with MS standing watch)

>
>What does LIanja off - not as opposed to Ms / .net solutions but as opposed to all that. ( I don/t ask this confrontaitonally but out of ignorance of Lianja. I just remember people touting it here as "like foxpro" which doesn't seem much of a recommendation )

The stuff I wanted to implement already tested.
Local data and remote queries pushed first onto the equivalent of hard disk, not RAM.
One query interface for local lookup data and remote results - less ORM baggage, more SQL.
IMO the data *structure* architecture making most of device capabilities and network lag.

Couple that with meta-data as in Hank's vision, going much further than vfp ever did,
and you get data architecture pleasing even oracle hard hats if they are not bribed.

The language compatibility aspect is - agian specifiaclly for me - not that important.
Vfp having SQL integrated is probably the best language for them to pick,
but having the option to implement in Python or JScript will make life easier.

Having a locally running runtime driving the app will hopefully give better results
than Titanium or Phonegap - those apps are often desribed as slow.
Having to call through interfaces and libraries will impact Lianja as well,
but I hope that won't be that much of a hit.
I am not one of the gung-ho types and Linaja is still a long shot for me -
but the one I am crossing my fingers for.

regards

thomas