(Psst.. check out rfeedparser.)

Definitely will! Thanks

->"I assume if there were more people coding Ruby, there would be a better chance someone would step up and take his place."

Is it more the fact that the community is small or that fewer people share their code than in the Python community? Just wondering.

I don't really know Python's community that well, but I would wager it's probably due to sheer size. I disagree with PG's "law of averages" regarding choosing environments - working in a language that has more users does have significant benefits in my opinion.

BTW another example that comes to mind regarding beginner-friendliness is how long it took to get Rails working with Apache. Before Phusion you were supposed to run your own mongrel cluster or similar fringe solutions - it was insane to ignore the world's most widely installed server. Personally I only started considering Rails production-worthy after mod_rails turned out to be fast and stable. Sure, I can run Thin/nginx or whatever, but I don't want to learn a new server (and wait for it to mature) just so I can use Rails.

I, for one, thought that the popularization of the "Fuck Apache" mindset was one the most positive results of Rails' ascendancy.

I don't like Rails, but I hate Apache.

I'm think using Mongrel/LigHTTPD for a while might make you see Apache in a new light :)

I'm not qualified to respond to your points about Phusion and mongrel but on the previous point about the size of the community, are you also finding as a result that the job market for Ruby positions is sparse (forgetting about the economy for a second)? That's the impression I have from the job boards but you work in the field so maybe you have a better idea.

Actually, there's plenty of Rails work out there, and usually in higher rates than PHP (granted, you do accomplish more work per Rails hour).

It seems to me most Rails jobs are either for companies who chose Ruby because they really know their stuff, which is great, or companies who chose Rails because 2 years ago it was touted as some sort of Web app pixie dust in Wired Magazine, which is often less fun :)

I wasn't sure whether the latter firms had found some new pixie dust by now. Good to know. Obie Fernandez has a talk online somewhere about billing where he says something like no one working in Rails should bill less than $150/hour and that he bills himself and his developers at $250 but will occasionally give discounts for various reasons. Maybe I have numbers wrong - just found it - http://www.infoq.com/presentations/fernandez-sales-do-the-hu...

I recommend watching it. Good talk. Takeaway point - always err on the side of charging too much :)

"I mean stuff like having better documentation, for example, online, free, in googleable format"

Do you mean for the core language? Are you not happy with http://www.ruby-doc.org/ ?

I am not happy with them: recently I was looking for the API docs of the standard library for Ruby 1.9, and it turns out it is not available online anywhere. ruby-doc only has the 1.8 stuff. I spent hours trying to figure out how to create my own documentation with rdoc ad ri but eventually gave up. So now I don't even have the documentation of the standard library for Ruby.

Plus you can do a custom Google search like this:

      http://ruby-doc.org/q/<your search string>

Best thing I learned today. Thanks.

My pleasure.

ruby-doc.org is nice, but there's a lot missing in the package level (FeedTools etc). Also, it could use a lot more code examples.

Here again I think it's interesting to compare to PHP's annotated docs ca. 2000, which were a great resource since they usually contained a few common usage examples for every function. The language itself was less consistent and mature than Ruby, but the user contributed (pre-Web 2.0! ;)) docs made up for it.