Timeline for Code Smell: Inheritance Abuse
Current License: CC BY-SA 2.5
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 15, 2012 at 19:39 | comment | added | Matthieu M. | @MatrixFrog: I keep forgetting about Haskell's true age, even though I remember photographs of the original team and it looked the 80's had called. It always seems so ahead of its time. | |
| Dec 15, 2012 at 18:24 | comment | added | Tyler | Just for the record, Haskell is 10 years older than C# :) | |
| Dec 15, 2012 at 18:24 | comment | added | Steven Evers | Haskell is a purely functional language (which I am s huge fan of though) and Go doesn't include a number of important elements (yet?). The rest of this is just throwing the baby out with the bath water. | |
| Aug 2, 2012 at 9:14 | comment | added | LCJ | @MatthieuM. I liked your answer. I too think somewhat in your line though I have a different problem programmers.stackexchange.com/questions/159151/… | |
| Nov 10, 2010 at 0:10 | comment | added | mlvljr | [on the original post] How.. DARE YOU??!! Take your words back ;) | |
| Oct 18, 2010 at 19:04 | comment | added | Matthieu M. | @Tim: I don't really like Go :), Modern means recent and Go is certainly newer than C#. Furthermore I would say that C# doesn't break any ground in the world of languages, it's very close to Java for example and thus does feel old :) | |
| Oct 17, 2010 at 17:05 | comment | added | Tim Goodman | "Modern languages" always seems to mean "the languages I like best". C# is a modern language, and it certainly hasn't abandoned inheritance. That said, you make some good points. | |
| Oct 17, 2010 at 10:19 | comment | added | Matthieu M. | @Tim Murphy: I really think that inheritance is a poorly designed mechanism, though it's always easy to say a posteriori. Inheritance violates the "Single Responsability Principle" :) | |
| Oct 17, 2010 at 10:18 | comment | added | Matthieu M. | @dsimcha: actually, it's better if the language does not allow automagic delegation, because forcing the programmer to type somehow forces him to think about whether or not what he's typing is really useful. | |
| Oct 17, 2010 at 4:28 | comment | added | Tim Murphy | "Inheritance is code smell." Wow! Inheritance is good, it is the use of it that can be evil. | |
| Oct 16, 2010 at 20:50 | comment | added | dsimcha | This is reasonable IMHO only if your language allows automagic delegation of everything in a single line of code just like the way inheritance works. If it requires a metric fsckton of boilerplate, then this has to be weighed. | |
| Oct 16, 2010 at 18:24 | history | answered | Matthieu M. | CC BY-SA 2.5 |