Untitled.png
[Hide] (418.4KB, 443x948) >>31389
>You have to add a <br/> if you want a line break without forcing a new paragraph.
Well at least it's possible, even if you literally just have to throw markdown completely out the window and use it's shitty html emulation.
>Its key design goal was readability, that the language be readable as-is, without looking like it has been marked up with tags or formatting instructions
<Even strictly in the realm of things which it was designed to handle, it is way more obtrusive than even html (which isn't even a fucking markup language for TEXT)
<Producing any kind of text document involves using html extensively even though 90% of what gets put into markdown originates in basically a unicode compliant text editor either directly or through a form via a browser
<invented by a wannabe applefag mobile developer (failed) and a copyleft retard who inflicted web.py on us, cofounded reddit, then was arrested for using his own account to rawdog download a database that had already been uploaded into the shadow library system two years ago
Sugoi.
>>31390
Not really, fag
It looks bad and it is bad, both in the really pervasive way that it uniquely identifies you as neither a culturally adapted user nor the 'random expert off the street' who is able to post on bulletin boards and other low friction social media but also just in being a shared identity that paints you as a loser. Sites which use markup are mostly populated by useful posts by people who don't, and the only places which use markdown besides reddit and blogs where nobody formats posts in the first place, are webfrontends where every actual piece of content was written by some cunt who, when he composed it, and when his peers will read it on their end, will be doing so either in a text editor or in the fucking email function of their IDE. Literally the only time markdown ever has a use on any site is to communicate with people who aren't associated with a project or the thread (since anyone who is sees the posts as an email anyway) in the notes for an issue/etc. on a git's web interface. Even end users who aren't associated with the project won't see or use markdown when they write to insulated developers on these sites because they're ultimately still just using the ticket system to send an email.
(You need to go back)