5 ms·
"It’s harder to reason out program flow. " -- I think this is the key cons which might lead us into nightmare.
by xumingmingv 9y ago
"It’s harder to reason out program flow. "
-- I think this is the key cons which might lead us into nightmare.
- dep_b 9y agoIf you think it’s necessary you can still explicitly list receivers on the message handler instead of using a list of objects that implement a certain interface. It makes code a bit more kludgey though.
- mikekchar 9y agoFor me the interesting thing is that the very lack of coupling seems like a problem to me. If A depends on B, I'd actually like B to be coupled to A. Back in the old days when I believed "generic components" were a cool idea, I'd always run into that problem. It's too general and so it has not structure. And then it is actually implicitly coupled (even if it has a network system and a communications protocol in the middle) -- it's just that you've abstracted away the interfaces with a bunch of adaptors. It's like having a plug on your electronic device that can fit any socket, but only one of the many sockets actually works. I imagine the author has techniques for dealing with that kind of problem, but has unfortunately not shared them. Maybe another time.