Verbosity Difference
2009-08-19 17:25:50.883102+02 by
Dan Lyke
1 comments
The Verbosity Difference, on OOP and programming language verbosity:
The problem is that the marginal cost of adding a new class is greater than the marginal cost of extending an existing class. If it was easier to make a new class, we would have done so. But we would also have made a new class if it was harder to add methods to an existing class, because then the trade-off would have been different. In other words, what matters is the difference in verbosity between the “right way” and the “wrong way”, not the absolute level of verbosity.
[ related topics:
Software Engineering
]
comments in ascending chronological order (reverse):
#Comment Re: made: 2009-08-20 06:56:49.953934+02 by:
spc476
It could also depend upon coding conventions. I have a friend who's coding style mandates a huge, 20+ comment block for every function, regardless of how trivial a function (which includes a hand-maintained change log per function). So inadvertently he's created an environment where it's easier to add functionality to an unrelated function than to create a new function.
But it's the way he's always done it, and it's the way he'll always do it.
We will not edit your comments. However, we may delete your
comments, or cause them to be hidden behind another link, if we feel
they detract from the conversation. Commercial plugs are fine,
if they are relevant to the conversation, and if you don't
try to pretend to be a consumer. Annoying endorsements will be deleted
if you're lucky, if you're not a whole bunch of people smarter and
more articulate than you will ridicule you, and we will leave
such ridicule in place.