Hi Daniel,

Thanks your feedback is highly appreciated.

> Most of VFPers came to VFP for the speed and usabiliy. Which was unmatched when it comes sheer database mangling. Until a dozen of years ago, when VFP database
> sizes became limit for a lot of us, there was no better tool to interactively investigate data.

I agree, the same was also true with Visual Objects, maybe not to the extend VFP dbf interaction evolved, but it was pretty decent speed. One of the features for DBF that is on the to-do list is the FlexFile (similar to Rushmore) utility, that can also re-use memofields and keep them un-bloated.

> The ability to produce a code-based application that would compound the result of these data-massaging actions (dbfs either locals or as
> SQL-engine downloads and then, on a second step, local rushmore-sped-up local sql command) has been a joy to work with.
> But sure VFP is now showing its age now:

Yes it is showing its age, but it is still a remarkable tool. Coming from a Visual Object environment, there are still people that swear to it and keeps on holding back due to some 3rd-party products that are not yet available, but they are slowly getting ported.

> - the speed of the interpreter is on par python. But yes that's interpreter speed, and C++ speed improved are NOT simple (fll).

That is the beauty of X# since its core is just a c# in XBase syntax, and 64bit is already available even for DBF access and Unicode.

> "Premature optimization" is definitely NOT a VFP way and part of its great success back in the years. Yes a lot us are all followers of Donald here (Knuth edition...).

I agree, but at least X# gives one the ability to optimize in a stepped approach, maybe initially focus on the bits that would show the best improvement etc. and then only focus on UI and other processes.

> On the same line, having a fast and decent way to produce declarative UIs reasonable fast and then later on move the GUI stuff to WFP
> when appropriate would be great. I am certainly pushing the enveloppe a bit here. But we are on a forum aren't we :-)

Well, X# already support WPF, so it is for the user to decide when they want to do such a migration. It also already support NetCore, so it is ideally positioned to take XBase into the future.

Kind regards,

Daniel