>I don't understand #3. Why do you say stateless web apps won't work?

I am probably obsolete, but I understand that web servers start each response somewhat ignorant of the state of the screen. Some of our main screens are kind of data dense. They are not just data capture and process later. They provide continuous feedback of calculations as data is entered. That is valuable from the customer's point of view.

>
>Some points on your being annoyed by Microsoft....Technology changes, which means tools and languages change. This doesn't just happen with Microsoft. Look at Angular for another example.

I know that, but our app's exe is 50 MB and we cant afford to have to rewrite stuff that already works except for significant improvement, so we are looking for that sweet spot where the tool is improving yet mature, or at least committed to keeping old code working, as has been the case with VFP.



>>We have a successful payroll application developed with VFP and DBFs specifically for the laws of Panama. We feel we have a very good handle on the business problem and are looking to rewrite the application with up to date tools.
>>
>>Requirements:
>>1. The update should be able to run in the cloud or in a customer's server and PC if customer requires it.
>>2. Though the main processes are normally run from a terminal in the office, the app will receive and provide data access from phones and tablets and who knows what else in the future.
>>3. Some of the data capture screens provide immediate feedback which requires a lot of computation, such as significant checking of historic data. Stateless web server behavior is not really acceptable.
>>4. The tools used should be reliable and expected to have a long life left in them. I am especially bothered by MS's habit of periodically making updates to their tools which require you make substantial changes to your code if you wish to use them. Backward compatibility of updates is something we value.
>>5. Developer productivity enhancing tools are a key consideration.
>>
>>All suggestions and comments are welcome.
>>
>>Thank you very much,
>>
>>Alex