GitHub satanically messing with Markdown – changes 666 to DCLXVI

Re:GitHub satanically messing with Markdown – changes 666 to... by enriquto on Tuesday November 26, 2019 @04:27AM (#21636735)

that's what plain html is for! I don't really see the point of markdown. With modern html5 you do not even need to close most tags.

[ Parent | on HN ]

Re:GitHub satanically messing with Markdown – changes 666 to... by irrational on Tuesday November 26, 2019 @09:54AM (#21638722)

I don't know. Even though I know HTML, I'd much rather create a bullet list by putting an asterisk in front of each item than writing a bunch of <ul><li> tags.

[ Parent | on HN ]

Re:GitHub satanically messing with Markdown – changes 666 to... by JadeNB on Tuesday November 26, 2019 @10:08AM (#21638862)

> I don't know. Even though I know HTML, I'd much rather create a bullet list by putting an asterisk in front of each item than writing a bunch of <ul><li> tags.

But I wouldn't—and it's a lot easier for you to process your Markdown and paste it into an HTML-enabled text field than it is for me to process my HTML and paste it into a text field that understands only one of the flavours of Markdown that doesn't have sufficient escape hatches built in (or that, like most flavours, has lots of features built in that you're apparently supposed to discover only by experimentation, preferably without any sandbox or preview available).

[ Parent | on HN ]

Re:GitHub satanically messing with Markdown – changes 666 to... by feanaro on Tuesday November 26, 2019 @08:40AM (#21638137)

IMO, plain HTML is much more confusing and quite a bit less legible.

[ Parent | on HN ]