On Sun, 24 Feb 2019 07:56:27 +0000, Ahem A Rivet's Shot
wrote:
[snip]
> For anything I/O bound I prefer Python, Perl or Java (but not
>'enterprise' Java with all the trimmings and cruft - the language is good
>but the cruft is ... well cruft). Readability, maintainability and speed of
>development are all more important than raw efficiency - most especially
>maintainability. It is no good having code a tenth the size and ten times
>faster if the first time someone less careful works on it dangerous hidden
>bugs appear because handling pointers and raw memory requires care.
I prefer a language that is human-oriented. I would rather have
something run a bit more slowly but be safer. Most of the time, it
does not matter (to me or mine) much anyway. If it does, then I worry
about optimisation.
> It is also worth noticing that just because the language is low
>level and permits high efficiency there's no guarantee of efficient
>programs, all too many programmers start coding and stop designing far too
>soon and wind up using very bad algorithms or optimising the wrong things
>producing twisty masses of C code that once you understand what they're
>supposed to achieve can be replaced by short pieces of clear python that
>*are* ten times smaller and run ten times faster or slightly longer pieces
>of C that are *slightly* faster than the python but harder to maintain.
Exactly. I write something reasonable; it usually is fast
enough. If not, only then I optimise.
Sincerely,
Gene Wirchenko
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | FidoUsenet Gateway (3:770/3)
|