← Back to context

Comment by kid64

8 months ago

'It may sound obvious but the primary way we reduce the risk of supply chain attacks is to avoid depending on third-party code."

What a horribly disingenuous statement, for a product that isn't remotely usable without 3rd-party plugins. The "Obsidian" product would be more aptly named "Mass Data Exfiltration Facilitator Pro".

I've used Obsidian for years without a single 3rd party plugin.

It is possible to make your same point without histrionic excess.

  • Yeah, this is always the response. Usability can be assessed objectively, so you just have low standards.

    • I have to agree that I don't find plugins necessary, and I'm not sure why you're so down on people using a solid backlinking note taker. I don't think I have low standards, I think Roam and Logseq aren't that great and Obsidian is all I need.

    • A more charitable interpretation would be that that have different needs. My keyboard costs more than my computer, but most people probably spend $15-$50 on a keyboard. Even my mouse is well outside that range. Do I have high standards or do I have tendonitis?

      4 replies →

> a product that isn't remotely usable without 3rd-party plugins

That's not even remotely true. Obsidian out-of-the-box is very usable, covers pretty much all use cases for a note-taking software.

I've been using it for ages, and I haven't needed to turn on the Community Plugins switch for anything.

Usually the people I see with tons of Obsidian plugins are people who think "just one more plugin" is what stands between them and productivity.

That's just...what? It's highly usable without plugins. Yes, I use plugins...but that's by choice. Obsidian is still a superior Markdown editor with backlink support, plugins or not.

  • I think you and your fellow commenters are missing the point. The degree to which Obsidian is "a superior Markdown editor with backlink support" can be debated. What I'm saying is that actual usability, in this context, is not a matter of opinion -- see ISO 9241-210, ISO/IEC 25010, etc.. Having said that, I'm glad you're happy.