Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Interfaces are an inherently weaker form of the age old Operation Code and data packet paradigm.

Only if the language in question doesn't allow something like `interface MyNewInterface extends MyOldInterface { ... }`.

I'm not too clued up on state-of-the-art for OO languages, but my understanding is that this is a practical approach in the mainstream languages that support OO.

For your [0] link, I'm familiar with those arguments, but I believe that this is very subjective. For example, in a modern context, I'd probably use interfaces, which makes all those arguments, except for the state argument, moot.

For the [1] link, I've not read that before but it is a very long interview and I am in disagreement with the general thrust that the argument is "generic programming" vs "OO patterns". If all the facts were forced into that argument, then sure, there might be a point to the criticism, but the fact is that it is possible and simple to use both at the same time.

IOW, they are not in competition with each other, so presenting one as superior to the other is pointless.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: