I also think as task to be a core functionality and for me tasks are typically related to any block in any note. Once again markdown is the limiting factor because it’s an unstructured graphical text representation with pretty loose syntax, and until people are afraid to make exotic extension to it (or accept that companion structured data is needed) they won’t be anything more than paragraphs with a square next to it. Even HTML allows more expressivity, semantic and extensivity.
I’m with you on the distinction between what should be core and plugin. For me plugins should be exclusively enriching concepts that the core introduces and standardise. When plugins starts to offer core and fundamental features it means the core is mostly empty, doesn’t drive the developpement. Having to spend time on different computers installing the same plugins and configuring them the same way is a bit annoying.
To push the concept further, core functionalities have the advantage of working in search, in editor, in auto-complete, everywhere, and then plugins can make the experience even richer by building on the strong foundation. When a functionality is brought by a plugin, it will only exist, work, sync and be extended inside that plugin. There is no commitment that the plugin will continue to exist or that the core won’t break it in the future, no guarantee other views will work with it.
I know developpers are just two and things won’t happen until long term, but i don’t see any blog talking about the future, about long term design directions, about roadmap or architecture. If i knew stuff is coming then i will stay for it and support it, but if all changes are little improvement here and there for the mobile experience, but things related to organisation workflow, knowledge management or big changes are to never happen or always as a “you can make it as plugin”, it will be hard to keep investing in the product which has a super promising start but needs to follow the curve and not stop in the middle.
So I hope they see obsidian as mid developpement and have a rich feature set for version 2 and not as a finished product that just need polish 