I mean, this is why I think PDFKit is a good comparison. Could you render your app's entire UI as a series of PDFs? Absolutely! Should you do that? Uh, probably not. You should use the native controls Apple gives you for buttons and dialogs and input fields and so on.

But WebKit is the native UI for HTML, and Markdown is intended to be transpiled to HTML.

▲

stavros 5 hours ago | parent | next [-]

It's irrelevant what Markdown was meant to be transpiled to. When people say "Markdown support" these days, they mean "rich text support", since Markdown is actually just ASCII. It is ridiculous to need a Web renderer to render rich text, on any platform. Even terminal emulators can do it.

	▲	4 hours ago \| parent \| next [-]
		[deleted]
	▲	Wowfunhappy 5 hours ago \| parent \| prev [-]
		HTML is basically analogous to RTF, no?

▲

carlosjobim 4 hours ago | parent | prev [-]

If think that the MacOS GUI is actually entirely rendered as a series of PDFs, if I have understood things correctly.

▲

jonhohle 4 hours ago | parent | next [-]

That’s how it originally worked, but Apple has moved away from PDF to other native GPU frameworks for drawing. Now window content is stored as bitmaps instead of redrawing vector instructions.

▲

mpweiher 3 hours ago | parent [-]

That's not how it ever worked.

Quartz is a vector drawing engine whose output can be captured as a PDF and which is closely aligned with the PDF imaging model.

Window content was always stored as bitmaps.

	▲	jonhohle 2 hours ago \| parent [-]
		You’re correct. I meant to say textures, but even that isn’t completely accurate. AppKit used to generate the bitmap directly through CoreGraphics (PDF model). Now it uses Core Animation and Metal and no longer draws the bitmap directly.

▲

mpweiher 3 hours ago | parent | prev [-]

You have understood things incorrectly.