Conversation

Okay, I have a bunch of things to say/rant on this.

Quote Tweet

Maggie

visting SFO

@Mappletons

· Apr 23

Replying to @thunknotes

Expect you've already read it, but dropping the ref for others. @kmelve wrote up a good piece on markdown earlier this year: smashingmagazine.com/2022/02/though

Appreciate your thoughts on this. Interop is obviously one of the strongest arguments for markdown. Have you considered it from the perspective of a non-dev / non-technical user? Who has no idea what markdown is and just wants to create rich, visual docs without strange syntax?

Eg. The “I am an editor of text, and I find it friendly” is from the perspective of someone very comfortable in code and syntax. For many people WYSIWYG interfaces with rich options for formatting and data types (tables, video, etc) w/o any html tags or syntax is friendlier.

Taylor Hadden

@Cptn_ChillPill

Apr 23

100%, I am the exception. It’s just that the things that make it easier for non technical people make it more annoying, more fricious for me.

Replying to

Agreed. Definitely creates more headaches and complexity for devs. We’re still in the messy phase where the DX is kinda crap and we don’t have good shared formats yet. Hoping that improves in the coming years

9:33 PM · Apr 23, 2022Twitter for iPhone

Replying to

I was speaking less as a dev and more as a writer in this instance, actually. I prefer the experience of writing in markdown (especially with span level elements).

Taylor Hadden

@Cptn_ChillPill

Apr 23

It doesn’t help that I take lots of notes _about_ code and most WYSIWYG text editors are _very bad_ at quickly starting and working with inline and block level code compared to markdown.

Show replies