Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #43479
| References | (9 earlier) <CAPTjJmqxns1dDbHVvu7_T7Zxf_UROcWnhxWWctaaAsRndVTy9g@mail.gmail.com> <mailman.321.1365492029.3114.python-list@python.org> <5163c578$0$29977$c3e8da3$5496439d@news.astraweb.com> <CAMjeLr9rT+BgCq=ag8VpEy6OrGy-JN2mjaLcLWQ6aRsLcHDvDg@mail.gmail.com> <5B80DD153D7D744689F57F4FB69AF474182F6BDD@SCACMX008.exchad.jpmchase.net> |
|---|---|
| Date | 2013-04-12 12:57 -0700 |
| Subject | Re: im.py: a python communications tool |
| From | Mark Janssen <dreamingforward@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.534.1365796686.3114.python-list@python.org> (permalink) |
On Fri, Apr 12, 2013 at 12:46 PM, Prasad, Ramit <ramit.prasad@jpmorgan.com> wrote: > Mark Janssen wrote: >> But you see, there's the critical difference. First of all you're >> making two errors in your comparison. Firstly, a *person* is saying >> that she's going to *do something for you*. She's making a promise. >> If I put a piece of software online -- you're taking it! That's #1 >> (!) > > Theoretically isn't putting a piece of software "online" akin to > publishing it? Following that logic, then there is the possibility > of arguing an implicit promise that the software does what it is > supposed to. Any bugs would be the responsibility of the developer. It is akin to publishing it. The law has not made a good distinction about responsibility in this area. But I'm telling you that unless money is exchanged THERE IS NO AGREEMENT MADE, implicit or otherwise. If there is no agreement, then another party can't blame you for something you didn't promise. Otherwise, I can blame you for insulting my fashion sense. > On a separate note, even if the judgment supports your view > and the developer is never responsible for damages, will you > still not be responsible for any court/lawyer fees? If someone brings you to court and fails to make their case, they've inconvenienced everyone. The fair thing would be for the court to require them to pay for your fees. >And > getting those fees paid by suitor will likely be another court case. Possibily, but don't accept this view of the legal system. Judges can be quite reasonable. They don't want more time taken for bullshit cases and would much prefer for things to be settled (that is what their duty is -- to settle matters, not to make lawyers wealthy). Mark
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
im.py: a python communications tool Jake D <jhunter.dunefsky@gmail.com> - 2013-04-05 17:16 -0700
Re: im.py: a python communications tool Demian Brecht <demianbrecht@gmail.com> - 2013-04-05 17:52 -0700
Re: im.py: a python communications tool Jake D <jhunter.dunefsky@gmail.com> - 2013-04-06 08:35 -0700
Re: im.py: a python communications tool Roy Smith <roy@panix.com> - 2013-04-05 21:07 -0400
Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-05 18:13 -0700
Re: im.py: a python communications tool Andrew Berg <bahamutzero8825@gmail.com> - 2013-04-05 20:26 -0500
Re: im.py: a python communications tool Jake D <jhunter.dunefsky@gmail.com> - 2013-04-06 07:54 -0700
Re: im.py: a python communications tool garabik-news-2005-05@kassiopeia.juls.savba.sk - 2013-04-07 08:59 +0000
Re: im.py: a python communications tool jhunter.dunefsky@gmail.com - 2013-04-07 14:47 -0700
Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-07 22:36 +0000
Re: im.py: a python communications tool Chris Angelico <rosuav@gmail.com> - 2013-04-08 13:00 +1000
Re: im.py: a python communications tool Jake D <jhunter.dunefsky@gmail.com> - 2013-04-08 03:48 -0700
Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-08 16:16 -0700
Re: im.py: a python communications tool Dave Angel <davea@davea.name> - 2013-04-08 22:05 -0400
Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-08 20:37 -0700
Re: im.py: a python communications tool Dave Angel <davea@davea.name> - 2013-04-09 02:04 -0400
Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-08 23:20 -0700
Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 06:47 +0000
Re: im.py: a python communications tool Demian Brecht <demianbrecht@gmail.com> - 2013-04-08 23:42 -0700
Re: im.py: a python communications tool Dave Angel <davea@davea.name> - 2013-04-09 02:42 -0400
Re: im.py: a python communications tool Chris Angelico <rosuav@gmail.com> - 2013-04-09 17:14 +1000
Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 00:20 -0700
Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 07:38 +0000
Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 01:02 -0700
Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 09:08 +0000
Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 02:29 -0700
Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 13:05 +0000
Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-12 12:57 -0700
Re: im.py: a python communications tool Neil Cerutti <neilc@norwich.edu> - 2013-04-12 20:05 +0000
RE: im.py: a python communications tool "Prasad, Ramit" <ramit.prasad@jpmorgan.com> - 2013-04-12 21:48 +0000
RE: im.py: a python communications tool "Prasad, Ramit" <ramit.prasad@jpmorgan.com> - 2013-04-12 19:46 +0000
Re: im.py: a python communications tool Chris Angelico <rosuav@gmail.com> - 2013-04-09 17:21 +1000
Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 00:39 -0700
Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 08:31 +0000
Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 01:58 -0700
Re: im.py: a python communications tool Grant Edwards <invalid@invalid.invalid> - 2013-04-09 14:41 +0000
Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 09:36 -0700
Re: im.py: a python communications tool Chris Angelico <rosuav@gmail.com> - 2013-04-09 19:40 +1000
Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 13:03 +0000
Re: im.py: a python communications tool Chris Angelico <rosuav@gmail.com> - 2013-04-09 23:23 +1000
Re: im.py: a python communications tool Chris Angelico <rosuav@gmail.com> - 2013-04-09 19:48 +1000
Re: im.py: a python communications tool Jake D <jhunter.dunefsky@gmail.com> - 2013-04-09 04:09 -0700
Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 02:46 -0700
Re: im.py: a python communications tool Grant Edwards <invalid@invalid.invalid> - 2013-04-09 14:30 +0000
Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 01:15 -0700
Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 08:45 +0000
Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 02:00 -0700
Re: im.py: a python communications tool Dave Angel <davea@davea.name> - 2013-04-09 05:18 -0400
Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 02:32 -0700
Re: im.py: a python communications tool Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-04-09 17:10 +0100
csiph-web