Ruby Is The Future

Post by ansin » Thu, Apr 02, 2009, 3:56 AM UTC

nir wrote: post #51

ansin wrote: post #23

Earlier quoted context omitted.

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 :)

Post by Tichy » Thu, Apr 02, 2009, 6:01 AM UTC

ansin wrote: post #26

nir wrote: post #18

Earlier quoted context omitted.

I love Ruby. I love that code can be so short and yet easily readable. It might be slower and perhaps more memory-hungry than other languages, but for my needs that's usually not an issue. What I do miss are good, well documented , stable libraries. For example, I currently process RSS/Atom feeds with FeedTools, whose own creator says he's tired of maintaining (I totally understand him and am extremely thankful for t…

"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/ ?

Post by jshen » Thu, Apr 02, 2009, 4:10 PM UTC

ansin wrote: post #25

jshen wrote: post #8

Earlier quoted context omitted.

dealing with the type system in scala can be a pain and is a hit to productivity in the early stages. The question is if the hit in the early stages leads to more productivity in the later stages. I'm not convinced that it does. I've done a lot of ruby, and I've had monkey patching bite me a few times. However, fixing the problem was never that hard (two days max) and is clearly overshadowed by the productivity gaine…

You're lucky that in those cases you were able to recover in only two days. The time it takes to get back on track can be proportional to the size of the project so imagine if you were dealing with an enterprise system written in and monkey patched in Ruby and you had a similar problem. Depending on your luck, you might get back on track or you might end up having a lot of extra time to work on your resume.