The best jokes are still in the comments though

Regarding the other errors, it seems your compiler is simply on strike. This can happen occasionally when compiling french code, and should fix itself in a few days.

The way I see it, if you want to be pedantic about it (it being a joke photo, so potentially unintentionally reversed by the camera, of a cake which is in 3d space and can be seen in both directions) you might as well do it properly and acknowledge that different orders exist for bits.

Indeed writing conventions are also a good point, however this is not writing. People actually working at bit level are probably more likely to see bits on a scope (so in both LSb or MSb order) than as 1 and 0s written on a piece of paper or a screen.

Indeed, endianness is the order of bytes, my bad. I guess I meant LSb vs MSb

Binary exists in both big-endianLSb or little-endianMSb. In other words, both directions can be valid.

As explained below: Endianness is specifically the order of bytes. I was under the impression that it also implied a specific order of bits but anyways, the correct terms for this discussion is Least/Most Significant bit order.

In general terms, it isn’t really. Or at least it is a controversial topic still subject to discussion.

https://opensource.org/blog/public-domain-is-not-open-source

As to this specific topic, the fact that all of the code has to be open source is part of the 10 criteria https://en.wikipedia.org/wiki/The_Open_Source_Definition

As such, you can’t consider open source the public domain portions of a codebase that also has proprietary portions.

Indeed I do

TIL I could easily do em dashes on my phone

OMG thanks.

I think I actually knew this at some point but somehow it completely slipped my mind.

What version are you running? I just tried on Ventura, worked fine on both a .dmg package and some terminal script, both unsigned, and both would need the settings thing if I simply double clicked to open. You still get a prompt, but you have an “open anyways” option.

brew install —cask librewolf

I’ve never used Rust but from my very cursory knowledge of what the borrow checker entails, it wouldn’t add so much to Ada.

Use of pointers is already strongly discouraged by the simple fact that the language is designed to rarely truly need them. Besides, the compiler itself chooses automatically whether to pass data by value or by reference depending on the required results and what is most efficient. You can also specify parameters passed to a function as read-only. Finally, another thing that Ada does to prevent yourself shooting in your foot is to enforce strong encapsulation of functions and data.

Overall, one way to put it in simple terms is that Ada requires the programmer to give enough information to the compiler so as to ensure that it actually outputs what you want it to, which as far as I understand, is sort of what the borrow checker is there for. The downside to the Ada approach is that it is very verbose, but with the kind of code editing capabilities we have nowadays it’s certainly not as much a hassle as it was when Ada came out.

Anyways, I suspect that both languages are different enough in overall paradigm that trying to solve problems in Ada the way you would in Rust would probably be quite frustrating and give rather poor result.

“Before rust you could either have a fast language (C/C++) or a memory safe language (any other language. That is, languages with garbage collector).”

Ada managed to do safe and fast over forty years ago.