As someone who learned Ada for a defense job years ago, I've been wondering how long it was going to take until I saw others comparing Rust to it, both in the sense of the language "safety" goals and the USG pushing for it.
While the rust compiler is leagues better than any Ada compiler I ever had the misfortune of dealing with, the day to day pain that Rust incurs will probably always be a thorn in it's side
I was taught this too growing up in rural america. Did it myself at some land my grandparents had.
Best explanation I've heard for why it "works" is that when looking for places to first install pipes the location tends to be obvious or intuitive, so then years later when someone needs to find it again we naturally trend to the same rough area, pull out those stupid rod things and when they randomly cross there's a pipe there cause we're already standing in the general right spot. Get a high enough success rate and our brains start to think there is causation to the correlation.
"... and no one ever offered him a command. He learned to play it safe, and he never, ever, got noticed by anyone"
This line has been the basis of several career changing events for me, and overall it's worked out pretty well
One I quote often:
"What do I do?"
"FIND HIM AND KILL HIM"
They were doing the breast they can 😒
For graphics, the problem to be solved is that the N64 compiled code is expecting that if it puts value X at memory address Y it will draw a particular pixel in a particular way.
Emulators solve this problem by having a virtual CPU execute the game code (kinda difficult), and then emulator code reads the virtual memory space the game code is interacting with (easy), interprets those values (stupid crazy hard), and replicates the graphical effects using custom code/modern graphics API (kinda difficult).
This program is decompiling the N64 code (easy), searches for known function calls that interact with the N64 GPU (easy), swaps them with known valid modern graphics API calls (easy), then compiles for local machine (easy). Knowing what function signatures to look for and what to replace them with in the general case is basically downright impossible, but because a lot of N64 games used common code, if you go through the laborious process for one game, you get a bunch extra for free or way less effort.
As one of my favorite engineering phrases goes: the devil is in the details
Having grown up and still have the majority of my family live in rural areas, you're correct in that there's a mentality that animals are tools, a means to an end. But I don't think many with that mentality will be forgiving of her for this.
With that mentality there is also a general understanding that these are "dumb animals" who can and will fuck up and especially hunting dogs need a lot of training. A dog who fails the training isn't usually put down, just either given some less strict job, kept as a pet or put up for adoption. Taking her at her word, it sounds like the dog had killed some chickens and had turned towards her and tried biting. But being the dog was only 14 months old, sounds like it had an excited temperament and hadn't learned just how much bigger than other animals it truly is. Hardly a reason to kill an animal, even if it was just raised as a tool.
The ham radio thing makes me so sad, it really does seem like a dying hobby. But when I took my test the club sponsoring it had guys there who immediately berated me for using a practice test guide and getting a cheap piece of crap radio. Like yeah, I know it's a terrible radio, but it was $70 with the practice guide and I'm a poor af college student. That little radio lasted me years and I only bought a new one cause it's battery died and I couldn't find a replacement
Yes and no.
Chess bots (like Stockfish) are trained on game samples, with the goal of predicting what search path to keep looking at and which moves will result in a win. You get game samples by playing the game, so it made sense to have stockfish play itself, since the input was always still generated by the rules of chess.
If a classifier or predictive model creates it's own data without tying it to the rules and methods in reality, they're going to become increasingly divorced from reality. If I had to guess, that's what the guy in the article is referencing when talking about "sanitizing" the data. Some problems, like chess, are really easy. Mimicking human speech? Probably not
As someone who is in the aerospace industry and has dealt with safety critical code with NASA oversight, it's a little disingenuous to pin NASA's coding standards entirely on attempting to make things memory safe. It's part of it, yeah, but it's a very small part. There are a ton of other things that NASA is trying to protect for.
Plus, Rust doesn't solve the underlying problem that NASA is looking to prevent in banning the C++ standard library. Part of it is DO-178 compliance (or lack thereof) the other part is that dynamic memory has the potential to cause all sorts of problems on resource constrained embedded systems. Statically analyzing dynamic memory usage is virtually impossible, testing for it gets cost prohibitive real quick, it's just easier to blanket statement ban the STL.
Also, writing memory safe code honestly isn't that hard. It just requires a different approach to problem solving, that just like any other design pattern, once you learn and get used to it, is easy.
I'm genuinely curious how saying that Linux GUI desktop has issues equates to gargling Microsoft's balls?
So many people forget that while they understand how to use a Linux terminal and how Linux on a high level works, not everyone does. Plus, learning all of that takes time, effort, and tenacity, which not everyone is willing to do. Linus's whole conclusion was that as long as that learning curve exists and as long as it's that easy to shoot yourself in the foot, Linux desktop just isn't viable for a lot of people.
But Linus has done a lot of public fuck ups therefore everything he says must be inherently wrong.
As embedded dev, the stack trace alone scares me. It would be funny to watch the Java runtime blow the 8 frame deep stack on a PIC18 tho