News for hackers. Stuff that matters.
Re:What's better about Ruby than Python? - comp.lang.python by rjurney on Thursday August 26, 2010 @07:07PM (#1637438)
The fact that anyone at any point can monkey patch any built-in is a potential liability for large teams, with average programmers. It must be addressed by culture and code review that you may or may not have.

Still worth it though :)

Re:What's better about Ruby than Python? - comp.lang.python by jshen on Thursday August 26, 2010 @07:45PM (#1637538)
I've never bought the idea that the opposite is a better trade off because it comes with costs too. Have you ever worked with a bunch of mediocre java programers? Heaven forbid they make an interface that isn't well thought out and needs to be changed later!
Re:What's better about Ruby than Python? - comp.lang.python by rjurney on Thursday August 26, 2010 @07:54PM (#1637563)
That extreme is also terrible. Python is somewhere in between.
Re:What's better about Ruby than Python? - comp.lang.python by jshen on Friday August 27, 2010 @12:04AM (#1637963)
if ruby is an extreme to the left, and java an extreme to the right, then python is also extreme to the left. The difference between python and ruby in dynamicity is really small.

Python is not in the middle of ruby and java. Python is virtually on top of ruby.

Re:What's better about Ruby than Python? - comp.lang.python by andybak on Friday August 27, 2010 @06:16AM (#1638412)
A fair point. Maybe 'optimum' would be a more useful concept here than 'centre'... I see Python's position on the dynamicity (ugh) spectrum is in line with it's philosophy on readability.

(On a side note - your definition of 'extreme' rather depends on what outliers you have. I do love it when the US media refers to the Democrats as 'left of center' ;)

Re:What's better about Ruby than Python? - comp.lang.python by jshen on Friday August 27, 2010 @10:52AM (#1638971)
yup, republican and java are in the same camp ;)

On a serious note, I've been doing ruby as my job for about 5 years and I work at a giant corporation with a few hundred programmers. In those 5 years I've never been bitten by someone changing a core class that breaks my code. Maybe 3 times I've been bitten by someone changing a non core class, and it usually takes me about an hour or two to resolve it.

So that's maybe 6 hours in 5 years where I've lost time due to this, but the amount of time it has saved me is far larger than this.

Re:What's better about Ruby than Python? - comp.lang.python by andybak on Friday August 27, 2010 @04:11PM (#1640084)
That sounds like an interesting big Ruby gig that would be a good story to tell the anti-dynamic languages FUD brigade.

You should blog :)

Re:What's better about Ruby than Python? - comp.lang.python by derefr on Thursday August 26, 2010 @11:30PM (#1637926)
In what situation is it actually a good idea to employ a large number of bad programmers, rather than a small number of good ones? We shouldn't be making trade-offs for the sake of bad ideas ;)
Re:What's better about Ruby than Python? - comp.lang.python by acdha on Friday August 27, 2010 @09:52AM (#1638800)
There's a distinction to be made between preventing risky behaviour and relying only on a programmer's good judgement to avoid mistakes. Even if your team is solely good programmers there's a lot to be said for discouraging unsafe behaviour by default since anyone can have a bad day, distraction, etc.

I view this situation as somewhat analogous to having guards on power tools: even a highly skilled operator doesn't want to rely on always doing something perfectly.

Re:What's better about Ruby than Python? - comp.lang.python by derefr on Friday August 27, 2010 @06:00PM (#1640433)
The nice thing about code is that (when version controlled) all mistakes can be fixed retroactively. As long as two programmers aren't having a bad day at once, pairing will catch "all" errors. As long as all your programmers aren't having a bad day at once, code review will catch "all" errors again. ;)
Re:What's better about Ruby than Python? - comp.lang.python by wariola on Friday August 27, 2010 @06:56PM (#1640572)
This is why you need to automate peer review http://www.parasoft.com
Re:What's better about Ruby than Python? - comp.lang.python by techiferous on Friday August 27, 2010 @12:55AM (#1638036)
...and all it takes is one rogue or bad programmer to mess up the code base.
Re:What's better about Ruby than Python? - comp.lang.python by derefr on Friday August 27, 2010 @04:45AM (#1638300)
...in either scenario. During code review, however, I'd expect that the good programmers would reach much more strongly to the rogue commits than the mediocre programmers would.
Re:What's better about Ruby than Python? - comp.lang.python by wmoxam on Thursday August 26, 2010 @09:19PM (#1637734)
Are there many ruby app built by large teams?

In my experience, teams building Ruby apps tend to be much smaller than teams building Java apps ..

That said, this is a problem for any libraries that you might want to include, you have to trust that the authors followed conventions and didn't do any thing 'evil'. Ruby Rewrite (http://rewrite.rubyforge.org/) was conceived to specifically avoid this sort of problem.

Re:What's better about Ruby than Python? - comp.lang.python by sunkencity on Friday August 27, 2010 @03:17AM (#1638208)
The best software is built by small teams.