markdown is a markup language 'intended' to be rendered as HTML, WebKit seems appropriate to render HTML

the_gipsy 4 hours ago | parent | next [-]

Still seems overkill. It's just headers, lists, block quotes, codeblocks, and a few inner emphasis and link formatters, basically. HTML is the whole jungle for a gorilla with a few bananas here.

	▲	Someone 30 minutes ago \| parent \| next [-]
		> It's just headers, lists, block quotes, codeblocks, and a few inner emphasis and link formatters, basically That, and in-line HTML. https://daringfireball.net/projects/markdown/syntax#html: “For any markup that is not covered by Markdown’s syntax, you simply use HTML itself. There’s no need to preface it or delimit it to indicate that you’re switching from Markdown to HTML; you just use the tags. The only restrictions are that block-level HTML elements — e.g. <div>, <table>, <pre>, <p>, etc. — must be separated from surrounding content by blank lines, and the start and end tags of the block should not be indented with tabs or spaces. Markdown is smart enough not to add extra (unwanted) <p> tags around HTML block-level tags.” Because of that, I think I would use a html renderer to render markdown. Because people allowing arbitrary HTML opens a huge can of worms I might also whitelist a restricted set of HTML.
	▲	trinix912 an hour ago \| parent \| prev [-]
		It's still going to be faster than creating and moving around a bunch of NSViews simply because the WebView (native WebView, not Electron) renders the entire content at once, directly on the graphics pipeline, skipping all layout and compositor steps that get done on normal NS(Text)Views. The key point here is to use the WebView only for the text view. Where it goes wrong is when people start writing entire interactive UIs in the WebView. The other option would be PDFKit, but most people aren't nearly as comfortable programming with PDF as they are with HTML.

▲

TingPing 4 hours ago | parent | prev | next [-]

More importantly all HTML is valid markdown.

▲

the_gipsy 4 hours ago | parent [-]

Putting HTML in markdown defeats the purpose IMHO.

	▲	Wowfunhappy 2 hours ago \| parent \| next [-]
		I don't think it does at all! > The overriding design goal for Markdown’s formatting syntax is to make it as readable as possible. The idea is that a Markdown-formatted document should be publishable as-is, as plain text, without looking like it’s been marked up with tags or formatting instructions. https://daringfireball.net/projects/markdown/ Using some semantic HTML as an occasional escape hatch is perfectly in line with this overall goal.
	▲	nchie 2 hours ago \| parent \| prev [-]
		That doesn't make it not true though. Markdown generally supports HTML (though oftentimes only a subset), and is typically styled using CSS. Using a web view makes complete sense to me.

▲

tclancy 3 hours ago | parent | prev [-]

That doesn’t track at all. Markdown was created as a simpler way to mark up text than HTML. They are both ways of encoding a document that provide ways to convey intention. HTML is no one’s end goal.