Quote:
Originally Posted by PeterT
Exactly! (And yes I have used Markdown when coding content for a website a few years back; the site had been coded in a CMS that included markdown as an option for document entry, and when I joined it they were already using markdown.)
|
I would, if it weren't such
a giant pain in the ass to use Markdown. As I've said,
more than once, I use Markdown both in my customer service system (150-300/mails/day) and our production management system (literally, thousands of notifications/week), of TWO different kinds (one uses single paired asterisks for italics, and double-asties for bold, the other uses underscores for italics, and single-pair asterisks for bold, different things for headers, bq's, etc....), and it's very tiring to write/use, in my opinion.
is it fine for a few paragraphs? Yes, albeit annoying. Is it a giant paint in the
tuchus to use for 100K words? ABSOLUTELY. Would I ever write a book in it? NOT IN THIS OR ANY OTHER LIFETIME.
If one is OCD, and needs that level of
visually-reinforced structure, great. I don't. {shrug}. I can create perfectly clean styles in Word, (or RTF and about 10 other formats), output them and get clean content. I don't have to see paragraph tags wrapped around everything. I mean, seriously, folks, think about what you're saying:
if you're going to write in markdown, why not just write the damn HTML in the first place? I'm sure that there's some logical reason for
that distinction, but I don't see it. it's like...baby-step HTML. Mini-ML. Sheesh, why bother?
P.S.: Yes, guys,
I get the humor. You mean well, even if you are completely and utterly wrong.
I'll love ya anyway.
Hitch