Re: software situation

From	Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com>
Newsgroups	sci.electronics.design
Subject	Re: software situation
Date	2026-03-27 17:57 +0000
Organization	To protect and to server
Message-ID	<10q6gf3$25egd$1@paganini.bofh.team> (permalink)
References	<hssask1jni4460b638qcdm4bumb47jvbc4@4ax.com> <18a098629788bab0$85$2674190$4286dcd3@news.newsgroupdirect.com> <oh7dsk5104ubn6dbbi0nq348scg42esevi@4ax.com> <sr8dsk5p0h84u44be7iniv2o74c6kigeha@4ax.com>

Show all headers | View raw

Jeff Liebermann <jeffl@cruzio.com> wrote:
|-----------------------------------------------------------------------|
|"Never mind that the experts and the consensus are often wrong:        |
|<https://www.learnbydestroying.com/jeffl/crud/Premature-Judgement.txt>"|
|-----------------------------------------------------------------------|

Thanks for that stimulating text file but its end has an unproven
consensus about Gates:
""640K ought to be enough for anybody." 
   -- Bill Gates, 1981".
I never see this Gates purported quotation in its original (and I saw
a misquotation alleging that he said 16K!). During an old decade I
once read this insightful counterargument arguing that Gates never
actually says "640K ought to be enough for anybody." i.e. that if so
many persons claim that he had said so, then someone should be able to
show this original publication by Gates instead of hearsay. Did Gates
really ever say "640K ought to be enough for anybody."?
(S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)

Back to sci.electronics.design | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

software situation john larkin <jl@glen--canyon.com> - 2026-03-26 10:58 -0700
  Re: software situation Sergey Kubushyn <ksi@koi8.net> - 2026-03-26 20:29 +0000
    Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-26 17:51 -0700
      Re: software situation Sergey Kubushyn <ksi@koi8.net> - 2026-03-27 02:03 +0000
        Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-26 21:41 -0700
          Re: software situation Sergey Kubushyn <ksi@koi8.net> - 2026-03-27 06:09 +0000
            Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-27 04:15 -0700
          Re: software situation Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-03-27 10:07 +0000
            Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-27 05:37 -0700
              Re: software situation Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-03-27 18:24 +0000
                Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-27 12:04 -0700
                Re: software situation Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-03-27 22:35 +0000
                Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-27 15:58 -0700
                Re: software situation Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-03-29 09:24 +0000
        Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-27 10:00 -0700
          Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-27 10:17 -0700
            Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-27 10:32 -0700
              Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-27 11:22 -0700
              Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-27 11:34 -0700
                Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-28 06:41 -0700
                Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-28 13:56 -0700
                Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-29 05:53 -0700
                Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-29 12:39 -0700
                Re: software situation john larkin <jl@glen--canyon.com> - 2026-03-29 13:13 -0700
                Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-29 14:29 -0700
                Re: software situation john larkin <jl@glen--canyon.com> - 2026-03-29 15:24 -0700
                Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-29 20:54 -0700
                Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-29 21:07 -0700
                Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-29 21:16 -0700
                Re: software situation john larkin <jl@glen--canyon.com> - 2026-03-30 07:44 -0700
                Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-30 09:02 -0700
                Re: software situation john larkin <jl@glen--canyon.com> - 2026-03-30 16:00 -0700
                Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-29 17:09 -0700
                Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-29 20:48 -0700
              Re: software situation Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-03-27 21:38 +0000
      Re: software situation someone <cffbf4deb9142bce48974efc0e64dede@example.com> - 2026-03-27 04:30 +0000
      Re: software situation Joerg <news@analogconsultants.com> - 2026-03-27 10:35 -0700
        Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-27 11:27 -0700
          Re: software situation Joerg <news@analogconsultants.com> - 2026-03-27 11:46 -0700
            Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-27 14:54 -0700
  Re: software situation someone <cffbf4deb9142bce48974efc0e64dede@example.com> - 2026-03-27 04:30 +0000
    Re: software situation Jeff Liebermann <jeffl@cruzio.com> - 2026-03-27 07:41 -0700
      Re: software situation Jeff Liebermann <jeffl@cruzio.com> - 2026-03-27 16:04 -0700
      Re: software situation someone <cffbf4deb9142bce48974efc0e64dede@example.com> - 2026-03-30 23:30 +0000
        Re: software situation john larkin <jl@glen--canyon.com> - 2026-03-31 11:01 -0700
          Re: software situation Jeff Liebermann <jeffl@cruzio.com> - 2026-03-31 13:54 -0700
            Re: software situation john larkin <jl@glen--canyon.com> - 2026-03-31 15:06 -0700
              Re: software situation Jeff Liebermann <jeffl@cruzio.com> - 2026-03-31 16:14 -0700
                Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-31 16:43 -0700
                Re: software situation Jan Panteltje <alien@comet.invalid> - 2026-04-01 06:41 +0000
                Re: software situation john larkin <jl@glen--canyon.com> - 2026-04-01 00:49 -0700
                Re: software situation Jeff Liebermann <jeffl@cruzio.com> - 2026-04-01 17:39 -0700
        Re: software situation Jeff Liebermann <jeffl@cruzio.com> - 2026-03-31 14:15 -0700
          Re: software situation Jan Panteltje <alien@comet.invalid> - 2026-04-01 06:45 +0000
            Re: software situation Jeff Liebermann <jeffl@cruzio.com> - 2026-04-01 09:11 -0700
              Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-04-01 09:43 -0700
              Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-04-01 10:35 -0700
    Re: software situation john larkin <jl@glen--canyon.com> - 2026-03-27 08:16 -0700
      Re: software situation Jeff Liebermann <jeffl@cruzio.com> - 2026-03-27 09:01 -0700
        Re: software situation Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-03-27 17:57 +0000
          Re: software situation Jeff Liebermann <jeffl@cruzio.com> - 2026-03-27 15:06 -0700
            Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-27 15:48 -0700
            Re: software situation Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-03-28 00:44 +0000
      Re: software situation someone <cffbf4deb9142bce48974efc0e64dede@example.com> - 2026-03-30 23:30 +0000
  Re: software situation Jan Panteltje <alien@comet.invalid> - 2026-03-27 08:03 +0000
  Re: software situation someone <cffbf4deb9142bce48974efc0e64dede@example.com> - 2026-03-30 23:30 +0000

csiph-web