Nice to see the "true spirit" of OpenSource being practiced and growing in Europe...I hope other countries jump into this as well, with support and resources.
Weird, I have honestly never walked into a Barnes and Noble and had satisfaction with any of their technical content on the shelf. That pleasure died when we lost Borders.
Not to mention, what happens in the event of damage to the towed aircraft rendering flight operations impaired such that it affects the towing aircraft?
This just seems intentionally bad to show where Rust would be better. This is yet another example of what I call "corner-case" instruction, which I define as, "I am going to take an obviously terrible corner-case that shows what an awful developer can do that will break a program, then demonstrate my brilliance by introducing my (highly-biased) opinionated point I wanted to make..."
In this particular case, it was subtly, Rust is preferred because it doesn't allow unsafe memory operations such as the one demonstrated. Really, all it demonstrates is that you can create really bad C++.
In the end, Streaming Services have proven to be nothing more than advertising platforms scattered with brief moments of content. The ads outweigh the content making it less cost effective than going back to Cable, which is still terrible also. Hence the need to pirate and control what content you see.
This is all well and good but, for my mileage, nothing can ever beat C++ generics and the RAII pattern when there is a choice between plain old C and C++ . One second while I get my fire-retardant suit on...
Maybe...the cynic in me says that someone feels this needs to be preserved because it will become another Google relic in favor of something newer, or more shiny. Or likely something written in Go...just a guess on my part...