Im sharing some thoughts and possible solutions on this. I'm validating your experience on Windows as well, and taken some L's because of it. Our time, commitments to others, and workflows are important and I feel frustrated when I take L's because of external factors, like software. However, I think there is a way to balance these immediate needs and frustrations with the future benefits our time and contribution to Dendron will bring. I started a relationship with Dendron after investment and experience through multiple notekeeping systems. I came with some domain knowledge of memory and cognition, and found the design values of Dendron to match with these principles. The details Kevin puts into features showed me he's thought deeply about and understand these principles. I also believe Kevin has thought about Dendron's resilience during his design process. The markdown, attention to compatibility with mobile Markdown apps, and keeping user syntaxes compatible with market rival Obsidian are all strengths of Dendron, by design. Due to these factors, I felt comfortable committing my time and notes to Dendron, and to make Dendron part of my workflow and inevitably, part of my emotional life. And despite the errors that has been happening and the frustrations Ive been experiencing, I see it as a small bump in the long road. When Dendron isnt working, I pull up Obsidian to access my connections, or Listary-lookup Typora to look up individual notes, continue with my workflow from there, and then after my workday is done and I have some free time, give feedback and bug error to this community to complete the loop. Dendron has never disconnected me from my second brain that I built with Dendron. Dendron allows these alternate workflows by design when Dendron itself breaks, I credit that to the strength of Kevin and the Dendron team's vision, and hope people take this into consideration in your decisions.