California Court: EULAs are Inapplicable in Some Cases

(outer-limits) writes "In a significant ruling in a California court, a judge has ruled the standard EULA licensing agreement to be invalid. This must be the biggest upset in software licensing ever. No more are we powerless End Users of software, having to agree to every restriction a software company makes (Expect an appeal on this, though)." Note that this is about the resale of bundled software, so it's not like EULAs are dead, but this ruling could have broad effects. Update: 02/12 03:45 GMT by J : Yeah, this is a repeat - sorry.

Comments

Good deal!

[GSloop]

The sale of software should in general, follow the rules and protections of a sale of goods.

This would prevent the slipping in of "contract" style wording, and the attendant need to have every software license reviewed by a lawyer. Sure, really wild terms in a software license might get thrown out in court, but that will take time and more importantly MONEY!

This is why UCITA is 3 or 4 or 100 times as bad as the current situation. UCITA allows all software to be contracts, and formalizes the legal standing, so contracts become the norm.

As a follow-up, I beleive that all software should also be subject to normal liability/tort law. If software doesn't do what it's supposed to do, and the vendor didn't take adequate care to ensure that it would, the vendor should be liable for damages.

I made this point a day or two ago, but again...
Sure, software might cost more to produce if it had to survive a "reasonable" test for correct function. But how much do the companies that employ us as consultants/help-desk people/network engineers, etc, spend having us chase bugs down that shouldn't have been there in the first place. Add that to the "cost" of the product, and you have the "real" cost. And I submit that it's way, WAY higher than most of us realize.

Until there's some real threat to shipping crappy software, the usual suspects will continue to "ship early, fix bugs later" if ever. Oh, and while you're at it, "add lots of fluff, and cool UI elements" (Does this remind anyone of Windows XP - a totally gross fluffy UI (my opinion) and a HUGE GAPING hole in security.) Adding some teeth to the legal system will give everyone a _chance_ to slow down and get things right. The shareholders will understand, the board of directors will understand etc.

Until we all require decent software that runs right, and a sale process that is fair, and understandable, we're going to continue to get screwed. UCITA and LONG LEGAL EULA's will always favor the software vendor. The court system may now be (finally) realizing that software isn't that much different than any other good, for example, shovels or cars or VCR's. These goods don't (AFAIK) have EULA's, and are subject to serious repercussions should they work incorrectly. Plus your ability to force the vendor to refund your money is much greater.

Repeat after me...
"Software just ain't that different from regular stuff we all use every day" In fact, software/firmware is in lots of devices, and we don't accept similar restrictions in their use...what about cell phones. Did you have to agree to a EULA to use it? Does it reboot/crash often? How about your VPR or Toaster or Car or Microwave?

Screw EULA's. Screw UCITA. They're both just ways to tip the balance of power WAY over to the manufacturer/seller. They don't offer any protections that a resonable seller needs.

Cheers

What does this mean to software hackers...

[ThomasMis]

I write software for companies so I can eat. On a contract I don't retain ownership of the code, I could usually care less. But I include a clause that says something to the effect that my software is good for no particular purpose and that if it breaks, I'm not liable. This is a good thing for small time guys like me. As I can't really afford to run to a lawyer all the time. But if that doesn't hold up anymore, am I going to face trouble when my call into a Win32 API hangs?? I call LPTRSomeWin32Function() in my software, it blows up and end user sees an error box pop up in the application that I wrote. Is the court going to tell me that I'm liable for broken software when the libraies I use that I didn't write cause the process to go boom?

I don't know... this is all food for thought. If I'm sued can I turn around and sue the developer of teh library? If I'm linking into glibc and it breaks can I sue GNU? Richard Stallman?