> The other great use case for Markdown is in a context where you either need or just want to be saving to a plain text file or database field. That’s not what Apple Notes is or should be.
I don't follow why this is a relevant concern for Apple Notes.
By any measure I would argue that Notion "has markdown support". By that I mean: You type Markdown, Notion knows how to render the markdown you type, and you can easily export files in Markdown. However, what they aren't doing, by any stretch of the imagination, is storing your documents in a markdown format on their servers or your device.
There's a third quality that you might label "Native Markdown" where the documents themselves are stored in Markdown. Obsidian does this. I'd imagine products like the Github Issues description field also does this. But I would not require this quality in a product which has "Markdown Support". In fact, I would argue this is the defining difference between saying that a product Supports Markdown versus it Is Markdown.
Its tremendously and obviously unlikely that Apple will be changing the storage format of their notes to be Native Markdown. I also don't think it really matters for a product like Apple Notes; I don't care what format the notes are stored in. Users of Obsidian might care about this, but that's because Obsidian has a different kind of customer than Apple; people who worry about data portability. Totally cool; that's just not Apple Notes.
Its like arguing that Vim keybinds are only interesting within Vim. My favorite way to use vim keybinds is this great Firefox extension; scroll down pages with j, copy the URL with yy... Markdown is more than just a data format; at a much more abstract level, its a keybinding system for text formatting. In Apple Notes today I have to hit Shift+Cmd+H to get a header. I'd much rather just hit #.
I don't follow why this is a relevant concern for Apple Notes.
By any measure I would argue that Notion "has markdown support". By that I mean: You type Markdown, Notion knows how to render the markdown you type, and you can easily export files in Markdown. However, what they aren't doing, by any stretch of the imagination, is storing your documents in a markdown format on their servers or your device.
There's a third quality that you might label "Native Markdown" where the documents themselves are stored in Markdown. Obsidian does this. I'd imagine products like the Github Issues description field also does this. But I would not require this quality in a product which has "Markdown Support". In fact, I would argue this is the defining difference between saying that a product Supports Markdown versus it Is Markdown.
Its tremendously and obviously unlikely that Apple will be changing the storage format of their notes to be Native Markdown. I also don't think it really matters for a product like Apple Notes; I don't care what format the notes are stored in. Users of Obsidian might care about this, but that's because Obsidian has a different kind of customer than Apple; people who worry about data portability. Totally cool; that's just not Apple Notes.
Its like arguing that Vim keybinds are only interesting within Vim. My favorite way to use vim keybinds is this great Firefox extension; scroll down pages with j, copy the URL with yy... Markdown is more than just a data format; at a much more abstract level, its a keybinding system for text formatting. In Apple Notes today I have to hit Shift+Cmd+H to get a header. I'd much rather just hit #.