To make things a bit clearer.
Reason for removing TXT support of player database:
There is individual char_server and char_server_sql, we needed double work for char server edits
Each time a new system appears like mercenaries, we would need to implement both sql and txt saving/loading, increasing our workload
The compiled code is actially different of a SQL and a TXT compiled servers, we need to maintain more project files, people asking for support need to provide additional information etc.
Using SQL is far more flexible because of CP and web services, and should perform better, and be safer ( less likely to loose data ).
They are frequently modified at the runtime.
Maintenance of SQL databases are easier ( deleting old/unused logins, purging invalid data, and etc).
There are TXT related bugs, and unimplemented TXT features such as mercenaries.
Now lets look at the db folder:
db folder does not need maintenance from the server owners.
Supporting db folder in txt format does not increase our workload much, the format is rarely changes, we do not need more project files for that etc.
It is fairly easy to convert some of the dbs to SQL in case of somebody feel more confortable with that
They are not modified on the fly, moreover the server does not modifies it at all.
Does not have bugs or unimplemented features.
Aegis also use flat text files for the same thing.
All in all, if somebody fond of SQL db's, he can use it. But dropping TXT support for db folder provides us (developers) only little (or almost none) decrease in our workload, but degrades eA compatibility, makes people harder to switch from eA, and causes additional workload for server owners too ( They now just need to update item_db.txt and they are done. But with SQL dbs, they need to update item_db.sql and import it afterwards, +1 step) . Moreover it makes it harder for those who used to the txt format, to do db work.
One of your reason was, it is easier to edit some dbs in SQL. Well.. if you use a GUI maybe. BUT:
There are tools available to easily edit TXT format too ( database editors )
If you feel more confortable to edit something in SQL, you are free to do it that way and export afterwards ( i.e. mass edit ).
Maybe you feel that db developers would have double work if we maintain 2 dbs. Well, no. They only need to maintain sql, or txt. The one they prefer. And if we provide conversion tools, they can keep updated the other one. ( I think there are some pearl script available to convert dbs, however it would be maybe better to provide binaries, it would be easier to use for all ).
That is my opinion.