[erlang-questions] Re: No, really, please stop misinterpreting what I wrote

[Raoul Duke]

>> discover is fast.  The authors were disturbed, saying that they'd
>> prefer that Erlang programmers implement things so as to be *clear* in
>> Erlang, so that maintainers of the Erlang interpreter and compiler would
>> know what to target for optimization.
> contexts, on this list and elsewhere. The problem is not
> just that people write 'optimized' code at the expense of clarity.
> They often end up optimizing things that don't matter, and miss
> things, like algorithm optimization that really does.

yup, and it ain't just in Erlang. (as already alluded to re: c.) oh
the humanity of all the wasted effort and cpu cycles. :(