Combination of anti large company sentiment + people feeling entitled to get things for free if I had to guess. It also usually feels wrong when a corporation threatens a lawsuit over a single person since the US court system heavily favors the person with more money and it's probably a true statement to say that Nintendo has more resources than the lead dev.

Modern Vintage Gamer on YouTube had an interesting take in that by stifling emulator development now it will hurt the industry in the long run because Switch exclusives will become increasingly difficult to play once support ends (an argument I myself don't find all that compelling)

Nerrel on YouTube has a well put together and researched video on emulation where at least in the US it's been tested in court several times that emulators are legal, but obtaining the code for the emulators to run is almost always not since you usually have to make a copy and that violates the publisher's right to copy

"... 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"

Ironically enough Aurora city water consistently wins awards for it's quality lol.

I think the legitimate reason is that Aurora is a physically massive city, has lower housing costs than the rest of the metro area, and Denver has a habit of forcing its homeless population out and into Aurora. The police department is also an absolute good ole boys club who are all terrified of city residents to the point where they drive unmarked/undercover vehicles by default (at least it seems that way, I see so few marked police cars but whenever there's a collection of cop cars with lights going the majority are the undercover)

Sauce: Current Aurora, CO resident. It's not all bad

If Wells Fargo had amazing management, was a massive and undeniable benefit to humanity, and every one of their employees loved working there, how precisely would that have changed the outcome here?

The only two things that I can think of that would have changed what happened is 1) Security actively monitored every single person's activity within the building at all times and make notes so one of the security team would notice that she's been slumped over for a long time, and 2) management insisted that all team members are in office every single day to ensure that they all can see each other. In today's work culture, I'd argue that doing either of those things is bad management.

You say the point is that it happened at Wells Fargo, but let's be more clear here: is your goal to find any reason to help justify your distaste of Wells Fargo?

I do believe Wells Fargo has a lot to answer for, but let's be honest and just in what we go after companies and people for. If we constantly attack entities we don't like for anything that on first pass sounds bad, eventually we'll have called wolf too many times and legitimate complaints will get ignored

I really don't think Wells Fargo has any blame in this, this just as easily could have happened to any company. Perhaps it is a problem with corporate America, but what would you say they're actually negligent of?

it may sound callous and cold, but logistics does end up asking strange questions like "What is a reasonable amount of time to notice that an employee passed away at their desk in a corporate office?" Or "How do we verify that every employee in the building is still alive?"

It's unfortunate and sad what happened to this woman, but I don't see how Wells Fargo played any part in this other than to be a rage-bait headline

God dammit, I lost my ocarina!

Embedded systems run into this a lot, especially on low level communication busses. It's pretty common to have a comm bus architecture where there is just one device that is supposed to be in control of both the communication happening on the bus and what the other devices are actually doing. SPI and I2C are both examples of this, but both of those busses have architectures where there isn't one single controller or that the devices have some other way to arbitrate who is talking on the bus. It's functionally useful to have a term to differentiate between the two.

I've seen Master/Servant used before which in my experience just trips people up and doesn't really address the cultural reason for not using the terms.

Personally I'm a fan of MIL-STD-1553 terminology, Bus Controller and Remote Terminal, but the letters M and S are heavily baked into so much literature and designs at this point (eg MISO and MOSI) that entirely swapping them out will be costly and so few people will do it, so it sticks around

They were doing the breast they can 😒

I'm not really feeling it

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

Omg someone else who doesn't like the xindi arc? There are two of us!!!

Seriously tho, fuck season 3. I love Enterprise but always skip season three, there were just so many things wrong with that season, so many dumb writing decisions like the one you point out

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.

Hey now, simple tailor Garak would just be practical. It would indeed be the safest way

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