The case for incorporating key plugins into the core program so they are present by default

Use case or problem

I am a recent convert to Obsidian after decades of using OneNote and Evernote before that. I also have been using Complexities. A consistent “con” for the case against adopting Obsidian for information management is its need to find and then incorporate plug ins. This contributes to both a steep learning curve in the app’s use and increasing the length of time needed to customize it to one’s needs. Obsidian is now mature enough and its developers should have enough information to know which plug in is used by most of its users. These key plugins should be incorporated and updated into the core program. They can be turned on or off if the users would rather not use them. Examples of some key (to me) plugins are editing tool bar, cards view, calendar, image converter. It would seem to me that everyone would benefit from these plugins. Inclusion of the best or most flexible of a key or essential plugins as default would not exclude developers from developing other plugins that may operate similarly but these would simply reside where they do now - in the Community Plugin space from which they could be added. Basically, I am requesting the expansion of the Core Plugins catalogue.

See this topic: