Ryan Randall :OpenAccess: :hc: on Nostr: npub1qmcpm…yv6gx Really, truly, what it comes down to for me is that the Tasks ...
npub1qmcpm5qnud8p4az4enwx0arcnw38jxyq70yzphj5xdn9va6q8s4qryv6gx (npub1qmc…v6gx) Really, truly, what it comes down to for me is that the Tasks plug-in ( https://publish.obsidian.md/tasks/Introduction#Task+management+for+the+Obsidian+knowledge+base ) works better than all the other approaches I've tried, including OmniFocus, etc, etc, etc.
But I feel like the plug-in's success is largely separate from the app itself.
What I vaguely resent is that Obsidian's devs have quickly established such a critical mass, plus a secondary " influencer / explainer" ecosystem, to effectively suck most of the oxygen out of the "markdown, but slightly dynamic" possibility space for the next few years.
It feels like they stumbled into doing something awesome, but aren't yet temperamentally or technically equipped to handle users outside a very narrow slice of people—to everyone's detriment. The answer is always "use a plug-in!"
Anyways, I wouldn't advocate for others to use it. I'm just grumbling while also explaining what about it appeals to me, despite the shortcomings.
But I feel like the plug-in's success is largely separate from the app itself.
What I vaguely resent is that Obsidian's devs have quickly established such a critical mass, plus a secondary " influencer / explainer" ecosystem, to effectively suck most of the oxygen out of the "markdown, but slightly dynamic" possibility space for the next few years.
It feels like they stumbled into doing something awesome, but aren't yet temperamentally or technically equipped to handle users outside a very narrow slice of people—to everyone's detriment. The answer is always "use a plug-in!"
Anyways, I wouldn't advocate for others to use it. I'm just grumbling while also explaining what about it appeals to me, despite the shortcomings.