3 ms·

My theory is that programmers choose to use languages like Python and Ruby for their personal projects, despite their weaknesses, because these languages are mo

My theory is that programmers choose to use languages like Python and Ruby for their personal projects, despite their weaknesses, because these languages are more fun to program in. There's something about this thinking that gets me on the defensive. I think it's that so many people seem to unquestionly accept that C# and Java are for real work, but that Ruby and Python are somehow lesser languages. I work in the IT dept of a small but conservative company, in a large but conservative field. A few years ago, before I came onboard, they made the decision to phase out Java for Ruby, and now almost all work is Ruby. We've also migrated development environments from Windows to Linux. I'd consider myself a professional programmer, but this is my first job in a Ruby shop, and I have to say I am still staggered by the productivity. We do things with our small team that would never be considered amongst larger teams I've worked for. Strange thing is, we don't fit any of the Ruby/Rails stereotypes at all; average age of the devs would be mid-30s and we all have kids. Oh, and only one of us owns a Mac.

patio11 17y ago
I work in Java on the weekdays and Rails on the weekends. I do not find that Ruby is a weakness to me. Indeed, after several years as a professional Big Freaking Enterprise App Java developer, I would break out in a cold sweat if told to code up an A/B testing framework in it by my boss. I'd quote him two months. It took me a week in Rails, working after I got home (generally past midnight). Don't get me wrong, I like Java. I cut my teeth on programming Java. It put a roof over my head and food on the table. I support almost two thousand customers of a Java Swing app. But yikes, for the typical greenfield web application with flexibility to choose platforms, there are so many better choices.

patio11 17y ago

I work in Java on the weekdays and Rails on the weekends. I do not find that Ruby is a weakness to me. Indeed, after several years as a professional Big Freaking Enterprise App Java developer, I would break out in a cold sweat if told to code up an A/B testing framework in it by my boss. I'd quote him two months. It took me a week in Rails, working after I got home (generally past midnight). Don't get me wrong, I like Java. I cut my teeth on programming Java. It put a roof over my head and food on the table. I support almost two thousand customers of a Java Swing app. But yikes, for the typical greenfield web application with flexibility to choose platforms, there are so many better choices.