[dsuth]

Don't get me wrong, I'm the last person to defend the overuse of software patents. Where people are genuinely creating extremely complex functionality in software however, I think they deserve some protection for their outlay.

On your point about historically owning vehicles, as a software developer you will understand that there is a very wide gap in competence between being able to tune a standard motor, and being able to inspect and modify software that controls a car safely. Currently this is protected so that only the vendor can change it, precisely because that's how we wrote the standards - vendors are responsible for their code, and responsible for the safety outcomes on the road.

If we moved to an open model where anyone could modify the software in their car - what do you think would happen to the safety and reliability of that software? I don't think any of us could imagine that it would improve.

[tremon]

> you will understand that there is a very wide gap in competence between being able to tune a standard motor, and being able to inspect and modify software that controls a car safely

A big part of that is because cars have been around for over a century, and there has been a huge tinkering crowd to learn and teach newcomers to the scene. The software/robotics crowd is maybe only a decade old (ignoring the hacking scene). Why wouldn't we in a hundred years or so be able to write our own car control software? Or more importantly, why shouldn't we?

I also disagree on your stance that open-sourcing it wouldn't improve anything. If anything, open-source has been the driving force behind great procedural advancements in software design: source control, code quality measurements, unit testing, metaprogramming, have all been influenced or driven by large open-source projects. If anything, I think the first thing an open-source movement for car control software would produce is testable code, probably from a greater focus on compiler-enforced design-by-contract languages.

In my mind, the only reason we wouldn't be able to progress to that point is exactly because of these anti-reverse-engineering policies, because of IP protection and litigious manufacturers. I'm firmly with the EFF on their Freedom To Tinker cause, and I think it's perfectly acceptable for the EFF to take this case as an example of why current policies are wrong.

[marincounty]

"If we moved to an open model where anyone could modify the software in their car - what do you think would happen to the safety and reliability of that software? I don't think any of us could imagine that it would improve."

1. 99.99 percent of the owners of these automobiles wouldn't have a clue to even where to access, or what to do with the code? Most can't find their AlDl, or OBD plug.

2. Most mechanics out there don't know much about car computers, and 99.9 % know nothing about programming. When something goes wrong with the computer; they just replace it. When I was in automotive school, the failure rate of car computers were 1 in a million. I think that's low though? Mechanics just replaced the computer--hopeing they got the right one. The one in the vechicle was usually fine, but was shorted out by fat fingers, and hangovers.

In real life, when a mechanic, usually erroneously blames the automobiles computer, as the fault of the problem, he/she just replaces it. Their biggest achievement is not shorting the new computer in by installing it. Of course when they short out the computer, they blame the computer as defective, and charge the customer.

Dealership mechanics(some) can reflash their particular brand of vechicle computer/computers, but they don't code anything. They push a GUI button, and answer yes, or no questions the enginneers at corporate programmed.

As to propriatiry software, it's not about safety, and reliability. It's about customers being held hostage to the dealership. You buy a fancy car, with a bunch of do-dads on it. You can't just bring your ailing car to any independent mechanic. They don't have access to the computer system. Most wouldn't have a clue to the actual code, but they need trouble codes. These trouble codes are being held hostage. The dealer will happily fix your car, but at dealer prices.

Even if people abused the open source software(affecting emmissions), it would be caught at the bi-annual smog check? As the safety, the automobile companies would love to blame tampered with software in order to lessen their liability? (It sounds like it would be pretty easy to test for altered code, on the manufactures end?) For years now, I can buy computers that improve a vechicles performance, but it's just not worth not passing an emmission test--in my view.

So, I don't think it's about safety, It's about greed. And maybe other factors; like they don't want the Programmers peering into their horrid code. Code that defeats smog checks. Code that reuses other manufactures patents--without payment? Code that is just terribly written, and causes numerous accidents, and thefts?

Again, I don't want much. I just don't want to essentally lease my vehicle after buying it with cash? What? Yes, because no one other than the Dealership can work on it at $170 hr. The idependents will attempt to work on my new vechicles, but they never seem to solve the problem. Why should they, they don't have the information! These automobiles have gotten so complicated, even your dealership mechanic is usually figuring out your cluster of sensors on your dime. It's gotten to be quite a racket? I forsee acres, and acres of newer automobiles that are junked because they aren't worth fixing? Give out trouble codes? Give out a service manual with every new car sale. Tell the customer up front, "I will see you again sir, for many years--let me program all our dealerships into your GPS?" "I hope you never lose that high paying job?" "Your so good looking, why would you ever want to get your cute hands dirty working on that dirty automobile?"

Give me access to my computer on my car, at least the trouble codes, and access to a reasonably priced scan tool? I'll even sign a waver--if that's the problem?

[bad_user]

> In real life, when a mechanic, usually erroneously blames the automobiles computer, as the fault of the problem, he/she just replaces it.

For one, it depends on the repair shop you're talking about. Personally I require proof that the problem has been solved.

But anyway, for one while it may be true that most mechanics will simply replace a component when broken, replacements can also be made by anybody and that will drive the cost down and encourage local businesses.

And really, many software developers are nothing else than glorified mechanics. Right now the supply and demand curves are favoring us, but give it some time and you'll see software developers working for car repair shops. After all, the trend is always commoditization and at some point investors will stop wanting to create frontends to a database that are automating an Excel spreadsheet communicated in an email exchange.