On Tue, 28 May 2024 23:54:46 +0200
Antony Stone <Antony.Stone@???> wrote:

> On Tuesday 28 May 2024 at 23:16:42, Steve Litt wrote:
>
> > I've looked into the newer languages like rust and go and Julia, and
> > they don't work for me.
> >
> > As far as Julia, it's buggy as hell.
>
> Hm, references?
>
> > With go and rust, these languages seem much broader than C, Python,
> > Lua, old school Turbo Pascal and the like.
> >
> > What I mean by "broader" is that you need to memorize a whole lot of
> > stuff because a whole lot of stuff is built into the language instead
> > of just being createable in the language.
>
> Isn't that supposed to be one of the advantages of them - that you don't have
> to build stuff for yourself, but it's built in, and is (presumably) done well?

Hi,
Why you imply this, all buggy C programs out there were presumably
done well, until it's shown that they were not, so the main problem is bad programming
not bad program languages, why rust should not be affected by bad
programming, is there any mathematical proof that it is perfect?
I fear that just because of the fact that all is "built in" and the bug number
is correlated with the code size there should be naturally more bugs hidden in it.

> After all, look at a modern API to interact with some database-backed system:
> sure, you could go in and talk to the database itself, but it's generally much
> cleaner to learn the API and use the appropriate methods to get at the data
> you want. You still need to learn the API, though.

Exactly If you learn the C API than you don't need memory safe
languages because you write memory safe code by sticking to the C API.

Ciao,
Tito

>
> > As a counterexample, take C. C has very few commands and keywords to
> > remember. Learn =, ==, <, >, if, while, for, struct, typedef, arrays
> > and pointers and a small portion of the standard library and you're
> > good to go. When you need to do something, you don't search for a
> > command to do it, you just make it. If you didn't know about memcpy(),
> > you could write it in about 6 lines of C.
> coding in) is a low-level language (because you can make it do anything you
> like and it won't protect you from being a bad programmer) or a high-level
> language (because you're not actually dealing with the assembler and machine
> code unless you really really force things, and it has nice constructs such as
> block coding and if/else which you don't get with assembler code).
>
>
> Antony
>