Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #67816
| From | Marko Rauhamaa <marko@pacujo.net> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: How security holes happen |
| Date | 2014-03-05 08:37 +0200 |
| Organization | A noiseless patient Spider |
| Message-ID | <871tyhp2vd.fsf@elektro.pacujo.net> (permalink) |
| References | (7 earlier) <mailman.7759.1393972610.18130.python-list@python.org> <87d2i1mvg7.fsf@elektro.pacujo.net> <mailman.7777.1393980007.18130.python-list@python.org> <roy-4E7DBB.20574304032014@news.panix.com> <mailman.7789.1393992721.18130.python-list@python.org> |
MRAB <python@mrabarnett.plus.com>: > Into how many versions did Lisp split in its first 23 years? :-) I'm partial to Scheme, but I'll take any version. If you had tried Python 30 years ago, you'd give it up for any serious work because it would be so slow and consume so much memory. C++ virtual functions used to be avoided because of performance reasons. These are truly amazing times for computing: Java, C#, Python etc are now mainstream, and advanced programming concepts like closures are available to and expected from run-of-the-mill code pushers. Java programmers were afflicted by XML and didn't know of anything better. They are now being exposed to Clojure. Python programmers are starting to see glimpses of a better world with ast.literal_eval(). So we are getting there. Give it a few more decades. Marko
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: How security holes happen Chris Kaynor <ckaynor@zindagigames.com> - 2014-03-03 14:55 -0800
Re: How security holes happen sffjunkie@gmail.com - 2014-03-04 08:41 -0800
Re: How security holes happen Chris Angelico <rosuav@gmail.com> - 2014-03-05 04:07 +1100
Re: How security holes happen Skip Montanaro <skip@pobox.com> - 2014-03-04 11:16 -0600
Re: How security holes happen Ned Batchelder <ned@nedbatchelder.com> - 2014-03-04 15:47 -0500
Re: How security holes happen Ethan Furman <ethan@stoneleaf.us> - 2014-03-04 13:49 -0800
Re: How security holes happen Marko Rauhamaa <marko@pacujo.net> - 2014-03-05 00:48 +0200
Re: How security holes happen Chris Angelico <rosuav@gmail.com> - 2014-03-05 09:57 +1100
Re: How security holes happen Roy Smith <roy@panix.com> - 2014-03-04 17:59 -0500
Re: How security holes happen Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-03-04 23:16 +0000
Re: How security holes happen Chris Angelico <rosuav@gmail.com> - 2014-03-05 10:22 +1100
Re: How security holes happen Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-03-04 23:40 +0000
Re: How security holes happen Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-03-04 19:31 -0500
Re: How security holes happen Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-03-04 19:30 -0500
Re: How security holes happen Roy Smith <roy@panix.com> - 2014-03-04 20:57 -0500
Re: How security holes happen MRAB <python@mrabarnett.plus.com> - 2014-03-05 04:11 +0000
Re: How security holes happen Marko Rauhamaa <marko@pacujo.net> - 2014-03-05 08:37 +0200
Re: How security holes happen Steven D'Aprano <steve@pearwood.info> - 2014-03-05 08:26 +0000
Re: How security holes happen Ben Finney <ben+python@benfinney.id.au> - 2014-03-05 19:57 +1100
Re: How security holes happen Marko Rauhamaa <marko@pacujo.net> - 2014-03-05 11:01 +0200
Re: How security holes happen "Mark H. Harris" <harrismh777@gmail.com> - 2014-03-05 06:11 -0800
Re: How security holes happen Chris Angelico <rosuav@gmail.com> - 2014-03-06 02:16 +1100
Re: How security holes happen Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-03-05 19:24 -0500
Re: How security holes happen "Mark H. Harris" <harrismh777@gmail.com> - 2014-03-05 17:24 -0800
Re: How security holes happen MRAB <python@mrabarnett.plus.com> - 2014-03-06 01:40 +0000
Re: How security holes happen "Mark H. Harris" <harrismh777@gmail.com> - 2014-03-05 18:07 -0800
Re: How security holes happen Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-03-06 19:28 -0500
Re: How security holes happen "Mark H. Harris" <harrismh777@gmail.com> - 2014-03-06 17:53 -0800
Re: How security holes happen MRAB <python@mrabarnett.plus.com> - 2014-03-07 02:13 +0000
Re: How security holes happen "Mark H. Harris" <harrismh777@gmail.com> - 2014-03-06 18:39 -0800
Re: How security holes happen Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-03-07 19:46 -0500
Re: How security holes happen Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-03-07 19:43 -0500
Re: How security holes happen Neil Cerutti <neilc@norwich.edu> - 2014-03-05 14:19 +0000
Re: How security holes happen Marko Rauhamaa <marko@pacujo.net> - 2014-03-05 16:54 +0200
Re: How security holes happen Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-03-05 18:42 +0000
Re: How security holes happen Chris Angelico <rosuav@gmail.com> - 2014-03-06 06:00 +1100
Re: How security holes happen Grant Edwards <invalid@invalid.invalid> - 2014-03-05 15:28 +0000
Re: How security holes happen Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-03-05 15:47 +0000
Re: How security holes happen "Mark H. Harris" <harrismh777@gmail.com> - 2014-03-05 08:37 -0800
csiph-web