Sujet : Re: Baby X is bor nagain
De : already5chosen (at) *nospam* yahoo.com (Michael S)
Groupes : comp.lang.cDate : 17. Jun 2024, 10:25:27
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <20240617122527.0000559d@yahoo.com>
References : 1 2 3 4 5 6 7 8 9 10 11 12
User-Agent : Claws Mail 3.19.1 (GTK+ 2.24.33; x86_64-w64-mingw32)
On Mon, 17 Jun 2024 07:30:44 -0000 (UTC)
Kaz Kylheku <
643-408-1753@kylheku.com> wrote:
On 2024-06-17, James Kuyper <jameskuyper@alumni.caltech.edu> wrote:
The problem is that Bart's compiler is VERY unusual. It's
customized for his use, and he has lots of quirks in the way he
thinks compilers should work, which are very different from those
of most other programmers. In particular, compilation speed is very
important to him, while execution speed is almost completely
unimportant, which is pretty much the opposite of the way most
programmers prioritize those things.
Most programmers use Javascript and Python, which follow Bart's
priorities. Fast, invisible compilation to some kind of byte code
(plus possibly later JIT), slow execution time.
I'd dare to say that most programmers care about speed of compilation
more than they care about speed of execution even (or especially) when
they use "visible" compilation processes. Except when compilation is
already very fast.
BTW, my impression was that Bart's 'C' compiler uses 'visible'
compilation.
Then again, neither speed of compilation nor speed of execution are top
priorities for most pros. My guess is that #1 priority is conformance
with co-workers/employer, #2 is convenient IDE, preferably integrated
with debugger, #3 is support, but there is big distance between #2, and
#3. #4 are religious issues of various forms. Speed of compilation is at
best #5.