Re: fledgling assembler programmer

George Neuner <gneuner2@comcast.net>
Sat, 25 Mar 2023 20:54:26 -0400

          From comp.compilers

Related articles
[5 earlier articles]
Re: fledgling assembler programmer gneuner2@comcast.net (George Neuner) (2023-03-22)
Re: fledgling assembler programmer gah4@u.washington.edu (gah4) (2023-03-22)
Re: fledgling assembler programmer tkoenig@netcologne.de (Thomas Koenig) (2023-03-23)
Re: fledgling assembler programmer arnold@skeeve.com (2023-03-23)
Re: fledgling assembler programmer gah4@u.washington.edu (gah4) (2023-03-24)
Re: fledgling assembler programmer DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2023-03-25)
Re: fledgling assembler programmer gneuner2@comcast.net (George Neuner) (2023-03-25)
Portable Software (was: fledgling assembler programmer) DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2023-03-28)
Re: Portable Software (was: fledgling assembler programmer) arnold@freefriends.org (2023-03-28)
Re: Portable Software (was: fledgling assembler programmer) gah4@u.washington.edu (gah4) (2023-03-28)
Re: Portable Software (was: fledgling assembler programmer) gneuner2@comcast.net (George Neuner) (2023-03-28)
Re: Portable python Software (was: fledgling assembler programmer) gneuner2@comcast.net (George Neuner) (2023-03-29)
Re: Portable Software (was: fledgling assembler programmer) gah4@u.washington.edu (gah4) (2023-03-29)
[11 later articles]
| List of all articles for this month |
From: George Neuner <gneuner2@comcast.net>
Newsgroups: comp.compilers
Date: Sat, 25 Mar 2023 20:54:26 -0400
Organization: A noiseless patient Spider
References: 23-03-001 23-03-002 23-03-003 23-03-007 23-03-008 23-03-012 23-03-017
Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="33069"; mail-complaints-to="abuse@iecc.com"
Keywords: code, interpreter
Posted-Date: 26 Mar 2023 05:15:30 EDT

On Sat, 25 Mar 2023 13:07:57 +0100, Hans-Peter Diettrich
<DrDiettrich1@netscape.net> wrote:


>After a look at "open software" I was astonished by the number of
>languages and steps involved in writing portable C code. Also updates of
>popular programs (Firefox...) are delayed by months on some platforms,
>IMO due to missing manpower on the target systems for checks and the
>adaptation of "configure". Now I understand why many people prefer
>interpreted languages (Java, JavaScript, Python, .NET...) for a
>simplification of their software products and spreading.




Actually Python is the /only/ one of those that normally is
interpreted. And the interpreter is so slow the language would be
unusable were it not for the fact that all of its standard library
functions and most of its useful extensions are written in C.


In practice Java and Javascript almost always are JIT compiled to
native code rather than interpreted. There also exist offline (AOT)
compilers for both.


Many JIT runtimes do let you choose to have programs interpreted
rather than compiled, but running interpreted reduces performance so
much that it is rarely done unless memory is very tight.




.NET is not a language itself but rather a runtime system like the
Jave Platform. .NET consists of a virtual machine: the Common
Language Runtime (CLR); and a set of standard libraries. Similarly
the Java Platform consists of a virtual machine: the Java Virtual
Machine (JVM); and a set of standard libraries. Compilers target
these runtime systems.


The .NET CLR does not include an interpreter ... I'm not aware that
there even is one for .NET. There is an offline (AOT) compiler that
can be used instead of the JIT.






>What's the actual ranking of programming languages? A JetBrains study
>does not list any compiled language in their first 7 ranks in 2022. C++
>follows on rank 8.
>
>What does that trend mean to a compiler group? Interpreted languages
>still need a front-end (parser) and back-end (interpreter), but don't
>these tasks differ between languages compiled to hardware or interpretation?


The trend is toward "managed" environments which offer niceties like
GC, objects with automagic serialized access, etc., all to help
protect average programmers from themselves ... err, um, from being
unable to produce working software.




>DoDi
George



Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.