3 ms·
> Do you want software to stop being shit? Then stop expecting... nay, stop demanding that software be shit. As I've written before, it's almost entirely about
by davidw 12y ago
> Do you want software to stop being shit? Then stop expecting... nay, stop demanding that software be shit.
As I've written before, it's almost entirely about the economics of it. For tons of software out there, there is simply no incentive to make it super stable, polished, secure, etc.
In other words: let's say you're building a web app for a small local business. Are you going to build it in Erlang, run it on several physical machines and do all the other fault-tollerant, high-availability stuff, or are you going to put together some pieces of Rails or PHP or Django and call it 'pretty good'? You're going to do the latter, because otherwise you're going to cost a lot more than the competition, deliver less, and in any case the guy running the business is going to be understanding if you need to take the site down for an hour on Sunday morning to upgrade something once in a while.
So far, so good. Security is a bit more problematic, because there can be some pretty serious financial ramifications. The trick is to get the people who bear those risks to pay some of what it costs to produce better software, which is not always easy in the case of open source.
- _delirium 12y agoI've long thought that the different liability regime is a big part of that. In just about any business that is not software, it's much harder for a commercial vendor to completely disclaim all liability via a boilerplate contract. At the very least some basic liability attaches when you ship a seriously defective product: if it's not even remotely fit for the advertised purpose, has failure modes bad enough to be negligent, etc. But the way the existing doctrines have been applied to the software: 1) are quite deferential to EULAs; and 2) de-facto raise the bar for "negligence" to something approaching intentional malfeasance or fraud. (The economic effects of the different liability regime might be good or bad, but it's quite striking how doctrines that are well-understood in other areas are applied so differently to software.)
- davidw 12y agoThat's a good point, but I still think it's tricky: we're talking about OpenSSL here. Making contributors liable for defects in open source software would have some very, very negative effects: we would not even have an OpenSSL to complain about.
- VLM 12y agoAnd thats why some are pushing for it. I don't like what they're doing, but its not like they don't understand their own actions.
- x0x0 12y agoopenssl didn't ship to end users; it's the software that goes to end users that should bear liability
- davidw 12y agoThat's a pretty much impossible distinction to make.