From: John Gabriele Date: 2006-05-12T06:03:50+09:00 Subject: Re: Sharp knives and glue On 5/11/06, rob wrote: > Re-opening classes is one of the things that makes ruby great. [snip] > > Why so precious? If you don't want people to modify your code say so. > If they go ahead and it blows up it's their fault. Not to take any sides, but I think I've heard the argument go: if you're working on a team on a large project, and all of a sudden "your" class breaks, management doesn't want to hear about someone else opening your class... they'll just see your name on the class causing the hold-up and then it *becomes* your problem. In the typical "enterprise scale" cubicle farm environment, team leaders are constantly looking to find someone to blame for the project being behind. B&D languages like Java lend themselves to rigid compartmentalization that yields paper trails. It's interesting to think about the dynamic there -- between the language and the cube farm.