Hi Hank,

>the official Lianja word:
>PHP, Python and JS are 100%.

Nice - but for the question at hand not really helpful, as there are differences between CPython, Jython and PyPy
which are all defined as "acceptable" implementations of Python.
Running all the selftests without failure is not enough if you want to estimate in advance if some packages can be used as is.

Getting Web2Py, Django or similar to run might not be so important in Lianja, as they offer similar routines in their VM,
but the question is still will I be able to run ***any*** CPython library without major test effort and
will I be able to also add those tools utilizing the C-Interface defined for CPython (and Cython!) like the numerical libs
as well without further thought - giving me relatively easy optimize potential via Cython or C directly.

You might remember from Ironpython that such things are not always possible without further work -
and is something that should be adressed before even deciding to enter a beta effort.
While I can sympathize with the Lianja devs trying to build the best product ASAP,
they must enable me to at least guesstimate the biz value and included risc.

Dancing around with licenses (concurrent changed last when?),
subscription models and cost is even further muddying the waters, but understandable as they need to reorient.
But not giving out tech spex even as a rough draft - nope, won't enter such a test program,
as I will spend too much of my time for unneccessary work (while still whetting my appetite to somehow use the paltform)

>VFP will be 98%: things specific to Windows and specific to the VFP IDE (e.g,, projecthook) aren't there.
>Also the official word: report a ticket on anything that is missing.
>So if your compatibility isn't 100% for that 98%, submit a ticket.

that sounds great (or at least realistic) - even if it puts some of the burden on us.

>There is a ton of stuff added to the VFox languge, as you also might have noticed (from looking at the Recital Commands and Functions). We'll be documenting it in the October (1st) edition of Hello, Lianja (the August issue is about Getting Start with the App Builder; the September issue is about Getting Start with the Cloud. At least that's the plan.)

As most of the customers will be DB devs, why not create a table of all vfp functions and methods,
adding fields for support level (total, partial, different, buggy, planned, none) including a memo field for test routines ?
Each bug found with a routine could be easily added to create a test harness for later versions.
I am pretty sure somewhere in Recital such tables exist, if only to drive their Help ;-)

You should also have a test application setup to build an app in 30 minutes (reuse in conferences, video...) and/or
show how things are done in each language. Worrying from my POV is that Barry did not take the chance
to draft some of the beta testers to give him such stuff in echange for token sum of money or licenses.

Could be lots of reasons for him not to do it this way, but most have some nasty side effects/considerations.

regards

thomas