Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.lisp > #32950

Re: Buffer Overflow in LISP

Newsgroups comp.lang.lisp
Date 2019-05-24 10:40 -0700
References (1 earlier) <m2a7gez0d0.fsf@despina.home> <barmar-6B8998.11044625042019@reader443.eternal-september.org> <m21s1qyp7t.fsf@despina.home> <240eddc7-e436-40a6-9099-52cabdfcf163@googlegroups.com> <m2h89l3wpc.fsf@despina.home>
Message-ID <d4d07459-b2f8-4abb-858e-e979ac91e8fe@googlegroups.com> (permalink)
Subject Re: Buffer Overflow in LISP
From taruss@google.com

Show all headers | View raw


On Thursday, May 23, 2019 at 10:30:28 AM UTC-7, informatimago wrote:
> 
> Certainly a better metric would be in order. But in anycase, by
> definition there will be fewer multi-user computers than single-user
> computers.

I might quibble that this is not necessarily axiomatic.
Certainly in the early history of computing there were more multi-user
computers. But enough of pedantry. Especially if you count smart phones
as computers.

> The business value of companies like Google is in reducing the number of
> computers they need to use to serve the 7 billion potential users.
> 
> The business value of companies like Apple or Samsung is to increase the
> number of hand-held computers the sell to the 7 billion potential users.
> 
> Apple will never make a iUberPhone!  "Press a button, and some random
> iPhone will be brought to your position in less than five minutes so you
> make your call or send you tweet!"  Anybody?

This sounds like a great premise for an April 1st post. Especially since
one could work autonomous drone delivery of the phones into it. Maybe
I'll try writing that next year...

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


Thread

Buffer Overflow in LISP yara.huss.113@gmail.com - 2019-04-25 03:52 -0700
  Re: Buffer Overflow in LISP shcv@sdf.org - 2019-04-25 09:21 -0400
  Re: Buffer Overflow in LISP "Pascal J. Bourguignon" <pjb@informatimago.com> - 2019-04-25 15:21 +0200
    Re: Buffer Overflow in LISP Barry Margolin <barmar@alum.mit.edu> - 2019-04-25 11:04 -0400
      Re: Buffer Overflow in LISP "Pascal J. Bourguignon" <pjb@informatimago.com> - 2019-04-25 19:22 +0200
        Re: Buffer Overflow in LISP Spiros Bousbouras <spibou@gmail.com> - 2019-04-28 08:34 +0000
          Re: Buffer Overflow in LISP Barry Margolin <barmar@alum.mit.edu> - 2019-04-29 12:31 -0400
        Re: Buffer Overflow in LISP a.daniel.eliason@gmail.com - 2019-05-23 08:35 -0700
          Re: Buffer Overflow in LISP Kaz Kylheku <847-115-0292@kylheku.com> - 2019-05-23 17:02 +0000
            Re: Buffer Overflow in LISP Stefan Monnier <monnier@iro.umontreal.ca> - 2019-05-30 15:50 -0400
          Re: Buffer Overflow in LISP "Pascal J. Bourguignon" <pjb@informatimago.com> - 2019-05-23 19:30 +0200
            Re: Buffer Overflow in LISP taruss@google.com - 2019-05-24 10:40 -0700
              Re: Buffer Overflow in LISP Paul Rubin <no.email@nospam.invalid> - 2019-05-24 10:45 -0700
                Re: Buffer Overflow in LISP "Pascal J. Bourguignon" <pjb@informatimago.com> - 2019-05-24 23:27 +0200
                [OT] was: Buffer Overflow in LISP Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-05-24 22:46 +0100
                Re: [OT] was: Buffer Overflow in LISP "Pascal J. Bourguignon" <pjb@informatimago.com> - 2019-05-25 01:00 +0200
                Re: [OT] was: Buffer Overflow in LISP Kaz Kylheku <847-115-0292@kylheku.com> - 2019-05-24 23:46 +0000
                Re: [OT] was: Buffer Overflow in LISP Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-05-25 01:35 +0100
                Re: Buffer Overflow in LISP Jason Cornez <jcornez@ravenpack.com> - 2019-05-29 16:10 +0200
                Re: Buffer Overflow in LISP "Pascal J. Bourguignon" <pjb@informatimago.com> - 2019-05-29 20:25 +0200
      Re: Buffer Overflow in LISP Vladimir Sedach <vsedach@oneofus.la> - 2019-09-22 21:26 -0700
        Re: Buffer Overflow in LISP Barry Margolin <barmar@alum.mit.edu> - 2019-09-23 00:45 -0400

csiph-web