2 ms·
I never really understood the point of these simplified markup languages. I see Markdown and ReST being pushed on non-technical writers who just don't want to u
by ams6110 11y ago
I never really understood the point of these simplified markup languages. I see Markdown and ReST being pushed on non-technical writers who just don't want to use a text-based markup language. They want Word, or Google Docs, or a rich edit box, or something like that.
As for me, yeah I like writing in plain text but given the choice I'd rather just write in HTML which I already know, rather than use something like Markdown. I don't find Markdown to be particularly time-saving or easier to use. Or if I'm writing something where I particularly care about beautiful typesetting or I need a table of contents and an index I'll use LaTeX which has been developed for decades specifically for scholarly and technical writing.
- agumonkey 11y agoThese users want familiarity, and get false simplicity / silo-lock-in. I'm not fond of giving emacs to everyone anymore, but even the simple fact of showing that simple text can be transformed into formatted beauty can open their mind. Otherwise, IMO, they don't understand they have a computer wanting to compute for them, they see a weird typewriter simulator that they should appease as much as possible otherwise that god might crash taking their hard (because the software is obscure) work down the drain. Now I also find markdown good enough. Headers, paragraphs, lists, quotes, links... Gruber's page list 10 kinds, easy to remember for anyone; balanced, minimal and generic document feature set.
- dredmorbius 11y agoMarkdown and other LWMLs are just that: lightweight. I've used over the years nroff, HTML, Wordstar and Wordperfect (which aren't _quite_ markup languages, though with their "reveal codes" modes they're close), HTML, DocBook, and LaTeX. Probably a few others. Oh: Twiki, MediaWiki and some other site-specific formatting languages. Generally in vim (which I'm using here and now for what it's worth). For much of the period from 1999 onward, basically, if I wanted to write anything vaguely structure, I went straight to HTML. It's not _too_ bad, and you can generally patch up any holes with tools like tidy (though it doesn't speak HTML5...). LaTeX (which I only really got down a year or two back) turned out to be a lot lighter than I'd anticipated, and is pretty good, overall. I actually recommend it pretty strongly, and may well either start or more frequently finish longer-form docs using it. If you're producing publication-quality work, it's really got a ton of win to it. The fundamental problem with HTML in my book is that it simply has too much presentation mixed up in it. It's possible to use it generically, but you've got to think about it somewhat. Markdown's not perfect, but in terms of creating a main content block you can drop into a lot of other forms, it's got strong arguments. Despite years of HTML, and, really, a lot of familiarity with it, Markdown beats it, if only because one of the most1fundamental text units, the paragraph, requires no additional formatting. (That's a principle strength of LaTeX as well.) It _also_ greatly simplifies both unordered and ordered list construction. Blockquotes and code blocks are trivial. Dittoes headers. Bold and italic text are easy, though you lose semantic distinctions as I noted above. Links are roughly equivalent. Tables -- not great, but certainly no worse than HTML. And so long as you're authoring offline, if you want HTML you've got it -- Markdown's effectively extensible. As a fundamental authoring tool: really good. Of course, if you prefer not using it, nobody's holding a gun to your head.