Should Developers Be Liable For Their Code? 517
Glyn Moody writes "They might be, if a new European Commission consumer protection proposal, which suggests 'licensing should guarantee consumers the same basic rights as when they purchase a good: the right to get a product that works with fair commercial conditions,' becomes law. The idea of making Microsoft pay for the billions of dollars of damage caused by flaws in its products is certainly attractive, but where would this idea leave free software coders?"
Not my fault (Score:5, Funny)
Re:Not my fault (Score:5, Insightful)
Hmm, it would probably go like this:
Engineers: "It's the software!"
Developers: "It's the hardware!"
Both: "Why didn't the testers catch this?"
Testers: "That wasn't one of the use cases, so it's the designers' fault."
Designers: "The product wasn't meant to be used that way, so it's a documentation error if the tech writers didn't tell users not to do that."
Tech writers: "Don't look at me, I just write what you guys tell me to write."
Open Source Developer: Don't look at me. My users contribute design ideas, code, docs, testing, etc. So if there's a problem, it's their fault 4 times over for designing it, coding it, failing to test it, and failing to document it. ;-)
Re:Not my fault (Score:5, Insightful)
Actually it'll probably work out like:
Providers: Yeah, it's broken, sorry. Contact our insurance company, and put in a claim.
Clients: Oh, you're insured for this? Great.
Providers: Yeah, of course. We're pros, and totally insured for this, like all the other pros. Why else do you think you couldn't get a two-page website for less than $12,000?
Re:Not my fault (Score:5, Funny)
Insurance company: Did the contract specifically say you could use that menu item while wearing a green shirt?
Clients: Well no, not specifically, but...
Insurance company: DENIED!!!!!!!!!!!!!
Re:Not my fault (Score:5, Funny)
Think of the mess when people start suing developers of web applications!
App Developer: Its the browser!
Browser developer: its the JavaScript library!
JavaScript library Dev: its the VM developers!
user again: Yeah lets sue Sun!
Javascript developer: JavaScript is not
User can't find Sun and sues Microsoft for VBScript because its the closest thing to it.
Microsoft: Oracle bought Sun.
Oracle: Hell I knew I shouldn't have bought Sun, anyway, Java is OpenSourced so I have no control over it.
Java developers: JavaScript is not Java!
User: Why am I here?
Java developers: I don't know, but if there is anything wrong, its usually Microsoft's fault.
Microsoft:
Microsoft Lawyer: Lets counter suit the chair manufacturers for not anticipating our use case.
Fast forward to court date after every software and furniture manufacturer under the sun gets involved in the case....
User's lawyer: What do you mean you got windows off of pirate bay? You could have mentioned this small detail before I took on your case!
RIAA Lawyer: Don't worry, you can plead insanity, and I can take it from here.
TPB: Argh! We be hosting the tracker only mate! not the software! the software be hosted in china.
After a very long court proceeding which involved everybody under the sun and caused three world wars, two nuclear stand-offs, and countless bus parties... a strange group of people came crashing into the courthouse
Guys in red:Nobody expects the Spanish Inquisition!
and it starts to go downhill from here!
Re: (Score:3, Funny)
I like your style. ^^
Got an humoristic blog? With an URL for me?
GPL v4 (Score:3, Insightful)
The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to destroy you and leave you (and or your business) reeling in economic and personal obliteration*. That our software looks like it does something productive should not be mistaken for any intent to be useful in any fashion â"the software is free for all its users.
*The GPL or authors of software using the GPL license make no guarantees regarding the effic
Re: (Score:3, Informative)
Re: (Score:3, Informative)
That's why if blame must be cast, it must be cast on the company as a whole. If you buy a television and it burns down the house, you don't sue the chinese kid making 3 cents and hour, you use the company (Sony, Toshiba, etc).
As for free software (beer), almost all free software comes with a notcie along the lines of "This software is provided free of charge without even the guarantee of sale...". If you provide someone with something, but do not charge for it, there is no guarantee of sale, so there is no
Re:Not my fault (Score:5, Funny)
It worked on my box.
gpl comes with a license (Score:3, Interesting)
Re:gpl comes with a license (Score:5, Insightful)
Sure, since that's a public health matter. If software controlling an aircraft crashes and causes the aircraft to crash too and that kills people, I'm pretty sure the software makers might end up liable too.
To continue your analogy, if a soup kitchen gives you soup that is too cold, comes in a plastic bowl and is too small of a portion, you've got nowhere to turn with that and you should have nowhere to turn with that, it is gratis after all. On the other hand, if this happens in a restaurant that calls itself high quality and advertises the famous chicken soup from a master chef and you get the same treatment, then there are numerous consumer protection agencies in Europe at least to fine the given restaurant.
Re: (Score:2)
Re:gpl comes with a license (Score:5, Interesting)
If software controlling an aircraft crashes and causes the aircraft to crash too and that kills people, I'm pretty sure the software makers might end up liable too.
Actually it would probably be whoever decided that that software was OK to use in an aircraft. If I were to somehow get an aircraft and install Gentoo on some critical system, I'm pretty sure I'd be the one to get in trouble rather than the Gentoo or Linux (kernel) or Glibc people.
Aircraft software (Score:5, Interesting)
I make software that goes on an aircraft for a living.
All such software is required to be certified by the FAA, which has elaborate requirements for development, documentation, and testing (the applicable document is DO-178B).
I'm told that the reason for certification is not safety, but culpability. If your software satisfies the requirements and passes review by the FAA, then your company will not be held liable if it causes problems.
In essence, certification represents "best effort" engineering practices and tries very hard to eliminate bugs in the final product.
By the time a software package gets on a plane, many people have combed over it looking for problems, and the testers have spent a massive amount of time running it. There is a safety/failure hazard analysis which asks all the "what if" questions, and the flight crew has written procedures in case it fails.
If a bug is found after deployment (this happens occasionally) and it is discovered that there was a flaw in the certification process, all hell would break loose. It would open up the FAA and the company to all sorts of lawsuits from injured parties. The people who signed off on the certification would essentially be screwed.
The FAA is generally a bunch of bureaucrats. The one thing they do well is look out for their own interests.
Oh, and I worked for the company that got Microsoft Windows certified to run in the cockpit as a map display. It's Posix compliant, dontcha' know!
Re:gpl comes with a license (Score:5, Interesting)
Well, as somebody with an engineering degree, I know that we were taught that we were responsible for designs produced using software products. So, for example, if one used structural design software to design a building, and that software gave erroneous results, you are to blame, and not the software.
Re: (Score:3, Insightful)
Well, as somebody with an engineering degree, I know that we were taught that we were responsible for designs produced using software products. So, for example, if one used structural design software to design a building, and that software gave erroneous results, you are to blame, and not the software.
The real blame, ultimately lies with the deepest pockets.
Re: (Score:3, Funny)
What if somebody sent the message, "Don't eat that banana, it's poisoned". But your Gmail clone loses some words and the other side gets, "eat that banana" only?
Re:gpl comes with a license (Score:5, Interesting)
Except you just can't run anything for aircraft control. Read the fine print on software like Java, Windows and other items. You'll see it explicitly states you are not to use it for nuclear power plants, aircraft control and other life-critical applications. There are special rules for the super-critical stuff.
On the other hand, if this happens in a restaurant that calls itself high quality and advertises the famous chicken soup from a master chef and you get the same treatment, then there are numerous consumer protection agencies in Europe at least to fine the given restaurant.
That concept is so pathetic I don't know where to begin. Consumer protection agencies to fine a restaurant for poor quality and bad treatment? Are Europeans that big of pussies? What is wrong with "tell your friends they suck, don't eat there" and watch their business evaporate? You can't be serious that the government steps in for things like this!?
Re: (Score:2)
There is a difference between matters of personal taste and false advertising, deceptive business practices and business scams. I was trying to make an analogy
Re:gpl comes with a license (Score:5, Funny)
A good analogy is like a map that lets you see a wider view of the terrain. A bad analogy is like the wrong sort of petrol in your car.
Re: (Score:3, Funny)
Re: (Score:3, Insightful)
If software controlling an aircraft crashes and causes the aircraft to crash too and that kills people, I'm pretty sure the software makers might end up liable too.
But the proposed legislation is consumer protection, which is a totally different branch of legislation to that relating to B2B contracts. Yes, the software makers might end up liable, depending on the contract between the service provider and the software supplier, but they might not. There's a lot of Linux used in air traffic control in Europe, but I doubt anybody involved in Linux could end up liable in the event of an accident. Rather, the air traffic service providers have to make sure they have adequa
Re: (Score:2, Interesting)
you can sue a soup kitchen if it gives you food poisoning.
But equally, people should be free to say what use their product is intended for. You can sue someone if they sell you food, you can't sue someone if they sell you some substance, and you decide to eat it (especially if it has warnings not to eat it).
The GPL states (similarly to most licences):
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PAR
Re:gpl comes with a license (Score:5, Insightful)
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
If the law changes and requires software to offer a warranty then the GPL will be vulnerable. Even if the GPL didn't include that statement, a court could invalidated it because a contract that breaks the law is not legally binding.
Changing a license for a big project isn't always easy.
This will most likely hurt companies like Redhat, Canonical, Novell and other corporate open source contributors because they will have to stand by their products and you're bound to get a few cases where they have to pay up.
But it's not a law yet.
Re: (Score:3, Insightful)
But equally, people should be free to say what use their product is intended for.
As a number of people pointed out, there are exceptions to this. Basically, laws can restrict what types of agreements can be entered into. The most extreme example of this is that you can't enter into a contract to be a slave. A less extreme example would be a law that voids all "no warranty" clauses of software licenses.
I also fail to see how causing injury is comparable to alleged liability of Microsoft.
Law suits are a mechanism for recovering damages caused by the other party. You can't sue someone for wrong doing (that's what criminal laws are for). What you sue for is the damages
Re:"May Contain Bugs" (Score:5, Funny)
> I'm looking at a silica packet that is labled, "Do not eat."
I followed those instructions and nearly starved to death!
My lawyer advised suing for "negligence causing anorexia."
Re:gpl comes with a license (Score:5, Funny)
I know a joke based on this:
If food makers used the same licenses as software makers, then in a opaque box, there would be a license agreement:
1. The manufacturer does not guarantee that this item can be used for food and is not liable if it is not suitable for eating.
2. The user is not allowed to examine the contents of this item (for example to look if it had rat tails in it).
3. The user has a right to use (eat) the product, but does not become its owner.
4. The right to use (eat) the product gets only one person.
5. The user does not have a right to sell of give away the product to third parties.
6. The manufacturer does not guarantee that the product is free of hazardous materials (for example, rat poison, dioxin etc).
7. The manufacturer is not liable for any health risk to the user because of the product.
8. The manufacturer guarantees that the box is made of high quality materials and, if there is a flaw in it, will replace the box. This does not extend to the product that is in the box.
9. By opening the box and reading this agreement the user automatically agrees to it.
Re: (Score:3, Insightful)
Silica gel, yum yum!
Re:gpl comes with a license (Score:4, Informative)
Doesn't GPL have explicit anti-sue protection, with that whole section on lack of implied merchantability or warranty?
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see http://www.gnu.org/licenses/ [gnu.org].
From the GNU how-to [gnu.org].
Does anyone know how this would interact with the potential EU law?
Re: (Score:3, Insightful)
Both open source and closed source software typically include non-warranty clauses. If a new law were passed to void those clauses, it would affect both types.
Re: (Score:3, Insightful)
In the food poisoning case you've suffered pain and discomfort.
You don't sue because you've been wronged. You sue because something of yours was taken away without your consent. If the law removes your ability to consent to certain risks (such as the risks associated with using untested software), then you'll be able to sue for the losses you would incur as a result of using untested software.
Ask for a refund.
The amount of damage you suffer is not limited to the price of the product when it comes to recovering damages through law suits. You have $0 involved in a transaction with a c
Re: (Score:3, Informative)
As to the moronic comment about the car thief, learn the difference between civil and criminal law and then come back, OK?
I am fully aware of the difference. Please, take your medication now.
if you pay you get working stuff or a refund, (Score:5, Interesting)
If someone sells GPL based software, they are free to do so and pick up the tab on flaws in the product. Same goes for proprietary software.
This should have been done at least 10 years ago.
Re: (Score:3, Insightful)
If you get free food and it gives you food poisoning, the one that made the soup will still be viable. Same issue here.
Re: (Score:2)
Yes. You also cant tell someone on the street that "I am not responsible for any thing that may happen if you take this free fight with me. Go ahead if you are really sure..." and you happen to kill him. You will be responsible, even if it was free and you warned.
Re:if you pay you get working stuff or a refund, (Score:5, Insightful)
This is an issue that is more complicated that should developers be held liable for perfection. Is it good enough to work reliably in most cases? Was there a malicious or negligent intent to box and bunch of schlock? There are a lot of good questions that could be asked here when trying to define the responsibility and accountability of development companies.
The market for proprietary software and the community for open source software does function pretty good for weeding out the crapware.
Re: (Score:2, Insightful)
This should have been done at least 10 years ago.
Well, yes. But like a great many technological issues the people who make the law have been completely ignorant that the issue even exists, let alone proactive enough to formulate a solution for it.
GPL (Score:5, Informative)
http://www.opensource.org/licenses/gpl-license.html [opensource.org]
Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.
Re: (Score:3, Interesting)
there is no warranty for this free software
every software license worth its salt has this clause. laws can make certain parts of agreements void. for example, you can't enter into a contract to be a slave.
Re: (Score:3, Insightful)
Re: (Score:2, Informative)
If a law is passed 'protecting' the consumers then this clause of the contract become void. You can't have a contract to kill someone and have it upheld in court. Same goes with this sort of thing.
There are other complications but basically that clause doesn't help because it would become an illegal clause.
open source is still not liable (Score:5, Insightful)
Because the software is not purchased there is no contract. "permission to use" is not the same as a sale.
Stupid Idea (Score:5, Insightful)
The idea that code should be perfect is a stupid idea: consumers don't want that.
They want "good enough," not perfect. Perfect costs a great deal of money, probably 4X, and consumers will buy the good enough product, at 1/4 of that price, well beyond 95% of the time.
C//
Re: (Score:2)
There will never be such thing as perfect code, not even with 4x prices to create it. You can improve a lot tho.
Re:Stupid Idea (Score:5, Interesting)
The idea that code should be perfect is a stupid idea: consumers don't want that. They want "good enough," not perfect. Perfect costs a great deal of money
Your comment is "insightful", but it is beside the point. This is exactly the same issue with all engineering. An object manufactured to better standards than needed for the purpose is an overly expensive object. The question rather is the web of responsibility. If Microsoft or Google or even somebody's shareware makes a claim of suitability, certainly the consumer should have redress when it proves unsuitable.
There are many other dimensions of this issue. For instance, the software industry is well known for adding pointless complexity - features that nobody ever asked for. If GE added a can opener to a toaster, they would be liable for any unexpected risks this reveals, but Microsoft can make Word so complex that businesses using it accrue large expenses related to training, etc., and risks related to misformatted and delayed documents and so forth - and yet Microsoft currently faces no significant market pressure from liabilities associated with having broken their own product.
And that happen ohow often ? (Score:2)
Re: (Score:2)
The idea that code should be perfect is a stupid idea: consumers don't want that.
They want "good enough," not perfect. Perfect costs a great deal of money, probably 4X, and consumers will buy the good enough product, at 1/4 of that price, well beyond 95% of the time.
How is this different from any other product that people regularly pay for? Yet the makers of those products are still liable.
Re:Stupid Idea (Score:4, Interesting)
Exactly. The problem with trying to enforce this kind of measure for software is that there is a cost/performance curve, and most people don't want to pay to be right up at the end of it.
Heck, no-one in the world knows how to get right up to the end of it. Even the guys at NASA, whose development process is awesomely effective at producing reliable software compared to the the commercial/home user industry, still get bugs. Given the nature of their work, their bugs can cost as much in a single mission as a bug in widely used home user software costs spread across the whole user base, potentially including a cost in human lives, so it's not like they're hiring stupid people or not trying to get everything perfect.
Re:Stupid Idea (Score:5, Funny)
Perfect costs a great deal of money, probably 4X
With free software, it's even more than 4X. Maybe even 10X.
Re: (Score:2, Insightful)
First of all, I would strongly disagree that most consumer software is currently 95%, more like 45% at best. I currently recommend people NOT use many of the consumer products with the highest market penetration, simply because it is nearly impossible to make them both safe and usable.
Second, we're paying far more than 4x for "good enough". Sure, the consumer goes and pays the "good enough" price, but that is FAR from the end of it. Consumers spend hundreds of billions every year fixing and securing "goo
Re: (Score:2)
What if.. (Score:5, Insightful)
Say a developer uses a number of 3rd party libraries (ie. Boost, TinyXML, etc), who will be pay damages if the program crashes in a bad way? The developer for not trying to catch 3rd party crashes, or the 3rd party for writing in bad code?
Re:What if.. (Score:5, Insightful)
If my harddrive breaks within warranty period, I don't go to the company who manufactured the silicon or the ICs, I go to the retailer or Samsung, who sold me the drive.
Re: (Score:2)
Developer will pay for the first hand damages, but on the hand he can go after the 3rd party library maker and try to get them pay for his damages. This is how it works elsewhere too.
Only if they get final say on release of the code. (Score:5, Insightful)
Until the coders get total control of the project, from inception to completion, then no, they cannot be held responsible for bugs in the code.
How many companies push to get code out the door with *imperfections* - claiming they'll fix those in the first update?
Too many these days.
I'd say it's the management that controls the release schedules that should sign their names in blood on the bugs still known about (and unknown as testing probably wasn't allowed to complete).
Re: (Score:2)
I think it'll be the companies responsability here, not a single developer's. If the company gets shit tho, they'll prolly fire that developer.
Re: (Score:3, Insightful)
I have mixed feelings on this.
This would only work if 'coders' gain the professional standing like doctors and lawyers. I would welcome the chance to have better qualified people in the field as well as bigger bucks.
On the other hand, all of software is design. It's hard to fault someone for breaking breaking standard protocol, when each piece of software is essentially designing something new. I heart surgeon doesn't invent a new heart procedure with each patient... By definition in software, everythin
Same place as always... (Score:2)
The idea of making Microsoft pay for the billions of dollars of damage [zdnet.com] caused by flaws in its products is certainly attractive, but where would this idea leave free software coders [linuxjournal.com]?
Probably the same place as always, ie, "you get what you pay for". If the users don't pay you, they can't reasonably expect anything from you. Well, maybe they could if you were to tell them that it would work (but who does that anyway), IIRC there tend to be rules about when people are harmed by relying on something you told them?
This isn't a way to make software better.... (Score:2, Insightful)
Re: (Score:2)
This is usual in big indrusties tho. For example banks are not allowed to be operate without certain level of financial ability, and I remember there just lately being news about US gov ordering some banks to increase their financial ability if they want to continue operating.
Computer industry has become a huge industry aswell, specially companies like Microsoft who almost everyone are using(*except who use linux/freebsd/etc only, but thats still a minority)
Re: (Score:2)
The word: Purchase (Score:5, Insightful)
When you buy software, for example a Linux distribution, you may expect that the distributor has tested the packages and that the software mostly works. Because you pay more for MacOS, you may just expect MacOS to work better.
Off course there has to come jurisprudence on all this, but I don't think that finding just one bug will entitle you to your money back. However, when the software won't work at all for you, the supplier can not hide behind EULAs and could be forced to compensate your damages... It will be a case-by-case balancing of responsibilities.
Re: (Score:3, Insightful)
Most EUropean countries have clauses in their laws that instruct the judge to take the price of the good into account when considering what would be a reasonable quality for a product. A corollary of that is when you give something away for free, the expected quality level is something like "not known harmful".
This is consumer protection law, not civil damages. The biggest practical upshot of this would be that if you buy a piece of software and it turns out not to be "fit for purpose", you have the right to a refund and maybe compensation for the cost of post and packing to return it. This is obviously moot if you downloaded the product for free.
Your point about price might, however, come into play if I bought a cheap Linux CD and wanted my money back because the Minesweeper implementation wasn't quite up to s
Licensing and Accredidation (Score:4, Insightful)
If the software is developed by professional developers with licenses, it gets a big seal on it, and then people can choose to buy it or not based on the rep of the licensing body, and their risk tolerance.
Re: (Score:2)
Re: (Score:2)
You can license the developers, but when management pressures them to cut corners you still have shoddy software.
I suppose that all depends on what the effect of losing one's software development license is. If a doctor, lawyer or engineer cuts corners and loses their certified status because of it, they might find themselves unable to get another job with equal pay, status & benefits.
If the penalty for cutting corners and losing your license is high enough, you'd eventually develop a culture where pushing a developer to knowingly do bad work is just as unacceptable as it is for any other certified profession.
Of
Two versions (Score:2, Insightful)
The result will be two versions of software. One will be priced the same as today, with a detailed license agreement with you ultimately giving up those rights and a second version that sells for a million dollars a copy with those rights.
Re: (Score:3, Insightful)
The result will be two versions of software. One will be priced the same as today, with a detailed license agreement with you ultimately giving up those rights
The purpose of the law would be to prevent license agreements taking those rights away. You already have them by default anyway (google "implied warranty of merchantability").
If it is free, you aren't liable (Score:2)
I think that is pretty obvious. The only time you would be liable is if you make a promise of some sort whether explicitly or implicitly. If it is free software and you offer to support it for money, you are also liable for your services... that's an ugly grey area. But the very notion that someone should be able to impose BSA tactics against your business while at the same time not be held liable for flaws in the product they are protecting with such tactics is pretty uneven. The "Because we say so" li
It is all in the license.... (Score:2)
Re: (Score:3, Interesting)
Sure it's all in the license at the moment. The question is whether we as a society are happy that these are valid licenses.
We don't let doctors do surgery with the EULA-like conditions that "anything they do is at the users own risk and the doctor isn't held to any standards."
We don't let engineers build bridges with the EULA-like conditions that "the bridge is delivered as is and people drive over it at their own risk."
Why do we allow software to get away with such a cowboy attitude when we're more rigoro
Re: (Score:2)
Why do we allow software to get away with such a cowboy attitude when we're more rigorous about other important infrastructure?
Because they were built by humans for known variables. When I write a piece of software, say, in Python, I know it will work on my version of Python, however, the build of Python two weeks from now, or two weeks previously may not run it at all. If its a low level program, I can't be 100% sure that the next version of the kernel will be able to run it.
There are so many variables that it is impossible to test them all. Add that in with patches that need to be hurriedly released to patch certain vulnera
Why would this affect free software coders? (Score:2)
I get that free as in beer != free as in speech, but there is a pretty high correlation, and really this article is trying to imply that if I give software away for free as in beer I can be liable to the person who "purchased" my software license. Are they really trying to suggest that the ubiquitous line in almost every free as in beer software along th
The Number of Uses (Score:2)
The problem with guaranteeing software is the number of uses that it can have and the number of different environments it can be used in.
Well, it's not necessarily a problem of software. If we look at the PlayStation/Wii/Xbox model, there is the potential to offer a guarantee there. Users are really only allowed to run things certified for the platform, one at a time, etc. That makes it at least *possible* to create a guarantee.
The problem with computers is that it is impossible to create a guarantee lik
The article is "scareware" (Score:2)
The proposal is to give licensees the same kind of protections as buyers, to close off the scam of "licensing" a product with more restrictions than allowed when selling it.
The writer just wanted to get more attention, so he puffed it up with an imaginary threat to developers.
--dave
I would say: (Score:2)
Yes, when the consumer pays for a service, like providing an tested Software, where the distibutor promises a certain function, several thing should happen
a) A distributor should have mandatory documented testing standards, where the documentation is public to the users (before buying).
b) These testing Standards should be formulated in terms of an ISO norm. E.g. Tests, source code review, etc. should be formulated as clear statements.
c) There should be a simple label system classifying highly speacialized (
Re: (Score:2)
It's time for software to grow up (Score:2)
It's time for software to grow up.
I proposed this in 2000 as a penalty for Microsoft in their antitrust trial. [animats.com] That would have been a big step forward.
The claim that "the vendor doesn't know the environment in which the software will be used" is bogus. Car companies have no idea where you will drive your car, or on what kind of roads. They have a far worse problem than any software maker. Yet they have to accept serious liability obligations.
Provided that this is implemented as a constraint on comme
Re: (Score:2)
Good idea (Score:2)
They should make the maximum penalty be that if you have a problem with the software, you are legally allowed a full refund of the purchase price, and the right to full access of the source code.
Imagine what that would do to Microsoft and the Open Source communities respectively.
Warranties of Fitness and Merchantability (Score:2)
There are laws on the books for this already.
They are called implied warranties of fitness and merchantability.
In most states in the U.S., these warranties can only be waived under certain conditions so software licenses don't necessarily absolve mfrs and merchants of responsibility.
Basic info:
http://en.wikipedia.org/wiki/Implied_warranty [wikipedia.org]
I guess that the reason this is newsworthy is that EU directives harmonize European laws, which are presently quite diverse on the matter.
Depends on what you call 'damages' (Score:2)
If you cant get your taxes e-filed due to a crash, its no different then not being able to get to the post-office due to your car not starting because of a defective battery.
Sure, you should be able to return/exchange the product as being defective but you don't get your IRS fine paid.
And we are talking consumer grade products here, if its specialized there should be some severe penalties if the product doesn't perform. ( such as a heart monitor for example )
Read what it says not what you want it to mean (Score:2)
but where would this idea leave free software coders?
From the same header:
licensing should guarantee consumers the same basic rights as when they purchase a good
When you obtain "FREE" software, you do not "PURCHASE" anything. The damages obviously do not apply - in a sane world.
The real concern is insurance rates (Score:2)
Nice idea, but... (Score:2)
The modern general purpose computer, even Macs, are very open products compared to typical consumer goods.
A CD player is a CD player. It has to work properly with itself, and CDs. Even componentized systems have a very limited environment within which they have to work. Precisely defined interfaces in and out, and they are limited in number.
A general purpose computer program though, is another beast entirely. There are thousands, if not millions, of other programs that they may have to coexist with. Mo
I dont think so (Score:2)
Once again the EU is not covered by US law (Score:2)
Unworkable (Score:3, Interesting)
This is an unworkable plan. Personal computers, by their very nature, require the end-user to tamper with them. The moment the end-user installs some 3rd-party software, or swaps out any piece of hardware, the environment the software runs under changes. This new environment will frequently produce a permutation that is impossible to predict and test against.
Additionally, many mainstream hardware manufacturers are TERRIBLE at producing hardware that conforms to the standards to which software developers target their code. Software developers can do everything right, but still see their programs malfunction due to circumstances beyond their control.
If this brain-damaged statute passes, the European Union will witness a steady exodus of consumer software, both closed and Open Source, from its member nations. There are just too many intermediaries between the software producer and software consumer to make this kind of liability feasible in any way, shape, or form. The price of even simple software would also rise to that of a small skyscraper, as a deluge of lawsuits would be filed by users for problems they caused themselves, but blamed on the software.
The cost to the European Union would be devastating.
Re:Where would this idea leave free software coder (Score:5, Funny)
Going to medical school.
umm... to avoid being sued?
Re: (Score:2)
'Going to medical school.'
Going to law school?
And while they're there, they could work towards drafting some sort of legal framework that guarantees 'consumers' of the European Commission's policies the same basic rights as those expected under other responsible authorities - e.g., the right not to have harmful copyright extension legislation imposed by an organization that 'wilfully ignores scientific analysis and evidence in its policy making process':
http://www.out-law.com/page-9378 [out-law.com]
Re: (Score:2)
Does this clear it up for you?
Re: (Score:2)
Constitution/International treaties > laws > government regulation > private contract > untested in court,
Could you site the case? Because I am fairly sure "the law of the land" doesn't make it on par with the Constitution. All laws passed by Congress are laws of the land. Unless it explicitly says that treaties have the power to modify the constitution, they don't have such power.
Re: (Score:2)
Re: (Score:2)
but I'm pretty sure that if a law and a treaty disagrees, the treaty is considered valid.
Actually, no, not in the US. For example, the UN charter was established through an international treaty. But US doesn't see UN proclamations, decisions, etc. as anything but advisory. Since US Congress (the legislature) has the power of the purse, all government expenses are appropriated by laws. US from time to time simply doesn't pay its UN dues. There is no recourse. If the treaty that established the UN charter were above the US law, there would be a way for the UN to recover the dues. But as lo
Re: (Score:3, Insightful)
If they pass a law to protect consumers tho, eula cannot go against it. Those parts in the EULA would be just as null.
Thats how it works in some countries in europe aswell. For example most eulas try to prohibit you from making *any* copies of the software/game, but laws state that you can make yourself personal copies. Law goes on top of EULA, and if they differ law always wins.
Re: (Score:3, Insightful)
However theres a little bit of difference on complexity on programming and constructing something (I know, constructing requires knowledge aswell, but not on so wide scale and on the same level of complexity)
Re: (Score:2, Insightful)
I am tired of these implicit assumptions that FOSS is better than proprietary/closed source. You assume that because you have an FOSS product that you automatically have more people testing your it.
A large company just released a RC for their new OS. It's a closed source and proprietary product and it's being tested for free by more people than your product is (admittedly). You should check it out.
Furthermore, open source only matters for testing when your testers are actually doing white box. Unless yo
Re: (Score:2)
Re: (Score:2)