I didn't use Posterous because it lacked markdown support. Funny though, that a little over a year ago, "Gary Tan" (company rep) said the company wanted to implement this "soon". http://getsatisfaction.com/posterous/topics/markdown_or_anot... Better late than never, eh?
Posterous adds markdown and syntax highlighting support
21–30 of 37 posts
Re: Posterous adds markdown and syntax highlighting support
#22I'm surprised they went with CodeRay rather than a more fleshed-out highlighting library. They only list 20 or so supported languages, whereas something like Pygments (which Github uses) supports closer to 100.
Truth is, I picked CodeRay for two reasons. It's fast and it's pure ruby. Pygments is great and I spent some time on a version that used it but CodeRay just fits better within our app. It's pure ruby, supports most languages I thought we should start with, it's extensible and has a roadmap for things that I could see our users asking for.
Re: Posterous adds markdown and syntax highlighting support
#23I didn't use Posterous because it lacked markdown support. Funny though, that a little over a year ago, "Gary Tan" (company rep) said the company wanted to implement this "soon". http://getsatisfaction.com/posterous/topics/markdown_or_anot... Better late than never, eh?
Re: Posterous adds markdown and syntax highlighting support
#24Earlier quoted context omitted.
Truth is, I picked CodeRay for two reasons. It's fast and it's pure ruby. Pygments is great and I spent some time on a version that used it but CodeRay just fits better within our app. It's pure ruby, supports most languages I thought we should start with, it's extensible and has a roadmap for things that I could see our users asking for.
From a user's perspective, at least, I would think that language coverage would trump most other things when considering different highlighters.
Re: Posterous adds markdown and syntax highlighting support
#25Re: Posterous adds markdown and syntax highlighting support
#26I'm surprised they went with CodeRay rather than a more fleshed-out highlighting library. They only list 20 or so supported languages, whereas something like Pygments (which Github uses) supports closer to 100.
Truth is, I picked CodeRay for two reasons. It's fast and it's pure ruby. Pygments is great and I spent some time on a version that used it but CodeRay just fits better within our app. It's pure ruby, supports most languages I thought we should start with, it's extensible and has a roadmap for things that I could see our users asking for.
Re: Posterous adds markdown and syntax highlighting support
#27Re: Posterous adds markdown and syntax highlighting support
#28I'm surprised they went with CodeRay rather than a more fleshed-out highlighting library. They only list 20 or so supported languages, whereas something like Pygments (which Github uses) supports closer to 100.
Truth is, I picked CodeRay for two reasons. It's fast and it's pure ruby. Pygments is great and I spent some time on a version that used it but CodeRay just fits better within our app. It's pure ruby, supports most languages I thought we should start with, it's extensible and has a roadmap for things that I could see our users asking for.
Simpler and cleaner that way.
Re: Posterous adds markdown and syntax highlighting support
#29Re: Posterous adds markdown and syntax highlighting support
#30Earlier quoted context omitted.
Truth is, I picked CodeRay for two reasons. It's fast and it's pure ruby. Pygments is great and I spent some time on a version that used it but CodeRay just fits better within our app. It's pure ruby, supports most languages I thought we should start with, it's extensible and has a roadmap for things that I could see our users asking for.
From a user's perspective, at least, I would think that language coverage would trump most other things when considering different highlighters.
You can't ever please him, and he's most likely to say "Pah, this isn't exactly what I want, I'm going to roll my own blog."
(P.S.: the hard bitten product manager in me thinks that, from a user's perspective, the user can't program and this feature means nothing to her either way, and every second spent thinking about it is a second the business never gets back.)