7 ms·
Author here. One practical reason to switch to Notable from Joplin is that notes in Notable are just plain files on disk, and that's extremely powerful. In Jopl
by fabiospampinato 6y ago
Author here. One practical reason to switch to Notable from Joplin is that notes in Notable are just plain files on disk, and that's extremely powerful. In Joplin instead you can only open notes one by one in the default app, the difference is that Joplin essentially copies the note out of its database, opens that in the external editor, and then synchronizes its changes back with the database. In Notable the files on disk _are_ the database.
In practice this means that you should be getting better startup times with Joplin's approach, but anything that has to do with manipulating a lot of notes with an external tool is trivial in Notable, but you can't really do it with Joplin.
Plus each note in Notable contains its own metadata in the YAML frontmatter section of the note. Last time I checked Joplin just doesn't expose this at all.
I don't know enough about QOwnNotes to compare it in the same level of detail.
If you want to give Notable another spin you should probably try one of the alphas of v1.9: https://github.com/notable/notable-experimental/releases https://github.com/notable/notable-experimental/releases the app changed quite significantly. For one now all shortcuts are customizable like they are in VSCode, and theming too is pretty much like in VSCode, in fact I ported all themes from VSCode to Notable, they are installable via the "Theme: Install..." command in the command palette.