4 ms·
> In the process you will lose links Err, no? They're preserved in the source just fine. > images Good riddance. > Additional complication is, if these are
by Nullabillity 7y ago
> In the process you will lose links
Err, no? They're preserved in the source just fine.
> images
Good riddance.
> Additional complication is, if these are multiple wiki pages, you have to save each separately.
Depends on your wiki system. For example, Gollum[0] (GitHub's wiki) stores everything in a Git repo, so it's trivial to get everything out using your regular file management tools.
> And again, normal users are not going to use sqlite, h2 or derby without having some kind of forms frontend.
DBeaver seems fine to me, and supports pretty much everything.
[0]: https://github.com/gollum/gollum https://github.com/gollum/gollum
- vetinari 7y agoWe are talking about normal users there, not developers. Think salespeople, assistants, project/product managers. They are not going to use git or dbeaver. Nor they are going without their diagrams, charts, schemas or links rendered inline. If you understand this, you will understand why Word and Excel are still a thing.