>>And either refrain from using eval(m.dynEval) or get religion praying your latest list of functions to include is correct...
>>For desktop install size is becoming less relevant each day -
>>on flapping floppies it was different, esp. in the times before 1.2M ;-)

Agree re eval(); if used to call functions, you need to ensure all potentials are included one way or another.

As for app size: if compact exes can be placed on a server and run across a network rather than installed to every PC, that can be worth tens of thousands of $ maintenance for a dynamic app. Right now we can deliver sophisticated apps on a $50 Raspberry Pi that can provide provides seamless quick file share for apps for up to around 30 users, with nothing needed on the PC. Bloat is also a little bit important under RTS even if you use Refox or VFP Compiler to compress, since VFP usually needs to shell exe content into memory. This is less of an issue as memory footprint of other development options goes up and up; often the clever young things disbelieve that modern apps can make do with 128MB RAM let alone 32MB...