PHP dBase as an alternative to SQLite

I have read several comments here that dBase is a dead system and no one use it anymore. I compared dBase and SQLite in php, and in my test dBase has many advantages over SQLite and similar systems:

Its database file is much smaller
Writing to the file is very faster with using a lesser amount of memory
Growing the file size has a negligible effect on the query.

I admit that SQLite has a wider range of commands for a better flexibility; but what can be the reason of unreliability or incapability of dBase which sent it to the background?

I have no idea about concurrent connections (though SQLite has serious limitations too). Please comment on this issue.

Summary: Apart from functionality, I just wanted to know what is possible disadvantage of dBase in performance.

Solution

If you are working with a single table then you might not find much difference (aside from the lack of SQL command support in dBase), but as soon as you start using relational data and having multiple related tables, use of dBase falls apart. You have to glue all your relationships together in code with dBase where with SQLite you can have full foreign key support and have relational dependencies.

Some might raise the objection that an InterBase server allows you to have relationships with dBase, but that is really outside the scope of what you're saying.

Summary: for single tables, maybe not much difference, for multiple, related tables, lots of of advantage to SQL-based systems like SQLite.