I would point out that a complete disclaimer of liability is fairly common even in commercial relationships. Just now I downloaded my motherboard's manual, and had to click through a liability and fitness-for-purpose disclaimer. So, even someone selling you a $300 enterprise motherboard doesn't want to be responsible for ensuring *you* are using it in a sensible fashion.
- Dave On Sun, May 13, 2018 at 2:45 PM, Gerald Henriksen <ghenr...@gmail.com> wrote: > On Sun, 13 May 2018 13:01:46 -0700 (PDT), you wrote: > > >I don't think this is the attitude behind GCC, or maybe it is. I want to > >write programs that do things worth money and hope to use Go or GCC to do > >so (including working with and on those projects for free), but if they > >might include unnecessary liability beyond regular bugs then that's a > >problem for me. > > I suspect you are worrying too much given both the long history of > open source software and the large number of > groups/organizations/companies that rely on it. > > But you aren't going to get much in the way of guarantees when you > receive and use something for free. > > If you really feel you need some sort of legal guarantee then I > suggest you look into some paid options that provide Go and/or GCC, > such as Red Hat or Ubuntu, where there may be more of a legal > framework that is more to your liking. > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
