Interesting quote and certainly can apply to some people, but this behavior could also be considered as "acts of service" type of "love language". You can take any endearing and genuinely good behavior and make a toxic version out of it.
My SIL queues up household tasks when I come over. "Hey I got this new thermostat, can you help me put it on?" kinda stuff that she could do herself but she knows that's what makes me feel fulfilled.
Someone who stops at road side, and helps a stranger with a tire iron, likely has no reason other than it just feels the right thing to do; the recipient's smile being the most precious payment they could possibly receive.
> In the myth of Narcissus, a beautiful young demigod who saw his own reflection in a pool of water became so enamored with it that he refused to move. He rejected the advances of beautiful young women and eventually wasted away, unable to break the spell of his own image.
Used Obsidian (paid for commercial and sync) for years, loved it, and evangelised. Ango and team seem to have genuine integrity.
Am moving to Emacs, org, plus self-built elements, however. With much pain.
You see, what is /not/ self-guaranteeing about a full Obsidian life-organising workflow is the necessary reliance on plugins and their quirky configs. I felt as locked in to the ecosystem as I ever did with services that ‘merely’ used a proprietary storage format.
I know others in the same boat. Obsidian’s long-term legacy may well be primarily as a market-maker for Emacs.
Sure, but the primary difference between what you're talking about is ecosystem lock-in vs file lockin.
both can be postured as a labor-saving measure, exposing user data to users is an additional burden on developers. Designing an extension system that is easy for other products to use is an additional burden on developers (& developer relations! And marketing! Other products won't just adopt your extension system willy-nilly)
But switching from obsidian to something else is so much easier on a file-level than say, google docs or whatever other super-proprietary system that's being used.
I'm very wary about adjusting my workflows to depend on flimsy or proprietary ecosystems. I don't really use vim with any plugins. I don't really use obsidian with any plugins, although I'm slowly trying to ease up to using a couple that would be big QOL improvements.
Striving for standard interfaces/workflows is a good thing, but I don't think emacs is that. vim isn't that. They've just cemented themselves as the de-facto.
I'm using vim bindings in obsidian, for what it's worth. I'm not re-learning a whole other set of keyboard shortcuts (although obsidian's is quite lacking)
