[chrisweekly]

> Development is already slowing down and focusing on fixing bugs

Yes - because it's stable and powerful. So grateful they care about quality and are not becoming bloatware / chasing random features.

As for the plugin ecosystem, it was always inevitable that a significant portion of them wouldn't be well-maintained and wld become obsolete.

As an Obsidian early adopter and heavy daily user, I have only good things to say about the core software and the handful of high-quality community plugins that support every workflow and use case I desire.

[slightwinder]

> Yes - because it's stable and powerful. So grateful they care about quality and are not becoming bloatware / chasing random features.

Yes, but this is only good for the satisfied users. Users who wait for certain "promised" features, might slowly become unhappy over time. Other will simply not find what they need.

I guess a bit of the problem is that Obsidian exploded in interests far beyond what the devs imaged, and now they are left with multiple different groups which are all not maintained equal well.

> As for the plugin ecosystem, it was always inevitable that a significant portion of them wouldn't be well-maintained and wld become obsolete.

Then remove them. It's not good if you offer the users add-ons which are not even working anymore.

[chrisweekly]

There's a bright-line distinction between core plugins (official) and community plugins. It's not the core team's responsibility to determine whether someone might be getting value out of a community plugin. TBH it seems like you're trying to find things to complain about, but have yet to raise anything substantive.

[slightwinder]

Community-Plugins are also offered and managed through the app itself, so they do have some sort of responsibility for what they make available.