Re: How security holes happen

Newsgroups	comp.lang.python
Date	2014-03-05 08:37 -0800
References	(6 earlier) <CANc-5Uzw703CBdWQOntoPDMtj6BaxrHNPyVC226ctVxhXgFO1Q@mail.gmail.com> <lf5e4d$lfm$1@ger.gmane.org> <mailman.7759.1393972610.18130.python-list@python.org> <87d2i1mvg7.fsf@elektro.pacujo.net> <5317471b$0$29985$c3e8da3$5496439d@news.astraweb.com>
Message-ID	<faab1e96-4183-4e11-9526-29cded7bcd96@googlegroups.com> (permalink)
Subject	Re: How security holes happen
From	"Mark H. Harris" <harrismh777@gmail.com>

Show all headers | View raw

On Wednesday, March 5, 2014 9:47:40 AM UTC-6, Steven D'Aprano wrote:

> Seriously, Lisp is not only one of the oldest high-level languages 
> around, being almost as old as Fortran and Cobol, but it was one of the  
> biggest languages of the 1970s and even into the 80s. 

Lisp was specified by John McCarthy (of Berkeley, CA) in 1958.  It is the second
oldest computer language behind Fortran, by one year.

There is a resurgence of interest in Lisp today (yes, not so much for common lisp) 
in the Scheme arena. The irony for AI today is that we are finally at the point 
where the technology can finally do what Alonzo Church and Alan Turing dreamed 
about. John McCarthy was *way* ahead of his time too. We are at the point where 
we are wondering again if computer science & technology in software engineering
will ever generate a "thinking" entity---self aware, creative, and of course able to
generate on it's own, "Cogito ergo sum"> 

Lisp/Scheme is awesome. But, if I want to have my little 'ol puter do some real work,
up comes IDLE and out comes a script in a couple of hours that's "awesome"!  
I still play around with gnu emacs and lisp. Its fun, educational, and truly enriching
beyond words. Check out the site, "Lambda the Ultimate" sometime:

http://lambda-the-ultimate.org/

marcus

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

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