Documentation / Ecosystem context
Ecosystem context
Where x64base sits, and what it is not trying to replace.
The xBase world is still alive: open-source compilers, commercial platforms, migration tools, DBF libraries, and a great deal of running legacy code. x64base belongs in that conversation without claiming to end it.
| Project | What it is | Overlap with x64base |
|---|---|---|
| Harbour / xHarbour | Mature open-source xBase compilers | Language and DBF handling. Harbour is far more complete as a compiler; x64base is not one. |
| Alaska Xbase++ | Commercial xBase platform | Commercial support and tooling. x64base is not for sale. |
| XSharp | xBase on .NET | Language lineage, different runtime entirely. |
| dBASE tools | Commercial descendants of the original | File-format compatibility. |
| Python DBF libraries | Read/write access to DBF files | Format handling, no engine or shell. |
The actual difference
x64base is the only one of these built so that the layers are the product. The others aim to make the database invisible and reliable, which is the correct goal for production software. This one aims to make it visible and explainable, which is a different job.
The honest constraint
Classic DBF-family formats carry structural assumptions from an earlier era of computing. Widening them to 64 bits is not a recompile; it changes the engineering math throughout — headers, offsets, memo identifiers, and every index backend, each audited separately. That work is in progress and tracked openly on the status board.