3 ms·
No. Strict liability for third party software failure is not a good idea. Software gains much much more from the freedom to innovate than it loses from exploi
by nitrogen 11y ago
No. Strict liability for third party software failure is not a good idea. Software gains much much more from the freedom to innovate than it loses from exploits. Strict liability would be a terrible blow against basically everything HN represents.
- golergka 11y agoWell, there are areas where freedom to innovate is more important, and then there are areas where liability is more important. May be US (as de-facto main government-level actor in IT and internet) could create voluntary certification that opened up companies to such liabilities? Small startup operating from a garage — no certification necessary, but users are aware that no one is guaranteeing anything. IBM? Level A certification which they advertise everywhere, with billions of dollars in potential fines.
- ivl 11y agoIf it was voluntary, I doubt many of those companies would see it as worth the risk. The problem is that these errors happen because so many people are working on interdependent parts. Many times, it's not even your error that can make your software vulnerable. I dislike making anything so risky, because we'll see much, much less good software at the end of the day.
- ptaipale 11y agoPlus a culture of risk-avoidance, blame-shifting and bureaucracy-over-innovation. I even feel the breath of having Ada (the language) enforced over all of us again, and similar ideas... (Not that Ada is so bad as a language, it's more about the ideas of enforcement and top-down control...)