clients should only ever input plain text
it's the application that should decide how it's to be displayed in different contexts
you're fighting the web if you're trying to do it otherwise, but then again, everybody is nowadays...
it's the application that should decide how it's to be displayed in different contexts
you're fighting the web if you're trying to do it otherwise, but then again, everybody is nowadays...
The world wide web is a free platform where you can publish plain text or HTML, but denying that it also became an application delivery platform is fighting against the reality.
I'm an early-internet kid, and even if we are going back to discover the "spirit of the internet", those times are full of contenteditable hacks and custom applet HTML editors.
Being able to edit HTML visually is so common, be it a simple personal homepage, editor to a corporate blog, or a product management tool.
you basically want an UI for inputing and validating some schema-enforced JSON, but that's overwhelming and overkill for most users and more apps, so you script into existence a simplified version of that (aking to "everyone who doesn't learn lisp is cursed to reinvent it" or smth like that but for frontend devs).
Its fixable. We just need to add a new, better designed rich text input element to the web.
The formatting equivalent of... "640k ought to be enough for everybody".
And its not just for "humanity's lowest common denominator". I love being able to copy+paste a table into an email and have it show up correctly. Today's convention where I have to screenshot something to show it to you is horrible.
Markdown isn't the right tool for every job. Would you use markdown to typeset your resume? To write an academic paper?
Lots of popular applications - like Notion or Google Docs - need something more powerful than markdown. And the current javascript APIs are failing them.