An open letter to the Obsidian team(emilebangma.com)
emilebangma.com
An open letter to the Obsidian team
https://www.emilebangma.com/Writings/Blog/An-open-letter-to-the-Obsidian-team
3 comments
This is a good letter. I literally just submitted my own plugin https://github.com/MaxwellsEquation/LaTerM-obsidian and it took me thirty minutes to get past the validation script, as it seems to check for "plugins's" in the script in some places, while the template specifies "plugin's". The process should probably be overhauled.
Good catch, that typo is fixed now.
I use Obsidian, but don't have much invested in any plugins or themes, so maybe I'm just not informed enough on the backstory here.
While I can't disagree with anything said, it's also not really unique, is it? This is the classic open vs. closed ecosystem debate - do we protect users with a walled garden or do we let them load up anything they want, even if that turns out poorly for some subset of them?
If you're going to plead for some kind of change, I think it would be more helpful if you had specific action items. A willingness to help is great, but how do you propose to help? A lot of people are technical, that's awesome. What are they going to build to fix the problem? Who or what is preventing them from doing that now?
While I can't disagree with anything said, it's also not really unique, is it? This is the classic open vs. closed ecosystem debate - do we protect users with a walled garden or do we let them load up anything they want, even if that turns out poorly for some subset of them?
If you're going to plead for some kind of change, I think it would be more helpful if you had specific action items. A willingness to help is great, but how do you propose to help? A lot of people are technical, that's awesome. What are they going to build to fix the problem? Who or what is preventing them from doing that now?