(I apologise if somebody already suggested this, I searched but failed to find anything).
So, my question is why not implement Obsidian as a VSCode extension? In that way the Obsidian engineers may focus on the features that make Obsidian unique and leave general editing and visualisation stuff for VSCode to take care of.
Is there some technical problem? If so, please explain.
Exactly the point I’m trying to make: VSCode is a reasonable text editor and substantial resources are dedicated to its further development. Why the Obsidian community doesn’t take advantage of this (free) offering and focus its (comparatively limited) resources towards strengthening its knowledge management-related features? Why lose time re-inventing the text editing wheel?
(I don’t mean to sound pressing, I’m just interested in the technical reasoning behind this choice).
Off the top of my head:-
Foam already exists
It reduces optimisation potential
It makes creating mobile versions harder
It reduces the size of the potential user base. By quite a lot I should think. I certainly wouldn’t consider it.
Definitely DO NOT WANT Obsidian to compete with or go in the direction of VSCode.
I also don’t want Obsidian to be a VSCode extension. That doesn’t make any sense to me…
Obsidian is already awesome and does what it does really well! It’s so easy to use, has a great UX/UI, and dead simple to setup and get started, I think those all lead to a potentially wider adoption among non-tech users.