Big no-no to Joplin for me is that it is using some custom data format (sqlite I think). Why bother? Just give me an app that can handle nicely markdown files, syncing I can do myself e.g. (Synology, rsync) or use some file syncing service (Dropbox, OneDrive, whatever).

Zettlr does the trick for me without interfering with what I write.

"Custom" would be the way Apple Notes or Evernote stores their data in opaque binary blobs. SQLite is standard and you can open it with plenty of third-party tools, but I see your point about plain text files being more convenient for certain tasks.

> SQLite is standard and you can open it with plenty of third-party tools

Tends not to play well with things like Dropbox or Syncthing though. Although I guess you can use litestream or something for the replication instead.

What's the issue? I guess it's just as simple as uploading the .db?

You're changing some note on device A and the same note differently on device B.

Both sync. You now have a conflict.

With text files, you at least have obvious merge strategies. With SQLite it isn't quite as easy.

I still don't mind SQLite in Joplin. It has advantages, as well.

Ah the multiple devices issue. I see...

How about doing everything server side so you are just using a thin client (read: web browser) instead?

See trilium: https://github.com/zadam/trilium