Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #77293
| References | <mailman.13604.1409316126.18130.python-list@python.org> <roy-AE646E.10535529082014@news.panix.com> <CANc-5UxEY4XgmoiNa5MR=1Hy8SeRtpr1r=rRjBFKw2RrxFNomQ@mail.gmail.com> <5400CE4C.8080209@stoneleaf.us> |
|---|---|
| Date | 2014-08-30 08:38 +1000 |
| Subject | Re: suckitude classifications [was Re: Keeping python code and database in sync] |
| From | Chris Angelico <rosuav@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.13623.1409351910.18130.python-list@python.org> (permalink) |
On Sat, Aug 30, 2014 at 5:02 AM, Ethan Furman <ethan@stoneleaf.us> wrote: > Speaking of suckitude, we could classify technologies that way: > > xml: major suckitude > > rpc: no suckitude > > python: negative suckitude I disagree with your last two qualifications. RPC still sucks, just not as much as some things do. And your last statement implies that Python actually fixes other problems, which violates one of the fundamental laws of physics: the Law of Conservation of Suckitude and Frustration. It's possible to reduce suckitude in one system by shifting it to another system, and it's possible to overall reduce suckitude in the universe by engaging in a very frustrating job, but merely combining two entities cannot actively reduce suckitude. Of course, sometimes you can wrap the suckitude up in another layer, thus reducing *apparent* suckitude, and this can make a system safer to use; but maintenance on the wrapper layer will reveal that nothing has been destroyed. Hello, Polly! ChrisA
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Keeping python code and database in sync "Frank Millman" <frank@chagford.com> - 2014-08-29 14:42 +0200
Re: Keeping python code and database in sync Rustom Mody <rustompmody@gmail.com> - 2014-08-29 05:55 -0700
Re: Keeping python code and database in sync "Frank Millman" <frank@chagford.com> - 2014-08-29 15:19 +0200
Re: Keeping python code and database in sync Roy Smith <roy@panix.com> - 2014-08-29 10:54 -0400
Re: Keeping python code and database in sync Skip Montanaro <skip@pobox.com> - 2014-08-29 12:04 -0500
suckitude classifications [was Re: Keeping python code and database in sync] Ethan Furman <ethan@stoneleaf.us> - 2014-08-29 12:02 -0700
Re: Keeping python code and database in sync Ben Finney <ben+python@benfinney.id.au> - 2014-08-30 06:34 +1000
Re: Keeping python code and database in sync Chris Angelico <rosuav@gmail.com> - 2014-08-30 08:31 +1000
Re: suckitude classifications [was Re: Keeping python code and database in sync] Chris Angelico <rosuav@gmail.com> - 2014-08-30 08:38 +1000
Re: suckitude classifications [was Re: Keeping python code and database in sync] Roy Smith <roy@panix.com> - 2014-08-29 19:19 -0400
Re: suckitude classifications [was Re: Keeping python code and database in sync] Chris Angelico <rosuav@gmail.com> - 2014-08-30 09:38 +1000
Re: Keeping python code and database in sync Skip Montanaro <skip.montanaro@gmail.com> - 2014-08-29 18:47 -0500
Re: Keeping python code and database in sync Ethan Furman <ethan@stoneleaf.us> - 2014-08-29 16:54 -0700
Re: Keeping python code and database in sync Skip Montanaro <skip@pobox.com> - 2014-08-29 21:14 -0500
Re: Keeping python code and database in sync Chris Angelico <rosuav@gmail.com> - 2014-08-30 12:28 +1000
Re: suckitude classifications {taken to absurdity} Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-08-30 11:13 -0400
csiph-web