5 ms·

Personally I hate when editors try and make my markdown look like anything but plain text. Syntax highlighting is fine, but I don't want you to make my font bi

Personally I hate when editors try and make my markdown look like anything but plain text. Syntax highlighting is fine, but I don't want you to make my font bigger when I type # and I don't want my text to be italicized when I type an asterisk, etc. Plain text has a purity and simplicity to it, and if I wanted those features I would probably just use MS Word or Pages or something. I don't personally find the preview to be distracting, and I like seeing the rendered product with a distinct separation from the code that generates it. I don't think I'll swap to this since I'm relatively happy with just having MacOS preview and a terminal in a workspace split, but I could totally see why someone would like this.

anthony_romeo 5y ago
Some places have a healthy mix. GitHub will bold and italicize the text to suggest the rendering of certain blocks, without changing font sizes. Good for reducing the need to swap between edit and preview to verify simple formatting issues as I write. What I truly despise is when markdown blocks are parsed immediately, where the delimiters are instantly removed and the text gets formatted into a terrible WYSIWYG editor. It causes me to constantly swap mental models as I write. It’s the worst of both worlds.
- tombert 5y ago
  The font size thing is the thing that bothers me the most. I can live with how GitHub does it, even if it’s not my favorite. 100% agree on the instant-rendering. That is always the first thing I disable in Slack.