They were doing the breast they can 😒

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++

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.

Oh yeah I pulled 20 years out of my ass. I could see some manager there saying to plan for it even though all the engineers expect a much shorter lifetime

The issue is that with ongoing service across time, the longer the service is being used the more it costs Kia. The larger the time boxes Kia uses the bigger the number is and the more you’re going to scare off customers.

Using Kias online build and price, looks like the most expensive Telluride you can get right now is $60k MSRP, cheapest at 30k

Let’s assume Kia estimates average lifetime of a Telluride to be 20 years so they create an option to purchase this service one time for the “lifetime” of the vehicle. Taking in good faith the pricing Kia has listed, using that $150 annual package, and assuming that price goes up every year at a rate of 10% (what Netflix, YouTube, etc have been doing) across those twenty years you’re looking at around $8.5k option. At the top trim thats still 14% extra that is going to make some buyers hesitant, at the base model that’s 28% more expensive.

Enough buyers will scoff at that so Kia can either ditch the idea entirely as they’ll lose money on having to pay for the initial development and never make their money back, or they find some way to repackage that cost and make it look like something that buyers are willing to deal with.

To me the bigger issue is the cost of the service vs what you’re getting. Server time + dev team + mobile data link cannot be costing Kia more than a few million annually, mid to upper hundred K is more likely so they must not be expecting that many people to actually be paying for any of this

Yup your right, I was wrong. Valve keeps the copyright regardless.

Dolphin situation was different though. https://dolphin-emu.org/blog/2023/07/20/what-happened-to-dolphin-on-steam/

Valve only ever insisted that Nintendo had to give Dolphin permission to distribute since Valve was afraid of a potential DMCA coming from Nintendo if Nintendo thought that the encryption keys were IP illegally being redistributed. Since Nintendo says emulators are illegal everywhere but a courtroom, Dolphin team knew that they’d never get an ok. Valve probably knew that but didn’t care enough to help fight that legal battle.

I’m not sure Valve cares about brownie points with Nintendo. The Steam Deck is a direct competitor against the Switch, Valve has done nothing to curtail the use of Switch emulators on Deck, and the work Valve has been doing makes using a switch emulator a better experience.

This whole thing only makes sense if Valve wanted to protect their IP. Involving Nintendo really does sound like blame shifting without having to actually go to court

I’m with you on the first part. It makes no sense for Valve to do this. Using LibUltra or not, Nintendo has been relatively lax on people creating new code for the N64. At least to my recollection only in cases where Nintendo felt their IP was directly being threatened did they try and take down fan projects. Even then they heavily rely on the redistribution of Nintendo IP to take things down. Admittedly I have only seen others talking about the Portal 64 project using LibUltra but even so that’s Nintendo’s fight, not Valve’s.

I don’t see how Valve could possibly be afraid of getting sued here by Nintendo, it doesn’t make sense. Valve did not create it, nor distribute, advertise, or aid in any way. IANAL but I don’t see how Valve could possibly be listed as a party to the lawsuit unless Nintendo lawyers agreed with Valve lawyers to go after this guy for IP theft.

TBH I see this more as Valve seeing that with a project this publicly known, if they don’t defend their IP here they’ll lose any future copyright claims and want to prevent it. They also see an opportunity here, blame Nintendo who won’t flinch it at since they get labelled legal bad guys all the time, no real dent to their reputation while saving Valve’s internet golden child perception. Valve would never do something like this so it MUST be Nintendo’s fault. Based on the comments in this thread and I’ve seen else where, that seems like a good assumption. Nintendo takes the heat while Valve protects their IP.

I’m a big fan of “Find him and kill him!” along with “Death to the opposition”.

So many great Worf quotes from DS9