It's one of these features that, all things being equal, we'd rather have than not have, but it's obviously not trivial to add it when the app wasn't originally designed for it.
And the previous comments were claiming that this project's data was 'proprietary' and not 'open' and the situation was inexcusable, basically because they assumed a database was this big scary thing (as opposed to an open book). That is a frustrating experience, and yeah maybe indicates that the person telling you how to write software doesn't know what they are talking about (for the folks following along at home, those frivolous cries of foul play were distracting from the real need they had for plain text over a database, someone else describes it quite succinctly a little later)
I think file system vs database storage is very much about trade-offs. Unfortunately the debate descends too quickly into who is right and who is wrong.
It's always difficult for developers to talk to users who often really don't know what they are talking about. I know that very well.
The only thing you can do as a developer (if you have time and patience) is to translate what users say into the closest thing that does make sense in terms of trade-offs.
But nobody is always patient.
Not sure I agree. Here's one comment by the developer (laurent):
"Ok, there's so much wrong in what you write about that it's hard to know where to start. I guess it would help if you had a clue about what you're talking about."
https://discourse.joplinapp.org/t/why-im-leaving-joplin-for-...