Встретилосьв ерланговой рассылке.

> And as Joe Armstrong has pointed out, performance considerations comes
> after correctness *and* maintainability, except for known performance
> bottlenecks where it pays to make a compromise.
>

Yes — try the following:

Repeat 10 times before meals, and before going to bed.

» I must program as inefficiently and beautifully as possible»

If the symptoms persist and you feel the need to program efficiently take a cold shower and a brisk bracing walk.

Your job is to write beautiful and clear code.

It is the compiler writers job to turn clear and beautiful code in quickly executing code.

It is the language designers job to design languages that will make it difficult for you to shoot yourself in the foot.

If you write clear code and you think it should run quickly and it does not do not optimise the code — tell the compiler writer to fix the compiler/run-time.

We will get 1000+ core machines within a few years — they are so bloody fast that we are having problems thinking of what we can use the CPU cycles for so
please don’t write efficient programs — otherwise we won’t need the 1K core machines

:-)

Originally published at U.F.M's Homepage. You can comment here or there.