3 ms·
> What if e.g. github reframed its project sponsorship model as something that involved getting maintainers setup with liability insurance and the ability to of
by luckylion 6y ago
> What if e.g. github reframed its project sponsorship model as something that involved getting maintainers setup with liability insurance and the ability to offer sponsors warranty and liability for their software.
I think it would be much more expensive. The developers of some library are having a hard time judging how much money somebody stakes on that library working perfectly. It might be that they'd lose an hour of work if they hit a bug, it might also be that a huge project fails with gigantic losses - it's hard to insure against that if you still want people to be able to afford it.
It's much easier to buy insurance on the user side where you know the potential impact (i.e. "my wordpress site will be offline for a day" vs "the oil rig I've run calculations for could sink if there was a bug").
- tibbetts 6y agoScaling the payment with the importance of the software is already how enterprise software largely works. Often times customers actively want to pay more for software so they can secure more attention from the vendor, if the software is critical to their business.
- m000 6y agoIt's not only about a legit project failing with gigantic losses. A blanket liability insurance would also raise hordes of liability insurance trolls. I.e. organized efforts to collect insurance payments by claiming damage caused by the use of the software.
- dcow 6y agoThis just sounds like any mature industry.