6 ms·
At a certain point, isn't it easier to just write the HTML?
by pavel_lishin 15y ago
At a certain point, isn't it easier to just write the HTML?
- jseliger 15y agoActually, this is related to a question I've thought about but never asked: if you're, say, writing a blog, why use Markdown over standard HTML? Does it give some advantage I'm not aware of?
- technoweenie 15y agoYou can write content faster if you're comfortable with the syntax. It also has the advantage of looking good unstyled and styled. The syntax tends to look like a styled plaintext email.
- lysol 15y agoAgreed. It gracefully degrades into something readable if parsing fails, which is not applicable to HTML.
- michaelschade 15y agoThis. I use Markdown syntax when writing blog posts since Posterous formats Markdown just fine and it lets me view my writing (mostly) unstyled in vim, which I personally find much more comfortable than some web-based editor.
- bergie 15y agoI do the same, though I guess this is more the fault of current web-based editors than of HTML itself. I'm trying to explore some ideas of simplicity in browser-based HTML editing with Hallo (http://bergie.github.com/hallo/ http://bergie.github.com/hallo/), but remains to be seen how well that works out. In the meanwhile there is always Markdown. And Vim.
- 6ren 15y agoIt's striking to me that markdown has become so popular, when wysiwyg HTML editors have been around for a long time, and are supposed to be easier to use (I would expect them to be). Perhaps it's partly that using asterisks for emphasis makes more intuitive sense than ^I or clicking a button etc; and partly that mostly people don't use it - let alone the more complex markdown features.
- bergie 15y agoI think it would make a lot of sense for WYSIWYG editors to support Markdown-like microsyntax for simple formatting: https://github.com/bergie/hallo/issues/11 https://github.com/bergie/hallo/issues/11 This way you start writing _something, and it becomes something
- michaelschade 15y agoIt's not that the WYSIWYG editors aren't easy to use in most senses–they're not difficult at all. However, many people that use Markdown are probably geeky enough to not need some WYSIWYG editor in the first place. For me, I'm in the terminal and MacVim for a good portion of my day hacking around; so, while I enjoy portions of the Google Docs(or whatever editor) interface, if I stop my usual coding activities to write a blog post, I'd like to stay in my natural environment of vim and terminal. This is particularly true if my blog post contains code–it feels much more natural for me to paste code samples between vim windows than it does to copy code from vim and paste it into some external editor. (So, basically, it's not just the syntax, it's also the environment in which I get to write that syntax.)
- macrael 15y agoThe biggest advantage for Markdown is that it is in plain text. It looks good in plain text. This makes it incredibly portable, lets me write it in whatever text editor I have at hand (even ssh'd into another machine (though I don't do that very often, everything I write is just in dropbox)). I prefer having my writing sitting on my machine in straight forward plain text formats rather than in HTML. It is so much easier to deal with this way, and it is a one step process to convert it to HTML when I want to post it online. Plus, if I want to convert it to some other format, it would be trivial to do so.
- ceejayoz 15y agoParticularly useful for HTML e-mail - write once and it'll look great in both the plaintext version and the HTML one.
- s1rech 15y agoFor blog posts, README's for github and stuff like that the source in markdown kind of looks better than the equivalent HTML tag soup. In fact, I wouldn't mind if javadoc supported it too.
- bergie 15y agoDocco does: http://jashkenas.github.com/docco/ http://jashkenas.github.com/docco/
- cormullion 15y agoIt's a writer's tool, rather than a coder's tool. Markdown text is getting on for half as long as equivalent HTML. # Subheading ## Main heading Plain paragraph. - bullet - bullet - bullet Paragraph. 87 characters in Markdown. 147 in HTML. If I write in HTML, I get distracted from the words by the HTML markup...
- jseliger 15y agoAh. Interesting. I use macros in Textmate and Typinator to accomplish more or less the same thing; for example, command-shift-v will enter "<a href=command-v">, with command-v being paste, and command-i will yield italics, and so forth. Still, having something universal, like Markdown, sounds attractive.
- FSX 15y agoImagine having to write a few lists or tables in HTML. I think writing Markdown in those cases is a bit faster and much more pleasant.
- remi 15y agoHaml is also great for writing <table>'s.
- baddox 15y agoMarkdown is for publishing, whereas Haml is for designers/developers. The point of Markdown is that non-technical users can use it, and it generally looks good and self-explanatory even unrendered.
- pavel_lishin 15y agoAssuming http://www.leancrew.com/all-this/2008/08/tables-for-markdown-and-textmate/ http://www.leancrew.com/all-this/2008/08/tables-for-markdown... is accurate, HTML tables look much more readable to me. /shrug
- dchest 15y agoSince it's allowed in HTML to not close <li> tags, lists are pretty readable and easy to write: <ul> <li>Item 1 <li>Item 2 <li>Item 3 </ul>
- arkitaip 15y agoThis. I find markdown and all its bastards insufficient and their syntax hard to remember. Sometimes you can use _ other times it's * and none of them are more intuitive that <em> or <bold>.
- veeti 15y agoActually, it's <strong> and not <bold> ;)
- deleted 15y ago[deleted]
- deleted 15y ago[deleted]
- arkitaip 15y agoCan't believe I made that mistake ;)
- jgroome 15y ago<strong>. (Sorry)
- deleted 15y ago[deleted]
- deleted 15y ago[deleted]
- kbd 15y agoI've always wished _ meant "underline" not <em>. Of course the HTML standard only defines <em> and <strong>, but _ could create output like <em class="underline"> or <em style="text-decoration: underline">.
- mooism2 15y ago<u>
- tanoku 15y agoHTML may be easier for you (it certainly is for me), but that's because you are a programmer. You must keep in mind that Markdown targets a very wide audience: you cannot expect your average Reddit user to write emphasis tags every time he wants to say something sarcastic in a comment, and trust me, that's pretty often. Likewise, you cannot expect the average Joe to remember the syntax of an HTML link tag when writing a comment in your website, but you do need (at least we do) to make sure that the links in your website have certain attributes (rel, target, etc): Hence, customizable Markdown.
- hnbla 15y agoFor me the problem if i write html is that i write it different all the time. In one place i might use <b> while i the next time use <strong> or maybe even go as far as <p style="font-weight:bold;">. Forgot to change paragraph with a </p><p>? Just add a <br /> instead! With markdown there is only ONE way to do things right and there's not many thing you can do (wrong) actually. With html it's too easy to go overboard and either mess things up or start being creative with individual styles all over.
- jcoder 15y agoThen you're restricted to HTML. You can parse Markdown and emit LaTeX, HTML, OPML—anything structured.