Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

"You're confused. Rubyists didn't sink your project. Bad programming (and management) did. They would have fucked up the project in Java or Haskell or Perl or anything else."

I'm not confused at all. Rubyists sunk the project, plain and simple. I actually still like Ruby, because I had a chance to do some cool stuff with it before our inferior rubyists wrought their havoc, and I agree that had we had decent management, they'd have been fired.

My only criticism of Ruby is that because it's easy, it allows vastly inferior programmers to program, which lowers the bar drastically. I believe that a number of the other senior developers there won't touch ruby at all now, I'm not one of those.

However, given one of the jobs I received e-mail about, I'd say that the salaries that rubyists can get puts them in the worst of both worlds -- it attracts people who want to be cool, and people who want high-paying jobs. Plus, it's easy to learn badly, which sets the bar very low.



My only criticism of Ruby is that because it's easy, it allows vastly inferior programmers to program, which lowers the bar drastically. I believe that a number of the other senior developers there won't touch ruby at all now, I'm not one of those.

Wrong. Every language allows this. Have you ever read enterprise Java or C++ code?


Actually it's entirely true. Ruby allows VASTLY inferior programmers to program. Java and C++ set slightly higher bars; at least with them you have to reach inferior, as opposed to vastly inferior, in order to make stuff work.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: