News for hackers. Stuff that matters.

A comment on GitHub satanically messing with Markdown – changes 666 to DCLXVI. Parent comment

Re:GitHub satanically messing with Markdown – changes 666 to... by contravariant on Tuesday November 26, 2019 @07:06AM (#21637549)
>It was much easier to write parsers for though. Most of the BBCode tags could be rendered with simple regex substitutions.

Nevermind. Let's not bring BBCode back.

[ Parent | on HN ]
Re:GitHub satanically messing with Markdown – changes 666 to... by laumars on Tuesday November 26, 2019 @08:56AM (#21638253)
On the whole I'd agree. When markdown is done right it's pretty awesome. However I'd still take BBcode over buggy half implemented markdown parsers like the one we have on HN. At least [i] is a less common token than * -- which leads to no end of edits when I've absent-mindedly emphasised something that should have been bullet pointed.

...but yes, I do agree that markdown is definitely better when it's done right.

[ Parent | on HN ]
Re:GitHub satanically messing with Markdown – changes 666 to... by CarlRJ on Tuesday November 26, 2019 @11:28AM (#21639734)
On second thought, let us not go to Camelot. It is a silly place.
[ Parent | on HN ]