407 karma · joined January 2, 2012
</sarcasm>
I'm not a pro product guy, I always choose the right tool for the job, but this stuff enrages me and makes me look at MS as scumbags.
> And suggests that this is better:
It depends in what terms are you thinking. A syntactic improvement is a also a benefit, isn't it?
It is partially my fault because I failed to express what I really ment. English not my native, so sorry.
What I really ment in this sentece is "why using (a lot of) ifs can be a bad practice in a Object Oriented language"
You do make a good point though that in having many small objects is easy to mess with external dependencies. But in my case, the testing always suggested if I had done something like that, and I improved. If an object becomes hard to test in isolation, then something has been done wrong.
Can you provide an example?
The cost of creating a file and moving behaviour there is exactly 0, but the benefits are there from day 1.
I never said that, why all the hate? I stated pretty clear that this is my approach on things, and I never pretended it to be the "right" one.
And you are right, this was not intended to be presented as refactoring pattern, although it qualifies as one, this is how I manage code in my projects from day 1. And I do agree with you that is not always reasonable to do that, but I just feel more benefits rather than penalties doing it from the start.
This can be misinterpreted in many ways.
Also, a big part of falcon patch is the ruby 2.0 garbage collector, which obviously will be available in ruby 2.0.