Now everyone wants to know how to solve the problem. If every developer needs to get a patent lawyer, it's going to be a big problem.
My suggested solution to the current software patent disaster:
Inventors have to demonstrate a solution (in source code and running) that covers "ALL" the claims. Earlier inventions, e.g. those from the last 17 years, that have not provided this by means of ending up in a product during this period are automatically revoked / declared invalid. Inventors can appeal against this (at cost increasing the older the patent is). Demonstrations within appeals are only possible with technology available at the date of filing.
This will automatically revoke all the fantasy patents (I call them Jules Verne Patents), bring sense back into patent filing - particularly when "pure front-end" patents are disqualified, and will help to protect us from the 1999/2000 patent litigation tsunami some are already expecting.
(Reg: 1999/2000 patent litigation tsunami - this could be caused by all those start-up companies that filed patents within the 1999/2000 bubble and then went belly-up - many of those patents might soon end up in patent troll litigation portfolios.)
Update: And patents should only be enforceable by practising entities vs. PAEs along the lines / to mitigate the issues that Google, Blackberry, Red Hat and Earthlink have outlined in their letter to the DOJ last Friday ( https://docs.google.com/file/d/0BwxyRPFduTN2VTE4TXlNcW9MR2s/... )
Problem is, the legislation to cover vague and broad patents may very well end up being vague and broad itself, unfortunately.
Plus, for some of the bigger companies you say chicken out, this is a potential winning strategy for them to stifle competition. The big companies have the funds to just settle and move on while the small companies that might pose a threat in the future may have a harder time dealing with even just a simple settlement.
I'd guess those must be the same sort of companies who engage in patent aggression themselves.
They are using claim 15 to sue over interactive chat: "A method, comprising: monitoring a product for an occurrence in the product of a trigger event of a predefined plurality of trigger events; incrementing a counter corresponding to the trigger event upon detection of the occurrence of the trigger event in the product; displaying a user interface, configured to probe for information regarding a use of the product, if the counter exceeds a threshold; storing an input received from the user interface on a device; and transmitting the input to a server. "