If you feel offended, my apologies, that was not my intention. Your original comments comes across that you were trying to say that certain users should not use markdown. That would contradict the idea to create a standard or “common” mark spec.
I would like conclude my contribution to the discussion with one last remark. After that, I have said all I have to say.
Referring to this wikipedia article
The Unicode standard defines a number of characters that conforming applications should recognize as line terminators:[3]
LF: Line Feed, U+000A
VT: Vertical Tab, U+000B
FF: Form Feed, U+000C
CR: Carriage Return, U+000D
CR+LF: CR (U+000D) followed by LF (U+000A)
NEL: Next Line, U+0085
LS: Line Separator, U+2028
PS: Paragraph Separator, U+2029
This may seem overly complicated compared to an approach such as converting all line terminators to a single character, for example LF. However, Unicode was designed to preserve all information when converting a text file from any existing encoding to Unicode and back. Therefore, Unicode should contain characters included in existing encodings. NEL is included in EBCDIC with code (0x15). NEL is also a control character in the C1 control set.[4] As such, it is defined by ECMA 48,[5] and recognized by encodings compliant with ISO-2022 (which is equivalent to ECMA 35).[6] C1 control set is also compatible with ISO-8859-1 .[citation needed] The approach taken in the Unicode standard allows round-trip transformation to be information-preserving while still enabling applications to recognize all possible types of line terminators.
As we can see here, the way line breaks are handled is already quite complex. It is my belief that adding a backslash or two spaces at the end of a line will not make life easier for future generations.