@tygre

Quote:

By experience, I must unfortunately report that trains, cars, etc. use a mixture of assembly, C, C++, Java, C#... all the way to JavaScript

I didn't say "cars", though I am familiar with MISRA C. Ironically, there's evidence that MISRA C actually does the opposite of what it intends. Here's a golden quote from that article:
Quote:

this makes it possible that adherence to the MISRA standard as a whole would have made the software less reliable.

After all, the problem is that they're starting from C, a language where "unsafety" is a feature, not a bug.

For trains I would hazard a guess that it depends very much on what system on the train you're talking about, and possibly the train corporation; see here for instance. I could easily see JavaScript being used for certain things.

That said, rail is such a big part of AdaCore's business that they dedicate an entire page to it. But, yeah, I remember seeing a job ad a couple of decades ago for Norfolk Southern where they wanted Java programmers, and I considered applying.

Having said so much on Ada's behalf, I'll add that the general impression in the CS community that Ada is "dead", "dying", and/or "too complicated" has an effect. "The unwisdom of crowds" and all that.

Quote:

And my contribution to the language war: Java before they introduced all these bloating features, like generics, lambdas, etc. (So, that would be Java 1.6 or 1.7)

I agree, to an extent! The designers of later Java looked at what worked in other languages (*cough* Ada *cough*, C++, and of course LISP where many of these features originate) and decided to implement in the worst way possible. Kotlin improves on it by defining "in" and "out" parameters for the generics. Of course, the Kotlin designers also implemented a language with very strong null safety mechanisms, whereas Java's designers thought C's profligate use of null was a great idea, despite billions of dollars' worth of mistakes.

Quote:

As for the ARM discussion, it's illuminating, bring it on!

I agree; I've been enjoying that. I've always wondered about the big-/little-endian implementation on ARM.

_________________
I've decided to follow an awful lot of people I respect and leave AmigaWorld. If for some reason you want to talk to me, it shouldn't take much effort to find me.

@tygre

Quote:

As for the ARM discussion, it's illuminating, bring it on!

Here you go. Side-by-side comparison of M68k code and its JIT translation for the AArch64 operated in big endian mode. A lot of FPU since it is a part of path tracer code. Result of my Emu68, by the way :)

Last edited by michalsc on 21-Apr-2021 at 03:03 PM.