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.

Ada

It has a lot of really nice features for creating data types and has amazing static analysis during compile time.

But all the tooling around it is absolute crap making using the language unbearable and truly awful. If it had better tooling I could see that it would have taken a decent chunk of development away from C and C++

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.

Whenever I replay OOT I never have a problem with Navi. She rarely hard interrupts, usually just a short tone and flashing C button that goes away after a few seconds. The voice lines only trigger if you press the button to call her, in most cases the hints she gives are genuinely helpful, and stays out of your way for the vast majority of the game.

Fi from skyward sword though..... Far worse because she does interrupt gameplay, often repeats what the last dialogue box just fucking told you, and takes several dialogue boxes to tell you what Navi would have taken one to do. I'm glad they significantly overhauled her interactions in the HD release but I'm still going to be hesitant to play that game again

I don't think the MacBook Airs launch is a good comparison.

Sure there was an early adopter tax on being one of the first "thin and light" laptops, but people already know what you can use a MacBook for, there was already a large value proposition in having a MacBook, the extra cost was entirely being more portable than it's full size counterparts. Everything you can do on a Mac, just way easier to take on the go.

I've read a few reviews on it, watched MKBHD's initial review, and outside of a few demo apps they point to the vision pro having no real point to it. Which if true, then it falls in line with existing VR headsets that are a fraction of it's cost and in a niche market, being three times the cost of your competitors is not a good position to be

In Enterprise definitely, but even then the crew would occasionally come across a "lesser" species and then debate about what to do about them.

In TNG era shows most of the other species encountered were portrayed as equal or lesser to humans/federation. Voyager plays with this a little bit since that crew of mostly humans, while almost always more advanced than the people they encounter, they are a lone federation ship with zero support, which knocks down their capabilities a bit.

There's a great throwaway line by Seven of Nine in voyager where the kazon weren't even worth the Borg's time to assimilate, but they were the main antagonist to Voyager those first few seasons because there were so many of them