31–37 of 37 posts
I was looking through the user preferences yesterday to see if they had added this option but couldn't see anything. I was on the verge of moving my blogs to Posterous when the affiliate link thing came to light. I can't see myself going back to the service until I can opt out of that.
Earlier 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.
Why not just slap in the google code highlighter javascript, if the page contains code. http://code.google.com/p/syntaxhighlighter/ Simpler and cleaner that way.
I'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.
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 was in my YC batch and the first thing I suggested to them was reST support. They've obviously had bigger fish to fry. Meanwhile, instead of taking an hour to implement a simple script to process markdown files into HTML and send them to Posterous, you've chosen to complain that a super-niche feature was actually released.
Earlier quoted context omitted.
Posterous was in my YC batch and the first thing I suggested to them was reST support. They've obviously had bigger fish to fry. Meanwhile, instead of taking an hour to implement a simple script to process markdown files into HTML and send them to Posterous, you've chosen to complain that a super-niche feature was actually released.
There is no reST library for ruby that I could find.
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 was in my YC batch and the first thing I suggested to them was reST support. They've obviously had bigger fish to fry. Meanwhile, instead of taking an hour to implement a simple script to process markdown files into HTML and send them to Posterous, you've chosen to complain that a super-niche feature was actually released.
The point is not about complaining, its that the company said a year ago that they would push it soon