I'm a Mechanical Engineering student and one of my recent projects had a lot to do with onboard computers on modern vehicles. This article is viewing only one side of the scene, and doing this with great bias.
While some of the examples like the Dinan S1 M5 is legit, these companies are less of a concern that the average script kiddy who wants to "hack" his car because it's the new thing to do in town. Advanced features like traction control and even cruise control on vehicles are critical to implement perfectly, and a small mistake in the code that guides these can be fatal. Companies like BMW spend millions on testing the code and making it perfect for use, and what this article is arguing for is replacing that with something that anybody can write. This is not safe.
On the other hand, some things like the Nismo and it's software imposed speed limit are just state restrictions. The Nissan GTR has a set speed limit which is turned off when the GPS detects that you're on a racing circuit.
Companies are ethically obliged to make sure that no amateur or third-party can make their cars unsafe. They are right in doing so, because at the end of the day they are liable. If there is a fatal accident of a BMW M5 due to a software failure error, nobody (read, the media) is going to blame Dinan. BMW takes the brunt for it. They are blames for writing "shitty software".
Unless companies or individuals are legally obliged to be accountable for the changes they make to a car, companies are right in making the cars impossible to tweak. It's not about the fact that you "own" the car and hence should be allowed to do whatever you like. That works only for iPhones and Play Stations where your actions probably wont result in somebody dying.
tl;dr — Much like spare parts, faulty software can kill onboard passengers in vehicles. While hacking sounds "cool", slight irresponsibility can end badly.
Ha! Traction control in my Subaru Forester is a joke. On snow and ice it turns my car into one of those football players in that vibrating football game. The only way to drive in Iowa is to turn the feature off, every time I get in the car.
You bring up quite a few excellent points, re: OEM engineering versus shade-tree tinkering. There is definitely merit to considering the "brain" of a car to be integral to its safety. Should a person wish to modify their car from OEM specifications, there are numerous avenues by which this can be done in a negative manner. As a reference point, I've been a "car guy" and fan of tuning / customization / tinkering for over a decade, and even had a chipped turbo car at one point in my life.
Regarding a real-world hazard specifically, I'll cite the example I frequently see on the road of a Chevy/GMC/Caddy SUV with much larger than stock wheels and tires and bone stock brakes. This is an obvious violation of the OEM engineering, a genuine physics problem. The safety of the driver/passengers is in jeopardy, as is the safety of others who share the road.
Thus, I'd like to note that I believe there's a bit of self-serving "caution" in place when it comes to manufacturers. I'll be stating a far-fetched sounding hypothesis, but one I believe is relevant. Okay, so if a manufacturer sells a car, but with extensive restrictions on modification, why does the manufacturer simply get to "write-out" safety obligations for the lifespan of the vehicle? Sometimes there are "service plans" that will address some basics (oil, tire inflation), but only for a limited timeframe. Should OEM safeguards to computer systems only apply for that period of time?
Or, to put it another way, if manufacturers cared about safety, why wouldn't they be held responsible for performing State Safety Inspections and provide the materials to ensure a vehicle meets the safety regulations year after year after year?
I know this is an out-there type of postulation, but when talking about vehicle safety, there are many factors that are much more practical in nature (maintenance, driver distraction, age-related degredation of faculties) that get little to no discussion because they're difficult problems. I'm mentioning this notion as a direct response to your theory that "companies are right in making the cars impossible to tweak" because, practically speaking, that's not the case at all...I see this discussion as many trees in the forest of motoring...
While some of the examples like the Dinan S1 M5 is legit, these companies are less of a concern that the average script kiddy who wants to "hack" his car because it's the new thing to do in town. Advanced features like traction control and even cruise control on vehicles are critical to implement perfectly, and a small mistake in the code that guides these can be fatal. Companies like BMW spend millions on testing the code and making it perfect for use, and what this article is arguing for is replacing that with something that anybody can write. This is not safe.
On the other hand, some things like the Nismo and it's software imposed speed limit are just state restrictions. The Nissan GTR has a set speed limit which is turned off when the GPS detects that you're on a racing circuit.
Companies are ethically obliged to make sure that no amateur or third-party can make their cars unsafe. They are right in doing so, because at the end of the day they are liable. If there is a fatal accident of a BMW M5 due to a software failure error, nobody (read, the media) is going to blame Dinan. BMW takes the brunt for it. They are blames for writing "shitty software".
Unless companies or individuals are legally obliged to be accountable for the changes they make to a car, companies are right in making the cars impossible to tweak. It's not about the fact that you "own" the car and hence should be allowed to do whatever you like. That works only for iPhones and Play Stations where your actions probably wont result in somebody dying.
tl;dr — Much like spare parts, faulty software can kill onboard passengers in vehicles. While hacking sounds "cool", slight irresponsibility can end badly.