Sujet : Re: Command Languages Versus Programming Languages
De : janis_papanagnou+ng (at) *nospam* hotmail.com (Janis Papanagnou)
Groupes : comp.unix.programmerDate : 13. Oct 2024, 13:29:00
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vegeee$m5s7$1@dont-email.me>
References : 1 2 3 4 5 6
User-Agent : Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
[ X-post list reduced ]
On 13.10.2024 10:18,
Muttley@DastartdlyHQ.org wrote:
[...]
I disagree. Modern linux reminds me a lot of SunOS and HP-UX from back in
the day. Not something that can be said for MacOS with its role-our-own
Apple specific way of doing pretty much everything.
I've never programmed on Mac OS X (if the discussion is about that)
but since its kernel is based on a BSD system it doesn't seem to be
different from other Unixes; as far as the subtopic "interpreter vs.
compiler" goes. (Ignoring other technical implementation details of
Unix.)
Myself I programmed on UTS, SunOS, AIX, HP-UX, and Linux, each with
its quirks, specialities and commonalities, some based on SysV, some
on BSD, and some used concepts from both. Linux reminds me more on
systems borrowing from both worlds (plus some more newer concepts).
Concerning the subtopic "interpreter vs. compiler" I don't think it
makes sense to continue the battle. With intermediate code and VM
languages, firmware and arbitrary specific variants how interpreter
can work, there's plenty of room to digress, nit-pick, and create
red herrings and straw men. The terms are (despite all the variants)
quite clear and can be looked up even in common (non-CS) sources;
there's no necessity to arm oneself with Tannenbaum or others. Hope
we can get over that. A practically useful way to discuss things
might be to speak about concrete concepts, not about (potentially
misleading) labels.
Janis