Re: Top 10 most common hard skills listed on resumes...

On 8/26/24 03:54, Michael S wrote:

On Sun, 25 Aug 2024 17:48:14 -0700
Tim Rentsch <tr.17687@z991.linuxsc.com> wrote:

...

It's been amusing reading a discussion of which languages are or are
not high level, without anyone offering a definition of what the
term means. Wikipedia says, roughly, that a high-level language is
one that doesn't provide machine-level access (and IMO that is a
reasonable characterization).

>
I don't like this definition. IMHO, what language does have is at least
as important as what it does not have for the purpose of estimating its
level.

That's not a particularly useful response. It would have been more
useful to identify what features a language should have to qualify as
low level or high level.
Defining a level solely in terms of what the language has, without
regard to what it doesn't have, leads to a potential ambiguity: what if
a language, let's call it A/C, which has every feature that you think
should qualify it as a low level language, AND every feature that you
think should qualify it as a high level language? If you define those
terms solely in terms of what the language has, then A/C must be called
both a low-level language and an high-level language.
If, on the other hand, you define the level of a language both in terms
of what it has, and what it doesn't have, A/C would be unclassifiable,
which I think is a more appropriate way of describing it. Every time
that someone says "low level languages can't ...", that statement will
be false about A/C, and similarly for "high level languages can't ...".

One principle that should be kept in mind when you're defining a term
whose definition is currently unclear, is to decide what statements you
want to make about things described by that term. In many cases, the
truth of those statements should be a logical consequence of the
definition you use.