The Anti-If Campaign
antiifcampaign.com
The Anti-If Campaign
1–10 of 27 posts
Re: The Anti-If Campaign
#2Oddly named campaign to promote better use of inheritance. "The Anti-Type Fields Campaign" would be more appropriate and less confusing.
Re: The Anti-If Campaign
#3Don't solve with conditionals that which can be solved by your language's dispatch mechanism.
Re: The Anti-If Campaign
#4[deleted]
Re: The Anti-If Campaign
#5This sort of debate annoys me - not so much because of the potentially fragile design on one side or the perhaps pedantic adherence to OOP principles on the other, but because I know that I could have things like pattern matching and a scarily expressive type system and, well, that'd make a lot of these problems disappear.
Curse you, Haskell, for making me so bitter!
Re: The Anti-If Campaign
#6Oddly named campaign to promote better use of inheritance. "The Anti-Type Fields Campaign" would be more appropriate and less confusing.
Inheritance or polymorphism?
Re: The Anti-If Campaign
#7Re: The Anti-If Campaign
#8Oddly named campaign to promote better use of inheritance. "The Anti-Type Fields Campaign" would be more appropriate and less confusing.
Inheritance or polymorphism?
calambrac gets it right: 'dispatch'. I though the article was going to be about pattern matching, actually. I guess polymorphism is a sort of pattern matching, but the real thing goes farther.
Re: The Anti-If Campaign
#9This is a joke, right? They're making fun of all the programs you see that have 20 different forests of tiny classes spreading the logic of one function across 45 files, right?
Re: The Anti-If Campaign
#10Don't solve with conditionals that which can be solved by your language's dispatch mechanism.
Don't solve with 15 minutes that which you can bill your client 80 hours for.