If you start a new application, I see no reason not to use something better - that supports goodies like transactions and SQL . For a new stand-alone application I'd choose embedded-firebird with no hesitations. If later it is decided to make the application multi-user, the change to the client-server version of firebird would be easy.
Its a question of the right tool for the job, not a question of is a screwdriver superior to the hammer. Each tool fits a different use.
I'd use TDbf for a networked 5 user LAN environment, but if you want something that works under more latency, for instance over the Internet, or if you have more users you'll probably want a client-server transaction based DB model.
If you want a single user application (or a few networked users) that is database enabled and doesn't require the end-user to know how to set up a database server, then products like TDbf are the answer.
This discussion seems reminiscent of old discussions over networked use of Paradox versus going with... what was the C/S database engine Borland supplied?
So if you want to compare TDbf you'd compare it against text-file based database engines, Paradox, dBase components, etc. Other than the possibility of porting an old open-sourced text-file database engine for Delphi, I think TDbf is probably unique in it's class for Lazarus support.
As a producer of commercial software for non-technical end-users, I'd never consider producing a MySQL, Firebird or MsSQL application. The end-user level of expertise is too high for my market. With TDbf I only have to let the user pick a directory to store the data in, and provide an easy way to do backups.
On the topic of embedded firebird, I've never used it in Lazarus (is it even available and stable in Lazarus?) but the comment on their website "The embedded runtime is < 2 MB" is reason enough for me to stick with TDbf. My total app with TDbf is smaller than that.
-Tony
