Short term - yes. But long term? It seems there is no point in planning to use a software for years now. And I don't like to migrate my knowledge base to new tool, every 2 years. But is there a way other than mastering org-mode on weekends?
Short term - yes. But long term? It seems there is no point in planning to use a software for years now. And I don't like to migrate my knowledge base to new tool, every 2 years. But is there a way other than mastering org-mode on weekends?
1. a quick tutorial will be plenty to get you started: https://mickael.kerjean.me/2017/03/20/emacs-tutorial-series-...
2. if you don't want to bother learning emacs, no worries, use one of the web apps such as the one I built: https://demo.filestash.app/login?next=/view/org/emacs.org#ty...
The rule still applies: whatever you chose, do not become dependent on a SaaS offering. The problem is in the name: service. A service is something other people do for you. They can stop at any time.
The problem is in having a trustworthy vendor or a healthy marketplace of alternatives you can switch to.
An important aspect of most SaaS businesses is that they're not commodities. It's a core part of most SaaS business models - they're purposefully sticky. When you become dependent on one, and it shuts down, or gets acquired, or decides to discontinue the features you care about, there usually is no drop-in replacement. There may not be a replacement at all, for the combination of features you need. And whatever alternative you find, migrating all your data is usually difficult, and often not possible.