Problems with incorporating markdown into a project

[Lou Quillio]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Gruber wrote:

| I could be wrong, but I don't think PHP Markdown could do
| 5,000-10,000 hits per hour, and if you're using the Perl version,
| you almost certainly couldn't get away with firing up that many
| instances of Markdown via CGI.

Yes, my opinion's confined to PHP Markdown.  Should've said so.

| If I were designing my own CMS, I would definitely store each post
| twice in the database -- raw Markdown for editing, and an XHTML
| version that would more or less be used as a cache.

I'm using Drupal's caching mechanism.  Lacking that, a Slashdotting
~ would get me in (shared) Dutch with TextDrive -- which means Dean
knew what he was doing.  Storing both forms was practical, and not
at all inelegant.  Smart, really.

| I think html2text is excellent, but I'd never use it as part of a
| round trip for CMS editing. You lose all your custom Markdown link
| labels, for example. That's just the nature of the beast, not a
| complaint.

Right.  Works on paper, but too complicated by half.

LQ
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCfv9XWb6NuB4EK7oRAugjAKCBlaF6ul6KzMvTThrU0wwspXs+ewCfRs5/
2sOyB4HHhFpZzl7PxZcoAqk=
=+ssG
-----END PGP SIGNATURE-----