On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over 3000
and they keep coming.
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed drivers >>>Not a Lisp fan then?
People love to invent weird computer languages. There are over 3000
and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap it that
way to read in a paper tape. It was a fun machine as it had a vector >graphics display so was very good for asteroids, but cheated at chess.
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed
drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over 3000
and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap it that
way to read in a paper tape. It was a fun machine as it had a vector graphics display so was very good for asteroids, but cheated at chess.
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed
drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over 3000
and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap it that
way to read in a paper tape. It was a fun machine as it had a vector graphics display so was very good for asteroids, but cheated at chess.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap it that way to
read in a paper tape. It was a fun machine as it had a vector graphics display
so was very good for asteroids, but cheated at chess.
On 06/11/2026 10:24, Martin Brown wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed
drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over 3000
and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap it that
way to read in a paper tape. It was a fun machine as it had a vector
graphics display so was very good for asteroids, but cheated at chess.
I think that machine had a moon lander game as well.
John
On 06/11/2026 11:25, John R Walliker wrote:
On 06/11/2026 10:24, Martin Brown wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed drivers >>>>>Not a Lisp fan then?
People love to invent weird computer languages. There are over 3000
and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap it that way >>> to read in a paper tape. It was a fun machine as it had a vector graphics >>> display so was very good for asteroids, but cheated at chess.
I think that machine had a moon lander game as well.
John
If that's the one I remember, you could successfully land if you plummeted till
you were 1 metre from the surface then burned all your fuel.
On 11/6/2026 8:00 AM, Simon Simple wrote:<https://www.wangmuseum.nl/wp-content/uploads/2021/01/wang360.jpg>
If that's the one I remember, you could successfully land if you plummeted >> till you were 1 metre from the surface then burned all your fuel.
I wrote one for our Wang, multiuser "programmable calculator" (with nixie displays!) in high school.-a Inspired by a BASIC game I had seen years earlier.
It was amusing as I created the various constraints without knowledge of whether or not you actually *could* land it!
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed drivers >>>Not a Lisp fan then?
People love to invent weird computer languages. There are over 3000
and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap it that
way to read in a paper tape. It was a fun machine as it had a vector >graphics display so was very good for asteroids, but cheated at chess.
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed drivers >>>>Not a Lisp fan then?
People love to invent weird computer languages. There are over 3000
and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap it that
way to read in a paper tape. It was a fun machine as it had a vector
graphics display so was very good for asteroids, but cheated at chess.
I did a lot of stuff in PDP-11 and 68K assembly languages. With a few
macros, they are almost higher-level languages.
Unlike some architectures that I might name.
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed drivers >>>>>Not a Lisp fan then?
People love to invent weird computer languages. There are over 3000
and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap it that
way to read in a paper tape. It was a fun machine as it had a vector
graphics display so was very good for asteroids, but cheated at chess.
I did a lot of stuff in PDP-11 and 68K assembly languages. With a few
macros, they are almost higher-level languages.
All high level languages get compiled into assembly language before than
can be run on a computer.
Being a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into something
that can be run on hardware (which will have an architecture - it is >constructed from components that have been connected by some kind of >architect).
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over 3000
and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap it that >>>> way to read in a paper tape. It was a fun machine as it had a vector
graphics display so was very good for asteroids, but cheated at chess.
I did a lot of stuff in PDP-11 and 68K assembly languages. With a few
macros, they are almost higher-level languages.
All high level languages get compiled into assembly language before they
can be run on a computer.
Well, no.
Being a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into something
that can be run on hardware (which will have an architecture - it is
constructed from components that have been connected by some kind of
architect).
If that post were compiled to assembly language, it would be a nop.
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:I did a lot of stuff in PDP-11 and 68K assembly languages. With a few
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over 3000 >>>>>> and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap it that >>>>> way to read in a paper tape. It was a fun machine as it had a vector >>>>> graphics display so was very good for asteroids, but cheated at chess. >>>>
macros, they are almost higher-level languages.
All high level languages get compiled into assembly language before they >>> can be run on a computer.
Well, no.
Counter-example?
Being a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into something
that can be run on hardware (which will have an architecture - it is
constructed from components that have been connected by some kind of
architect).
If that post were compiled to assembly language, it would be a nop.
As a compiler, you do seem to be sub-optimal, if not downright
afunctional. Ignoring implications you don't like isn't an option for a >compiler. There can be functions they can't parse - in your case don't
want to parse - but that doesn't generate a nop.
--
Bill Sloman, Sydney
On Sat, 7 Nov 2026 17:11:49 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:I did a lot of stuff in PDP-11 and 68K assembly languages. With a few >>>>> macros, they are almost higher-level languages.
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over 3000 >>>>>>> and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap it that >>>>>> way to read in a paper tape. It was a fun machine as it had a vector >>>>>> graphics display so was very good for asteroids, but cheated at chess. >>>>>
All high level languages get compiled into assembly language before they >>>> can be run on a computer.
Well, no.
Counter-example?
Interpreters.
Most Pythons
Tokeizers/threaded code compilers
The coolest case was probably the Burroughs systems
"AI Overview
Burroughs Corporation uniquely designed its computer systemsrComost
famously the Burroughs Large Systems starting with the B5000 in
1961rCoto run the ALGOL programming language natively rather than
assembler or Fortran."
Their Algol compiler made machine code directly and was written in
Algol! There was never any intermediate step.
Being a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into something >>>> that can be run on hardware (which will have an architecture - it is
constructed from components that have been connected by some kind of
architect).
If that post were compiled to assembly language, it would be a nop.
As a compiler, you do seem to be sub-optimal, if not downright
afunctional. Ignoring implications you don't like isn't an option for a
compiler. There can be functions they can't parse - in your case don't
want to parse - but that doesn't generate a nop.
I've written four RTOS's and three compilers. None of the compilers
generated intermediate assembly.
How about you?
On 8/11/2026 2:39 am, john larkin wrote:
On Sat, 7 Nov 2026 17:11:49 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:I did a lot of stuff in PDP-11 and 68K assembly languages. With a few >>>>>> macros, they are almost higher-level languages.
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over 3000 >>>>>>>> and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap it that >>>>>>> way to read in a paper tape. It was a fun machine as it had a vector >>>>>>> graphics display so was very good for asteroids, but cheated at chess. >>>>>>
All high level languages get compiled into assembly language before they >>>>> can be run on a computer.
Well, no.
Counter-example?
Interpreters.
An interpreter is just a line by line compiler.
Most Pythons
So you don't understand what's going on.
Tokeizers/threaded code compilers
So you don't understand what's going on.
The coolest case was probably the Burroughs systems
"AI Overview
Burroughs Corporation uniquely designed its computer systemsumost
famously the Burroughs Large Systems starting with the B5000 in
1961uto run the ALGOL programming language natively rather than
assembler or Fortran."
Their Algol compiler made machine code directly and was written in
Algol! There was never any intermediate step.
Being a compiler is tedious.
Borroughs had an Algol compiler, written in Algol. It was still a compiler.
Compiled code has more lines/commands/op codes than the code from which
is was compiled.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into something >>>>> that can be run on hardware (which will have an architecture - it is >>>>> constructed from components that have been connected by some kind of >>>>> architect).
If that post were compiled to assembly language, it would be a nop.
As a compiler, you do seem to be sub-optimal, if not downright
afunctional. Ignoring implications you don't like isn't an option for a
compiler. There can be functions they can't parse - in your case don't
want to parse - but that doesn't generate a nop.
I've written four RTOS's and three compilers. None of the compilers
generated intermediate assembly.
Who said anything about "intermediate assembler"?
The point about assembler is that it is human readable - groups of
letters rather than numerical op codes presented as strings of octal or >hexadecimal numbers. It is directly translatable into numerical opcodes
by a simple look-up table.
if you want to see what compiled code is actually doing it's usually
easier to understand what you get by running the look-up process backwards.
How about you?
Not my sphere of interest, even though I seem to have a better grasp of >what's involved than you do.
On Sun, 8 Nov 2026 15:44:12 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 8/11/2026 2:39 am, john larkin wrote:
On Sat, 7 Nov 2026 17:11:49 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:I did a lot of stuff in PDP-11 and 68K assembly languages. With a few >>>>>>> macros, they are almost higher-level languages.
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over 3000 >>>>>>>>> and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap it that >>>>>>>> way to read in a paper tape. It was a fun machine as it had a vector >>>>>>>> graphics display so was very good for asteroids, but cheated at chess. >>>>>>>
All high level languages get compiled into assembly language before they >>>>>> can be run on a computer.
Well, no.
Counter-example?
Interpreters.
An interpreter is just a line by line compiler.
Most Pythons
So you don't understand what's going on.
Tokeizers/threaded code compilers
So you don't understand what's going on.
The coolest case was probably the Burroughs systems
"AI Overview
Burroughs Corporation uniquely designed its computer systemsrComost
famously the Burroughs Large Systems starting with the B5000 in
1961rCoto run the ALGOL programming language natively rather than
assembler or Fortran."
Their Algol compiler made machine code directly and was written in
Algol! There was never any intermediate step.
Being a compiler is tedious.
Borroughs had an Algol compiler, written in Algol. It was still a compiler. >>
Compiled code has more lines/commands/op codes than the code from which
is was compiled.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into something >>>>>> that can be run on hardware (which will have an architecture - it is >>>>>> constructed from components that have been connected by some kind of >>>>>> architect).
If that post were compiled to assembly language, it would be a nop.
As a compiler, you do seem to be sub-optimal, if not downright
afunctional. Ignoring implications you don't like isn't an option for a >>>> compiler. There can be functions they can't parse - in your case don't >>>> want to parse - but that doesn't generate a nop.
I've written four RTOS's and three compilers. None of the compilers
generated intermediate assembly.
Who said anything about "intermediate assembler"?
The point about assembler is that it is human readable - groups of
letters rather than numerical op codes presented as strings of octal or
hexadecimal numbers. It is directly translatable into numerical opcodes
by a simple look-up table.
if you want to see what compiled code is actually doing it's usually
easier to understand what you get by running the look-up process backwards. >>
How about you?
Not my sphere of interest, even though I seem to have a better grasp of
what's involved than you do.
OK, what moron said
"All high level languages get compiled into assembly language before
than can be run on a computer."
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:I did a lot of stuff in PDP-11 and 68K assembly languages. With a few
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over 3000 >>>>>> and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap it that >>>>> way to read in a paper tape. It was a fun machine as it had a vector >>>>> graphics display so was very good for asteroids, but cheated at chess. >>>>
macros, they are almost higher-level languages.
All high level languages get compiled into assembly language before they >>> can be run on a computer.
Well, no.
Counter-example?
Being a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into something
that can be run on hardware (which will have an architecture - it is
constructed from components that have been connected by some kind of
architect).
If that post were compiled to assembly language, it would be a nop.
As a compiler, you do seem to be sub-optimal, if not downright
afunctional. Ignoring implications you don't like isn't an option for a compiler. There can be functions they can't parse - in your case don't
want to parse - but that doesn't generate a nop.
You clearly go into area were you are not an expert. Google a
bit about "undefined behaviour" in C and you will learn that
when source code makes no sense, then C compier can do
essentially anything, which in not so rare cases means that
compiler simply deletes what programmer wrote. Explicit nop-s
are rarely emited by compilers, but one can get 'return'
(if compiler decides that garbage source is doing nothing
useful, but it will eventually finish) or executing whatever
happens to be after deleted code (if compiler decides that
code should be never executed because it performed illegal
operation).
It is much nicer when you share things that you do know.
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:I did a lot of stuff in PDP-11 and 68K assembly languages. With a few >>>>> macros, they are almost higher-level languages.
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over 3000 >>>>>>> and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap it that >>>>>> way to read in a paper tape. It was a fun machine as it had a vector >>>>>> graphics display so was very good for asteroids, but cheated at chess. >>>>>
All high level languages get compiled into assembly language before they >>>> can be run on a computer.
Well, no.
Counter-example?
Being a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into something >>>> that can be run on hardware (which will have an architecture - it is
constructed from components that have been connected by some kind of
architect).
If that post were compiled to assembly language, it would be a nop.
As a compiler, you do seem to be sub-optimal, if not downright
afunctional. Ignoring implications you don't like isn't an option for a
compiler. There can be functions they can't parse - in your case don't
want to parse - but that doesn't generate a nop.
You clearly go into an area where you are not an expert.
Google a bit about "undefined behaviour" in C.
It is much nicer when you share things that you do know.
On 9/11/2026 6:27 am, Waldek Hebisch wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:I did a lot of stuff in PDP-11 and 68K assembly languages. With a few >>>>>> macros, they are almost higher-level languages.
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over 3000 >>>>>>>> and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap it that >>>>>>> way to read in a paper tape. It was a fun machine as it had a vector >>>>>>> graphics display so was very good for asteroids, but cheated at chess. >>>>>>
All high level languages get compiled into assembly language before they >>>>> can be run on a computer.
Well, no.
Counter-example?
Being a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into something >>>>> that can be run on hardware (which will have an architecture - it is >>>>> constructed from components that have been connected by some kind of >>>>> architect).
If that post were compiled to assembly language, it would be a nop.
As a compiler, you do seem to be sub-optimal, if not downright
afunctional. Ignoring implications you don't like isn't an option for a
compiler. There can be functions they can't parse - in your case don't
want to parse - but that doesn't generate a nop.
You clearly go into an area where you are not an expert.
I'm not pretending to be an expert, just less of a clueless newbie in
the area that John Larkin has shown himself to be.
Management of these processes is the cause of most bad designs.
The folks doing so are usually pretty ignorant of the efforts they
are charged with managing!
I don't make a habit of it, but there's no diplomatic way of getting the message across, when people are ignorant (which happens quite a lot), or stupid (which is rarer).
I was always struck by the typical senior managers password being so
weak that it was hardly worth having. Some of them even had it written
on a postit and stuck to their screen! You couldn't make it up!
What's amusing is all of these ideas are 50+ years old.-a Yet, people keep convincing themselves that they "need" more freedom... "constraints are
bad"
(as is the code they develop!)
On 10/30/2026 8:36 AM, JM wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed drivers
Not a Lisp fan then?
You don't need *strict* separation (e.g., like a Harvard architecture)
to benefit from this practice.-a If you can locate data/code on page boundaries and in page-sized units, you can commingle them freely.
But, the idea of treating memory as an amorphous gel that can be
freely molded is not going to work.
Nowadays, you actually need to put the different types of memories
in different *chips* if you truly want to maximize your protection
(you can gain some advantages with guard bands between regions but
the hardware has proven to easily exploitable in its efforts to
try to eke out more performance)
On 10/30/2026 11:47 PM, Don Y wrote:
On 10/30/2026 8:36 AM, JM wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed drivers >>>Not a Lisp fan then?
You don't need *strict* separation (e.g., like a Harvard architecture)
to benefit from this practice.-a If you can locate data/code on page
boundaries and in page-sized units, you can commingle them freely.
But, the idea of treating memory as an amorphous gel that can be
freely molded is not going to work.
Nowadays, you actually need to put the different types of memories
in different *chips* if you truly want to maximize your protection
(you can gain some advantages with guard bands between regions but
the hardware has proven to easily exploitable in its efforts to
try to eke out more performance)
I don't know any hardware manufacturer doing this -- well, I don't work
with military hardware so they could be doing it -- and now that Sam
Altman is gobbling up all the DRAM chips, I doubt we'll see this in end
user computers and phones any time soon.
So, is this a loss due to the 2026 DRAM shortage?-a Only speculative his- tory in the future will tell us.
On 10/30/2026 10:29 PM, Don Y wrote:
What's amusing is all of these ideas are 50+ years old.-a Yet, people keep >> convincing themselves that they "need" more freedom... "constraints are bad" >> (as is the code they develop!)
What is not amusing is that nobody thought to put computer security
education in the elementary schools fifty years ago.
And because the didn't do it then, they won't do it now -- is by obser- vation, their thinking.-a I don't know what goes on in the heads of peo-
ple who decide the elementary curriculum.-a Usefulness in life is not
their agenda.
Anyway, a /large/ part of the problem is that now that everyone uses computers, the computer security practices people should have been
taught in elementary school but weren't, don't work.-a Because they don't know them, and they don't know how real life organized criminals work.
Err, for an introduction to that, you could use the book /Undercover
Cop/ by Mike Russel and Patrick W. Picciarelli.-a It's an autobiography
of sorts, and therefore describes the real world, and not the fantasy
world in movies.-a You can then pair that knowledge with Nicole Perl-
roth's book /This Is How They Tell Me the World Ends/, for more real
world stories of computer security shenanigans.
Because if you don't know who the enemy is, and how he operates, how are
you going to secure your computer?-a With a ritual and magic smoke?
On 10/29/2026 8:59 PM, Don Y wrote:
Management of these processes is the cause of most bad designs.
The folks doing so are usually pretty ignorant of the efforts they
are charged with managing!
Please excuse me, I probably showed this example earlier this year in sci.electronics.design.-a A good example is
-a https://neilmadden.blog/2022/04/19/psychic-signatures-in-java/
where the /management/ was too lazy to hire a cryptographer for the pro- ject.-a It's not like you can accuse Oracle of not affording one.
On 11/9/2026 8:56 AM, Johann 'Myrkraverk' Oskarsson wrote:
On 10/30/2026 11:47 PM, Don Y wrote:
On 10/30/2026 8:36 AM, JM wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed
drivers
Not a Lisp fan then?
You don't need *strict* separation (e.g., like a Harvard architecture)
to benefit from this practice.-a If you can locate data/code on page
boundaries and in page-sized units, you can commingle them freely.
But, the idea of treating memory as an amorphous gel that can be
freely molded is not going to work.
Nowadays, you actually need to put the different types of memories
in different *chips* if you truly want to maximize your protection
(you can gain some advantages with guard bands between regions but
the hardware has proven to easily exploitable in its efforts to
try to eke out more performance)
I don't know any hardware manufacturer doing this -- well, I don't work
with military hardware so they could be doing it -- and now that Sam
Altman is gobbling up all the DRAM chips, I doubt we'll see this in end
user computers and phones any time soon.
You can often employ this technique in many of the larger SoCs.
sadly, the resources are often allocated by someone who doesn't
understand the VALUE of specific allocations.
E.g., if you put kernel memory in SRAM then "other memory"
being in LPDRAM has less potential -- via direct or side-channel
attack -- of corrupting it.
But, you have to be aware of the problem and understand how the
hardware works before you can make smart decisions about it.
Which, of course, means you have to have a firm hardware model
before you can sort out the software.
The hardware people are similarly clueless as they are usually not aware
of how the hardware will be used (and abused).-a They often treat
hardware as checkoff items:-a 2 serial ports; check.-a-a 3GB RAM; check.
1MB boot ROM; check.
One of the colossal FAILS IME was a hardware person putting a one-bit
latch to drive the input of a CVSD.-a So, the software had to sit in a
tight loop shifting bytes into the latch and clocking the CVSD.
And, of course, every path through the code had to have identical time
lest the clock frequency beat at the byte-rate.
Really?-a You couldn't put a byte-wide (parallel load, serial out)
SHIFT REGISTER there and have it self clocked so all the CPU has to
do is push BYTES at it every 8 bit times???-a You've traded a few pennies
for the entire CPU (because it can't do ANYTHING ELSE while caught
in this idiot loop).
Perhaps we should let hardware people write code and publicly
critique their failures?-a Or, let software people design the
hardware and let the hardware folks write the code??
So, is this a loss due to the 2026 DRAM shortage?-a Only speculative his-
tory in the future will tell us.
On 11/10/2026 1:42 AM, Don Y wrote:
On 11/9/2026 8:56 AM, Johann 'Myrkraverk' Oskarsson wrote:
On 10/30/2026 11:47 PM, Don Y wrote:
On 10/30/2026 8:36 AM, JM wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed drivers >>>>>Not a Lisp fan then?
You don't need *strict* separation (e.g., like a Harvard architecture) >>>> to benefit from this practice.-a If you can locate data/code on page
boundaries and in page-sized units, you can commingle them freely.
But, the idea of treating memory as an amorphous gel that can be
freely molded is not going to work.
Nowadays, you actually need to put the different types of memories
in different *chips* if you truly want to maximize your protection
(you can gain some advantages with guard bands between regions but
the hardware has proven to easily exploitable in its efforts to
try to eke out more performance)
I don't know any hardware manufacturer doing this -- well, I don't work
with military hardware so they could be doing it -- and now that Sam
Altman is gobbling up all the DRAM chips, I doubt we'll see this in end
user computers and phones any time soon.
You can often employ this technique in many of the larger SoCs.
sadly, the resources are often allocated by someone who doesn't
understand the VALUE of specific allocations.
E.g., if you put kernel memory in SRAM then "other memory"
being in LPDRAM has less potential -- via direct or side-channel
attack -- of corrupting it.
But, you have to be aware of the problem and understand how the
hardware works before you can make smart decisions about it.
Which, of course, means you have to have a firm hardware model
before you can sort out the software.
The hardware people are similarly clueless as they are usually not aware
of how the hardware will be used (and abused).-a They often treat
hardware as checkoff items:-a 2 serial ports; check.-a-a 3GB RAM; check.
1MB boot ROM; check.
One of the colossal FAILS IME was a hardware person putting a one-bit
latch to drive the input of a CVSD.-a So, the software had to sit in a
tight loop shifting bytes into the latch and clocking the CVSD.
And, of course, every path through the code had to have identical time
lest the clock frequency beat at the byte-rate.
Really?-a You couldn't put a byte-wide (parallel load, serial out)
SHIFT REGISTER there and have it self clocked so all the CPU has to
do is push BYTES at it every 8 bit times???-a You've traded a few pennies
for the entire CPU (because it can't do ANYTHING ELSE while caught
in this idiot loop).
Perhaps we should let hardware people write code and publicly
critique their failures?-a Or, let software people design the
hardware and let the hardware folks write the code??
So, is this a loss due to the 2026 DRAM shortage?-a Only speculative his- >>> tory in the future will tell us.
Or have more generalists around.-a I'm one -- no matter what Bill Sloman tries to say -- but with only a passing experience of hardware design.
Just enough to understand the basics.
If you dig into old Linus-rants on the LKML, you'll find the GCC-devs of"Impedance mismatches" in skillsets are common. Not just in design/development but, also, in userworld.
the time didn't care how the compiler was used for anything other than
user space.-a That's not a healthy environment for kernel devs.
So we should let compilers devs do operating systems, and operating sys-
tem people do compilers, and both groups do hardware.
At minimum.
On 11/8/2026 12:27 PM, Waldek Hebisch wrote:
You clearly go into area were you are not an expert. Google a
bit about "undefined behaviour" in C and you will learn that
when source code makes no sense, then C compier can do
essentially anything, which in not so rare cases means that
compiler simply deletes what programmer wrote. Explicit nop-s
The compiler doesn't have THAT much license. It can't decide to
implement arbitrary operations just because you APPEAR to be
relying on a behavior that is undefined.
E.g., memcpy() is free to walk past the end of the address space
if the source/destination address -- plus the length -- moves it
to that point. Or, it could opt to be more reasonable and inhibit
such action. Either solution is an acceptable behavior -- regardless
of the behavior that you *hoped* would occur.
But, it can't decide to divide every value stored in EVERY memory
location by 3 -- unless the value stored there is a 7 in which case
it replaces it with a 42. A compiler/library designer wouldn't
deliberately come up with a bizarre action to perform when the required action isn't clear. He'll do what seems logical in a normal case,
even if that isn't what the developer intended (developer broke the
contract by trying to do something that wasn't defined; we don't
punish him by killing his first-born...)
are rarely emited by compilers, but one can get 'return'
(if compiler decides that garbage source is doing nothing
useful, but it will eventually finish) or executing whatever
happens to be after deleted code (if compiler decides that
code should be never executed because it performed illegal
operation).
What "illegal operation" -- beyond a SIGSEGV? The compiler
doesn't prevent me from dividing by zero (though many are
astute enough to notice that and WARN me). Or, from overwriting
a table of interrupt vectors. Or, the software itself!
It can *advise* against things that seem likely to be errors
or result in anomalous behaviors. But, it's the developer who opts
to override those warnings. No rule says you have to check malloc()'s
return value. And, /in some cases/, you may be 100% confident that
it is *NOT* NULL.
[That's why folks who don't address every warning are shoddy
developers -- make it explicitly clear to me and the compiler
that you actually WANT this behavior!]
It is much nicer when you share things that you do know.
Johann 'Myrkraverk' Oskarsson <johann@Myrkraverk.invalid> skrev: |----------------------------------------------------------------------|
|"[. . .] | |What is not amusing is that nobody thought to put computer security | |education in the elementary schools fifty years ago." | |----------------------------------------------------------------------|
It is not plausible that a computer-security education in the
elementary schools fifty years ago (in 1976) would be useful. Almost
no child in 1976 used to have an Apple I, and an Apple I does not
demand a password. Cf.
HTTP://WWW.oldComputers.net
Johann 'Myrkraverk' Oskarsson <johann@Myrkraverk.invalid> skrev: |----------------------------------------------------------------------|
|"[. . .] |
|[. . .] I don't know what goes on in the heads of peo- |
|ple who decide the elementary curriculum. Usefulness in life is not | |their agenda. |
| |
|[. . .]" | |----------------------------------------------------------------------|
Of course it is! Elementary schools teach useful mathematics and
useful words.
Johann 'Myrkraverk' Oskarsson <johann@Myrkraverk.invalid> skrev: |----------------------------------------------------------------------| |"Err, for an introduction to that, you could use the book /Undercover | |Cop/ by Mike Russel and Patrick W. Picciarelli. It's an autobiography|
|of sorts, and therefore describes the real world, and not the fantasy | |world in movies. [. . .] |
|[. . .] |
| |
|[. . .]" | |----------------------------------------------------------------------|
Thanks for this suggestion. How did Mike Russell survive "being
ambushed and shot in the back of the head"?
Is the next quotation true? "his police handlers disregarded his
wishes and his well-being, conducting premature raids on the
gangsters."
(S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
Books and phones can become stolen.
(S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
On 10/31/2026 11:17 PM, Bill Sloman wrote:
I don't make a habit of it, but there's no diplomatic way of getting the
message across, when people are ignorant (which happens quite a lot), or
stupid (which is rarer).
Of course, you never see the same fault in yourself, you /fucking
moron/!
On 10/31/2026 11:17 PM, Bill Sloman wrote:
I don't make a habit of it, but there's no diplomatic way of getting
the message across, when people are ignorant (which happens quite a
lot), or stupid (which is rarer).
Of course, you never see the same fault in yourself, you /fucking
moron/!
On Mon, 9 Nov 2026 23:31:54 +0800, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:
On 10/31/2026 11:17 PM, Bill Sloman wrote:
I don't make a habit of it, but there's no diplomatic way of getting the >>> message across, when people are ignorant (which happens quite a lot), or >>> stupid (which is rarer).
Of course, you never see the same fault in yourself, you /fucking
moron/!
It's not anyone's fault that they are stupid. 50% of the population is
below the median IQ.
Be kind to the people who weren't lucky to be born beautiful geniuses
like us.
It is people's fault if they are nasty.
On 10/30/2026 9:36 PM, Martin Brown wrote:
I was always struck by the typical senior managers password being so
weak that it was hardly worth having. Some of them even had it written
on a postit and stuck to their screen! You couldn't make it up!
By observation -- and this is something Bill Sloman never understands,
he doesn't observe anything -
social status being around to /correct/ the managers.
their own view is more important than whoever tries to teach them good password habits.
Really, it's fine to write passwords down; just do it in a book you keep
in your pocket, and don't forget it by the computer [terminal].
And once you start writing the passwords down, you don't need to be
afraid of the cryptographically secure random password generators.
2FA helps if the password gets stolen somehow; it's usually not lifted
from the book.-a It's still annoying.
On Mon, 9 Nov 2026 16:42:08 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 9/11/2026 6:27 am, Waldek Hebisch wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:I did a lot of stuff in PDP-11 and 68K assembly languages. With a few >>>>>>> macros, they are almost higher-level languages.
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over 3000 >>>>>>>>> and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap it that >>>>>>>> way to read in a paper tape. It was a fun machine as it had a vector >>>>>>>> graphics display so was very good for asteroids, but cheated at chess. >>>>>>>
All high level languages get compiled into assembly language before they >>>>>> can be run on a computer.
Well, no.
Counter-example?
Being a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into something >>>>>> that can be run on hardware (which will have an architecture - it is >>>>>> constructed from components that have been connected by some kind of >>>>>> architect).
If that post were compiled to assembly language, it would be a nop.
As a compiler, you do seem to be sub-optimal, if not downright
afunctional. Ignoring implications you don't like isn't an option for a >>>> compiler. There can be functions they can't parse - in your case don't >>>> want to parse - but that doesn't generate a nop.
You clearly go into an area where you are not an expert.
I'm not pretending to be an expert, just less of a clueless newbie in
the area that John Larkin has shown himself to be.
I've written several compilers and several RTOS's and a bunch of
system simulators and hundreds of application programs, a good chunk
of a million lines of code. From PDP8 to ARM and one CPU that I
designed myself.
What's your definition of newbie?
in areas where you are ignorant you
can end up looking pretty stupid to people who are less ignorant.
On 10/11/2026 2:12 am, john larkin wrote:
On Mon, 9 Nov 2026 16:42:08 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 9/11/2026 6:27 am, Waldek Hebisch wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. >>>>>>>>>>>> Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over >>>>>>>>>> 3000
and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap >>>>>>>>> it that
way to read in a paper tape. It was a fun machine as it had a >>>>>>>>> vector
graphics display so was very good for asteroids, but cheated at >>>>>>>>> chess.
I did a lot of stuff in PDP-11 and 68K assembly languages. With >>>>>>>> a few
macros, they are almost higher-level languages.
All high level languages get compiled into assembly language
before they
can be run on a computer.
Well, no.
Counter-example?
As a compiler, you do seem to be sub-optimal, if not downrightBeing a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into
something
that can be run on hardware (which will have an architecture - it is >>>>>>> constructed from components that have been connected by some kind of >>>>>>> architect).
If that post were compiled to assembly language, it would be a nop. >>>>>
afunctional. Ignoring implications you don't like isn't an option
for a
compiler. There can be functions they can't parse - in your case don't >>>>> want to parse - but that doesn't generate a nop.
You clearly go into an area where you are not an expert.
I'm not pretending to be an expert, just less of a clueless newbie in
the area that John Larkin has shown himself to be.
I've written several compilers and several RTOS's and a bunch of
system simulators and hundreds of application programs, a good chunk
of a million lines of code. From PDP8 to ARM and one CPU that I
designed myself.
And I'm sure that you are perfectly happy with all of them. Egomaniacs
do go around describing themself as "stable geniuses".
What's your definition of newbie?
Somebody who doesn't know enough about what he his doing to be aware of
the areas he doesn't know enough about. It's not so much about what you know, as what you know about the limits of your knowledge.
And to finish this off with a warning, I have read the above for adults,Sorry, *written; I send before proof reading!
so if you less-than-jr-high-school reading comprehension isn't up to the
task of figuring out what I'm saying, that's squarely on you.
On 10/11/2026 2:31 am, Johann 'Myrkraverk' Oskarsson wrote:
On 10/31/2026 11:17 PM, Bill Sloman wrote:
I don't make a habit of it, but there's no diplomatic way of getting
the message across, when people are ignorant (which happens quite a
lot), or stupid (which is rarer).
Of course, you never see the same fault in yourself, you /fucking
moron/!
There are loads of areas where I'm totally ignorant. Real world feedback suggests that I'm not stupid, but in areas where you are ignorant you
can end up looking pretty stupid to people who are less ignorant.
Asserting that somebody is a /fucking moron/ is simple abuse, and that
does seem to be the only kind that you can manage.
Bill Sloman <bill.sloman@ieee.org> wrote:
[...]
in areas where you are ignorant you
can end up looking pretty stupid to people who are less ignorant.
Conversely, in areas where you are knowledgeable, you can look stupid to people who are ignorant.
On 11/9/2026 8:28 AM, Johann 'Myrkraverk' Oskarsson wrote:
On 10/29/2026 8:59 PM, Don Y wrote:
Management of these processes is the cause of most bad designs.
The folks doing so are usually pretty ignorant of the efforts they
are charged with managing!
Please excuse me, I probably showed this example earlier this year in
sci.electronics.design.-a A good example is
-a-a https://neilmadden.blog/2022/04/19/psychic-signatures-in-java/
where the /management/ was too lazy to hire a cryptographer for the pro-
ject.-a It's not like you can accuse Oracle of not affording one.
This (and the opposite:-a hiring someone and then ignoring their "expert recommendations") happens surprisingly often.
The people making the decisions aren't aware of how much they are unaware. Dunning-Kruger.-a Particularly dangerous when The Ignorant are in charge.
Nowhere is this more evident than in software as ANYONE can write code
and, true to D-K, they all *think* they know far more than they actually do.-a "I've written..." yeah, but were any of those really more than trivial exercises?-a I.e., if it was the sort of problem we'd get in a homework assignment, you know it has a complexity on the order of 8 hours or less
(cuz the homework budget for a course was 8 hours)
Another favorite is "real-time" -- particularly "hard" vs. "soft".
When most folks think it means "real fast" (it doesn't).-a Or, that
"hard" is "more difficult" than "soft" (the opposite is true -- in
spades -- which is why so many newbies resort to HRT solutions
to problems... they can't think beyond FORCING a hard requirement
when none is required... even in nuclear defenses!)
But, so much of this is ingrained that challenging it threatens
most folks' notion of their own competence so they ignore learning
about those things where their ignorance is so profound.
[You have to learn to work AROUND such people lest they compromise
any good work]
Actually, at '-O2' version of 'gcc' that I use replaces explicit
division by 0 by the 'ud2' instruction.
On 11/10/2026 1:49 PM, Bill Sloman wrote:
On 10/11/2026 2:12 am, john larkin wrote:
On Mon, 9 Nov 2026 16:42:08 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 9/11/2026 6:27 am, Waldek Hebisch wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman
<bill.sloman@ieee.org>
wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. >>>>>>>>>>>>> Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are >>>>>>>>>>> over 3000
and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap >>>>>>>>>> it that
way to read in a paper tape. It was a fun machine as it had a >>>>>>>>>> vector
graphics display so was very good for asteroids, but cheated >>>>>>>>>> at chess.
I did a lot of stuff in PDP-11 and 68K assembly languages. With >>>>>>>>> a few
macros, they are almost higher-level languages.
All high level languages get compiled into assembly language
before they
can be run on a computer.
Well, no.
Counter-example?
As a compiler, you do seem to be sub-optimal, if not downrightBeing a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into >>>>>>>> something
that can be run on hardware (which will have an architecture - >>>>>>>> it is
constructed from components that have been connected by some
kind of
architect).
If that post were compiled to assembly language, it would be a nop. >>>>>>
afunctional. Ignoring implications you don't like isn't an option >>>>>> for a
compiler. There can be functions they can't parse - in your case
don't
want to parse - but that doesn't generate a nop.
You clearly go into an area where you are not an expert.
I'm not pretending to be an expert, just less of a clueless newbie in
the area that John Larkin has shown himself to be.
I've written several compilers and several RTOS's and a bunch of
system simulators and hundreds of application programs, a good chunk
of a million lines of code. From PDP8 to ARM and one CPU that I
designed myself.
And I'm sure that you are perfectly happy with all of them. Egomaniacs
do go around describing themself as "stable geniuses".
What's your definition of newbie?
Somebody who doesn't know enough about what he his doing to be aware
of the areas he doesn't know enough about. It's not so much about what
you know, as what you know about the limits of your knowledge.
On 11/10/2026 6:20 PM, Johann 'Myrkraverk' Oskarsson wrote:
And to finish this off with a warning, I have read the above for adults,Sorry, *written; I send before proof reading!
so if you less-than-jr-high-school reading comprehension isn't up to the
task of figuring out what I'm saying, that's squarely on you.
On 11/10/2026 6:12 PM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
[1] If we use that term, the meme with the IQ curve I'm referring to has
a /moron/ on the left, and a /jedi master/ on the right.-a The terms do
not matter so much as long as we're being understood.
On 10/11/2026 9:22 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 6:20 PM, Johann 'Myrkraverk' Oskarsson wrote:
And to finish this off with a warning, I have read the above for adults, >>> so if you less-than-jr-high-school reading comprehension isn't up to the >>> task of figuring out what I'm saying, that's squarely on you.Sorry, *written; I send before proof reading!
"Sent" before proof reading. You imagine that you wrote your pretentious twaddle for adults, not realising that the "adults" have noticed that
you don't have anything useful to say, and have mostly got around to plonking you.
On 11/10/2026 1:10 PM, Bill Sloman wrote:
On 10/11/2026 2:31 am, Johann 'Myrkraverk' Oskarsson wrote:
On 10/31/2026 11:17 PM, Bill Sloman wrote:
I don't make a habit of it, but there's no diplomatic way of getting
the message across, when people are ignorant (which happens quite a
lot), or stupid (which is rarer).
Of course, you never see the same fault in yourself, you /fucking
moron/!
There are loads of areas where I'm totally ignorant. Real world
feedback suggests that I'm not stupid, but in areas where you are
ignorant you can end up looking pretty stupid to people who are less
ignorant.
Asserting that somebody is a /fucking moron/ is simple abuse, and that
does seem to be the only kind that you can manage.
No, absolutely not.-a I'm capable of quite complex abuse, which you'd re- member if you bothered to remember anything.
Happy receiving abuse, you fucking moron!
On 10/11/2026 9:38 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 6:12 PM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
[1] If we use that term, the meme with the IQ curve I'm referring to has
a /moron/ on the left, and a /jedi master/ on the right.-a The terms do
not matter so much as long as we're being understood.
What's obvious that you understand IQ curves to be scoring a single-
valued parameter.
It's well known that there are lots of components to the faculty that is usually described as intelligence. Quite a lot of work was done early on
om multifactor intelligence tests, but it didn't go anywhere useful.
The people doing the work didn't have much of a clue what the different factors might be, and didn't find any practical way of teasing out what
they might be. When people in recent years started using magnetic
resonance images of the brain to work out what was going on in the
brain, where, and in what sequence, they didn't do any better.
It's complicated and we need tools with a lot better discrimination than
we have at the moment.
If you think that you can divide the world into a linear array of people running from moron to the left to jedi master on the right, you've put yourself into the moron category.
My late wife was a psycholinguist who spoke four languages fluently and
was a foreign member of the US Academy of Science and a Fellow of the
Royal Society of London, but she didn't know much about electronics. At least she had enough sense not to post here.
On 11/10/2026 2:23 AM, Don Y wrote:
On 11/9/2026 8:28 AM, Johann 'Myrkraverk' Oskarsson wrote:
On 10/29/2026 8:59 PM, Don Y wrote:
Management of these processes is the cause of most bad designs.
The folks doing so are usually pretty ignorant of the efforts they
are charged with managing!
Please excuse me, I probably showed this example earlier this year in
sci.electronics.design.-a A good example is
-a-a https://neilmadden.blog/2022/04/19/psychic-signatures-in-java/
where the /management/ was too lazy to hire a cryptographer for the pro- >>> ject.-a It's not like you can accuse Oracle of not affording one.
This (and the opposite:-a hiring someone and then ignoring their "expert
recommendations") happens surprisingly often.
The people making the decisions aren't aware of how much they are
unaware.
Dunning-Kruger.-a Particularly dangerous when The Ignorant are in charge.
Nowhere is this more evident than in software as ANYONE can write code
and, true to D-K, they all *think* they know far more than they actually
do.-a "I've written..." yeah, but were any of those really more than
trivial
exercises?-a I.e., if it was the sort of problem we'd get in a homework
assignment, you know it has a complexity on the order of 8 hours or less
(cuz the homework budget for a course was 8 hours)
Another favorite is "real-time" -- particularly "hard" vs. "soft".
When most folks think it means "real fast" (it doesn't).-a Or, that
"hard" is "more difficult" than "soft" (the opposite is true -- in
spades -- which is why so many newbies resort to HRT solutions
to problems... they can't think beyond FORCING a hard requirement
when none is required... even in nuclear defenses!)
But, so much of this is ingrained that challenging it threatens
most folks' notion of their own competence so they ignore learning
about those things where their ignorance is so profound.
[You have to learn to work AROUND such people lest they compromise
any good work]
Thank you.-a When it comes to highly paid managers, or CEOs for that
matter, I have this theory that /whoever is paid more is right/.-a Which while watching financial crisis reenactment movies [1] seems to be true.
Of course I'm not completely sure of this, and there are always excep-
tions, so we can consider it a /working theory/, and add more observa-
tions of managers to the mix to see if it comes out statistically true
or false.
On the prior topic, I also lack experience in hard real time design, and don't even have a lot to say about the soft part of it.-a It's something
I'll keep in mind whenever I find myself facing such projects.
On 10/11/2026 2:23 pm, john larkin wrote:
On Mon, 9 Nov 2026 23:31:54 +0800, Johann 'Myrkraverk' Oskarsson
<johann@myrkraverk.invalid> wrote:
On 10/31/2026 11:17 PM, Bill Sloman wrote:
I don't make a habit of it, but there's no diplomatic way of getting the >>>> message across, when people are ignorant (which happens quite a lot), or >>>> stupid (which is rarer).
Of course, you never see the same fault in yourself, you /fucking
moron/!
It's not anyone's fault that they are stupid. 50% of the population is
below the median IQ.
I'm not. It's hard to get a Ph.D. if you can't score higher than 115 on
a IQ test, and I didn't have any trouble doing that, though I did take
a while to finish the project. The IQ test is a cheap, simple and none
too reliable measure of intelligence, but stupid people do pay more >attention to IQ scores than they should.
Be kind to the people who weren't lucky to be born beautiful geniuses
like us.
John Larkin isn't a genius - neither is Donald Trump - but egomaniacs do >like to make those kinds of claims
It is people's fault if they are nasty.
In some situations being nasty is the only way to get the message across.
On 11/10/2026 6:12 PM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
[...]
in areas where you are ignorant you
can end up looking pretty stupid to people who are less ignorant.
Conversely, in areas where you are knowledgeable, you can look stupid to
people who are ignorant.
And this happens all the time. It's kind of better to be a /midwit/
than a genius [1]. I've seen that a lot, in online /special interest/ >groups, and be subject to such abuse myself. The problem when people
get abusive, and say someone is /incompetent/, is that they are gener-
ally wrong. First, the moron can learn, and become greater that the
person throwing the abuse. This is an effect of time. Second, the ab-
user rarely follows up with /why/ said abuse was thrown, so the receiver
is left to ponder -- is there something I don't know, or are you just a >moron?
Now, people been around the block a few times know that today's ignora-
mus can be a /jedi master/ in a few months, or years, and doesn't have
to tell the rest of the group about their knowledge accumulation. So
they always end up as /just another moron/ once the person knows better.
This is called /lack of social skills/, and has real consequences.
Something some members of sci.electronics.design have yet to learn.
Best wishes, and happy jedi mastery!
[1] If we use that term, the meme with the IQ curve I'm referring to has
a /moron/ on the left, and a /jedi master/ on the right. The terms do
not matter so much as long as we're being understood.
On 10/11/2026 2:12 am, john larkin wrote:
On Mon, 9 Nov 2026 16:42:08 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 9/11/2026 6:27 am, Waldek Hebisch wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over 3000 >>>>>>>>>> and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap it that
way to read in a paper tape. It was a fun machine as it had a vector >>>>>>>>> graphics display so was very good for asteroids, but cheated at chess.
I did a lot of stuff in PDP-11 and 68K assembly languages. With a few >>>>>>>> macros, they are almost higher-level languages.
All high level languages get compiled into assembly language before they
can be run on a computer.
Well, no.
Counter-example?
As a compiler, you do seem to be sub-optimal, if not downrightBeing a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into something >>>>>>> that can be run on hardware (which will have an architecture - it is >>>>>>> constructed from components that have been connected by some kind of >>>>>>> architect).
If that post were compiled to assembly language, it would be a nop. >>>>>
afunctional. Ignoring implications you don't like isn't an option for a >>>>> compiler. There can be functions they can't parse - in your case don't >>>>> want to parse - but that doesn't generate a nop.
You clearly go into an area where you are not an expert.
I'm not pretending to be an expert, just less of a clueless newbie in
the area that John Larkin has shown himself to be.
I've written several compilers and several RTOS's and a bunch of
system simulators and hundreds of application programs, a good chunk
of a million lines of code. From PDP8 to ARM and one CPU that I
designed myself.
And I'm sure that you are perfectly happy with all of them. Egomaniacs
do go around describing themself as "stable geniuses".
What's your definition of newbie?
Somebody who doesn't know enough about what he his doing to be aware of
the areas he doesn't know enough about. It's not so much about what you >know, as what you know about the limits of your knowledge.
On 11/10/2026 1:49 PM, Bill Sloman wrote:
On 10/11/2026 2:12 am, john larkin wrote:
On Mon, 9 Nov 2026 16:42:08 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 9/11/2026 6:27 am, Waldek Hebisch wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. >>>>>>>>>>>>> Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over >>>>>>>>>>> 3000
and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap >>>>>>>>>> it that
way to read in a paper tape. It was a fun machine as it had a >>>>>>>>>> vector
graphics display so was very good for asteroids, but cheated at >>>>>>>>>> chess.
I did a lot of stuff in PDP-11 and 68K assembly languages. With >>>>>>>>> a few
macros, they are almost higher-level languages.
All high level languages get compiled into assembly language
before they
can be run on a computer.
Well, no.
Counter-example?
As a compiler, you do seem to be sub-optimal, if not downrightBeing a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into >>>>>>>> something
that can be run on hardware (which will have an architecture - it is >>>>>>>> constructed from components that have been connected by some kind of >>>>>>>> architect).
If that post were compiled to assembly language, it would be a nop. >>>>>>
afunctional. Ignoring implications you don't like isn't an option >>>>>> for a
compiler. There can be functions they can't parse - in your case don't >>>>>> want to parse - but that doesn't generate a nop.
You clearly go into an area where you are not an expert.
I'm not pretending to be an expert, just less of a clueless newbie in
the area that John Larkin has shown himself to be.
I've written several compilers and several RTOS's and a bunch of
system simulators and hundreds of application programs, a good chunk
of a million lines of code. From PDP8 to ARM and one CPU that I
designed myself.
And I'm sure that you are perfectly happy with all of them. Egomaniacs
do go around describing themself as "stable geniuses".
What's your definition of newbie?
Somebody who doesn't know enough about what he his doing to be aware of
the areas he doesn't know enough about. It's not so much about what you
know, as what you know about the limits of your knowledge.
And then we have the military term "unknown unknown." For instance in >business, you cannot prevent someone from inventing something else, that >completely obsoletes your business.
In /tech/, this is not an unknown unknown, because it's been done so
many times in living memory. It can still happen in other fields, com- >pletely blind-sighting the billionaires in charge of it.
Some people refer to this as a /black swan/ event, which I believe comes
from the field of economics.
And, to combine this topic with another one, since we were talking about >compilers, in the 90s, prior to the publication of GCC 2.95 [1], it
would have been considered an /unknown unknown/ that compilers could be-
come malicious to security sensitive programming. I bring you [2] as
exhibit A, and give the relevant quote.
The short and long is that, today, the only way to access a constant
time implementation from Rust is to write said implementation in
assembly.
I'll add that this is about comparing security sensitive strings, us-
ually of fixed length [3], and /not/ an O( 1 ) algorithm.
You can read this poster's point about why LLVM is not a polite com-
piler at [2].
Now, if you want to argue this conclusion, you'll have to make an acc-
ount on Stack Overflow, and comment there.
In other words, the only way to write constant time cryptography, is ba- >sically to do it in assembly, if any of GCC, LLVM, or MSVC are to com-
pile it.
In that sense, the /social contract/ between security sensitive program- >ming, and compiler makers has been broken.
And since we are in sci.electronics.design, we can also add that hard-
ware manufacturers typically do not assert in their manuals that a spe-
cific instruction is constant time, so now we get to wait and see if any
of the x86, or ARM, or maybe even RISC-V manufacturers bring back the
evil that was -- to my recollection -- the original 68000 shift instruc-
tion which spent more clock time for larger shift values.
And to finish this off with a warning, I have read the above for adults,
so if you less-than-jr-high-school reading comprehension isn't up to the
task of figuring out what I'm saying, that's squarely on you.
Best wishes, and happy constant time algorithms!
[1] Given Anton Ertl's research.
[2] >https://stackoverflow.com/questions/44691363/how-to-compare-strings-in-constant-time
[3] Hashed passwords are always the same length, but if the length
changes, comparing them in constant time doesn't work; this should be >obvious.
On Tue, 10 Nov 2026 18:20:58 +0800, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:
On 11/10/2026 1:49 PM, Bill Sloman wrote:
On 10/11/2026 2:12 am, john larkin wrote:
On Mon, 9 Nov 2026 16:42:08 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 9/11/2026 6:27 am, Waldek Hebisch wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. >>>>>>>>>>>>>> Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over >>>>>>>>>>>> 3000
and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to bootstrap >>>>>>>>>>> it that
way to read in a paper tape. It was a fun machine as it had a >>>>>>>>>>> vector
graphics display so was very good for asteroids, but cheated at >>>>>>>>>>> chess.
I did a lot of stuff in PDP-11 and 68K assembly languages. With >>>>>>>>>> a few
macros, they are almost higher-level languages.
All high level languages get compiled into assembly language >>>>>>>>> before they
can be run on a computer.
Well, no.
Counter-example?
As a compiler, you do seem to be sub-optimal, if not downrightBeing a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into >>>>>>>>> something
that can be run on hardware (which will have an architecture - it is >>>>>>>>> constructed from components that have been connected by some kind of >>>>>>>>> architect).
If that post were compiled to assembly language, it would be a nop. >>>>>>>
afunctional. Ignoring implications you don't like isn't an option >>>>>>> for a
compiler. There can be functions they can't parse - in your case don't >>>>>>> want to parse - but that doesn't generate a nop.
You clearly go into an area where you are not an expert.
I'm not pretending to be an expert, just less of a clueless newbie in >>>>> the area that John Larkin has shown himself to be.
I've written several compilers and several RTOS's and a bunch of
system simulators and hundreds of application programs, a good chunk
of a million lines of code. From PDP8 to ARM and one CPU that I
designed myself.
And I'm sure that you are perfectly happy with all of them. Egomaniacs
do go around describing themself as "stable geniuses".
What's your definition of newbie?
Somebody who doesn't know enough about what he his doing to be aware of
the areas he doesn't know enough about. It's not so much about what you
know, as what you know about the limits of your knowledge.
And then we have the military term "unknown unknown." For instance in
business, you cannot prevent someone from inventing something else, that
completely obsoletes your business.
In /tech/, this is not an unknown unknown, because it's been done so
many times in living memory. It can still happen in other fields, com-
pletely blind-sighting the billionaires in charge of it.
Some people refer to this as a /black swan/ event, which I believe comes >>from the field of economics.
And, to combine this topic with another one, since we were talking about
compilers, in the 90s, prior to the publication of GCC 2.95 [1], it
would have been considered an /unknown unknown/ that compilers could be-
come malicious to security sensitive programming. I bring you [2] as
exhibit A, and give the relevant quote.
The short and long is that, today, the only way to access a constant
time implementation from Rust is to write said implementation in
assembly.
I'll add that this is about comparing security sensitive strings, us-
ually of fixed length [3], and /not/ an O( 1 ) algorithm.
You can read this poster's point about why LLVM is not a polite com-
piler at [2].
Now, if you want to argue this conclusion, you'll have to make an acc-
ount on Stack Overflow, and comment there.
In other words, the only way to write constant time cryptography, is ba-
sically to do it in assembly, if any of GCC, LLVM, or MSVC are to com-
pile it.
In that sense, the /social contract/ between security sensitive program-
ming, and compiler makers has been broken.
And since we are in sci.electronics.design, we can also add that hard-
ware manufacturers typically do not assert in their manuals that a spe-
cific instruction is constant time, so now we get to wait and see if any
of the x86, or ARM, or maybe even RISC-V manufacturers bring back the
evil that was -- to my recollection -- the original 68000 shift instruc-
tion which spent more clock time for larger shift values.
And to finish this off with a warning, I have read the above for adults,
so if you less-than-jr-high-school reading comprehension isn't up to the
task of figuring out what I'm saying, that's squarely on you.
Best wishes, and happy constant time algorithms!
[1] Given Anton Ertl's research.
[2]
https://stackoverflow.com/questions/44691363/how-to-compare-strings-in-constant-time
[3] Hashed passwords are always the same length, but if the length
changes, comparing them in constant time doesn't work; this should be
obvious.
I'm always impressed by how few programmers have even a rough idea of
how much time it takes to execute their code. Guessing off by 10:1 is
common.
I get a scope and measure it.
We have a 75-cent dual-core ARM making a 100 MHz square wave, lines of
c setting a port bit up and down.
On Tue, 10 Nov 2026 18:38:47 +0800, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:
On 11/10/2026 6:12 PM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
[...]
in areas where you are ignorant you
can end up looking pretty stupid to people who are less ignorant.
Conversely, in areas where you are knowledgeable, you can look stupid to >>> people who are ignorant.
And this happens all the time. It's kind of better to be a /midwit/
than a genius [1]. I've seen that a lot, in online /special interest/
groups, and be subject to such abuse myself. The problem when people
get abusive, and say someone is /incompetent/, is that they are gener-
ally wrong. First, the moron can learn, and become greater that the
person throwing the abuse. This is an effect of time. Second, the ab-
user rarely follows up with /why/ said abuse was thrown, so the receiver
is left to ponder -- is there something I don't know, or are you just a
moron?
Now, people been around the block a few times know that today's ignora-
mus can be a /jedi master/ in a few months, or years, and doesn't have
to tell the rest of the group about their knowledge accumulation. So
they always end up as /just another moron/ once the person knows better.
This is called /lack of social skills/, and has real consequences.
Something some members of sci.electronics.design have yet to learn.
Best wishes, and happy jedi mastery!
[1] If we use that term, the meme with the IQ curve I'm referring to has
a /moron/ on the left, and a /jedi master/ on the right. The terms do
not matter so much as long as we're being understood.
Some people have extreme talents. It might be math, music, tennis,
whatever. Some part of their brain is six-sigma good, often at the
expense of other parts.
The specialized-genius bit can also make them obnoxious.
Johann 'Myrkraverk' Oskarsson <johann@Myrkraverk.invalid> skrev: |-----------------------------------------------------------------------| |"[. . .] Part of the | |theme of the book is the incompetence on the part of the police team --| |this includes Mike himself -- in planning and executing the undercover | |stint. [. . .] |
|[. . .]" | |-----------------------------------------------------------------------|
Hej!
Do you know if there are any similar books about Scandinavian or
Icelandic incompetent police forces or other incompetent authorities
(e.g. courts)? (I do not need such books to be in English - I can read Swedish etc.) I asked a friend in Sweden is "Skiftet" on Netflix a
true story. He did not know. (It is not a true story, but it is
supposed to be realistic.) Thanks.
|-----------------------------------------------------------------------| |"As for how he survived, it's best you just read the book to find out. |
| |
|[. . .]" | |-----------------------------------------------------------------------|
The blurb is not convincing that a person could really survive being
shot in his head. (Trump does survive, because an ear got shot.)
(S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
On 11/10/2026 11:59 PM, john larkin wrote:
On Tue, 10 Nov 2026 18:20:58 +0800, Johann 'Myrkraverk' OskarssonNow, please excuse my ignorance here [1], is that more or less expensive
<johann@myrkraverk.invalid> wrote:
On 11/10/2026 1:49 PM, Bill Sloman wrote:
On 10/11/2026 2:12 am, john larkin wrote:
On Mon, 9 Nov 2026 16:42:08 +1100, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:
On 9/11/2026 6:27 am, Waldek Hebisch wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman <bill.sloman@ieee.org> >>>>>>>>> wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. >>>>>>>>>>>>>>> Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over >>>>>>>>>>>>> 3000
and they keep coming.
Real men code in binary using the front panel switches. >>>>>>>>>>>>
I actually used a PDP-7 where you really did have to bootstrap >>>>>>>>>>>> it that
way to read in a paper tape. It was a fun machine as it had a >>>>>>>>>>>> vector
graphics display so was very good for asteroids, but cheated at >>>>>>>>>>>> chess.
I did a lot of stuff in PDP-11 and 68K assembly languages. With >>>>>>>>>>> a few
macros, they are almost higher-level languages.
All high level languages get compiled into assembly language >>>>>>>>>> before they
can be run on a computer.
Well, no.
Counter-example?
As a compiler, you do seem to be sub-optimal, if not downright >>>>>>>> afunctional. Ignoring implications you don't like isn't an option >>>>>>>> for aBeing a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into >>>>>>>>>> something
that can be run on hardware (which will have an architecture - it is >>>>>>>>>> constructed from components that have been connected by some kind of >>>>>>>>>> architect).
If that post were compiled to assembly language, it would be a nop. >>>>>>>>
compiler. There can be functions they can't parse - in your case don't >>>>>>>> want to parse - but that doesn't generate a nop.
You clearly go into an area where you are not an expert.
I'm not pretending to be an expert, just less of a clueless newbie in >>>>>> the area that John Larkin has shown himself to be.
I've written several compilers and several RTOS's and a bunch of
system simulators and hundreds of application programs, a good chunk >>>>> of a million lines of code. From PDP8 to ARM and one CPU that I
designed myself.
And I'm sure that you are perfectly happy with all of them. Egomaniacs >>>> do go around describing themself as "stable geniuses".
What's your definition of newbie?
Somebody who doesn't know enough about what he his doing to be aware of >>>> the areas he doesn't know enough about. It's not so much about what you >>>> know, as what you know about the limits of your knowledge.
And then we have the military term "unknown unknown." For instance in
business, you cannot prevent someone from inventing something else, that >>> completely obsoletes your business.
In /tech/, this is not an unknown unknown, because it's been done so
many times in living memory. It can still happen in other fields, com-
pletely blind-sighting the billionaires in charge of it.
Some people refer to this as a /black swan/ event, which I believe comes >>>from the field of economics.
And, to combine this topic with another one, since we were talking about >>> compilers, in the 90s, prior to the publication of GCC 2.95 [1], it
would have been considered an /unknown unknown/ that compilers could be- >>> come malicious to security sensitive programming. I bring you [2] as
exhibit A, and give the relevant quote.
The short and long is that, today, the only way to access a constant
time implementation from Rust is to write said implementation in
assembly.
I'll add that this is about comparing security sensitive strings, us-
ually of fixed length [3], and /not/ an O( 1 ) algorithm.
You can read this poster's point about why LLVM is not a polite com-
piler at [2].
Now, if you want to argue this conclusion, you'll have to make an acc-
ount on Stack Overflow, and comment there.
In other words, the only way to write constant time cryptography, is ba- >>> sically to do it in assembly, if any of GCC, LLVM, or MSVC are to com-
pile it.
In that sense, the /social contract/ between security sensitive program- >>> ming, and compiler makers has been broken.
And since we are in sci.electronics.design, we can also add that hard-
ware manufacturers typically do not assert in their manuals that a spe-
cific instruction is constant time, so now we get to wait and see if any >>> of the x86, or ARM, or maybe even RISC-V manufacturers bring back the
evil that was -- to my recollection -- the original 68000 shift instruc- >>> tion which spent more clock time for larger shift values.
And to finish this off with a warning, I have read the above for adults, >>> so if you less-than-jr-high-school reading comprehension isn't up to the >>> task of figuring out what I'm saying, that's squarely on you.
Best wishes, and happy constant time algorithms!
[1] Given Anton Ertl's research.
[2]
https://stackoverflow.com/questions/44691363/how-to-compare-strings-in-constant-time
[3] Hashed passwords are always the same length, but if the length
changes, comparing them in constant time doesn't work; this should be
obvious.
I'm always impressed by how few programmers have even a rough idea of
how much time it takes to execute their code. Guessing off by 10:1 is
common.
I get a scope and measure it.
We have a 75-cent dual-core ARM making a 100 MHz square wave, lines of
c setting a port bit up and down.
than a Yamaha OPL chip? I guess they aren't made anymore, since I can't
find anything on digikey quickly with the keywords "YMF262." So I just
don't know how expensive they were.
Of course, I'm sure your 75-cent dual-core ARM chips is doing something
else too, but I got curious, and couldn't find a price.
Best wishes, and happy electronics!--- Synchronet 3.22a-Linux NewsLink 1.2
[1] And hopefully just enjoy it.
Bill Sloman <bill.sloman@ieee.org> wrote:
[...]
in areas where you are ignorant you
can end up looking pretty stupid to people who are less ignorant.
Conversely, in areas where you are knowledgeable, you can look stupid to people who are ignorant.
On 11/10/2026 5:12 AM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
[...]
in areas where you are ignorant you
can end up looking pretty stupid to people who are less ignorant.
Conversely, in areas where you are knowledgeable, you can look stupid to
people who are ignorant.
And some who are knowledgeable use that knowledge stupidly,
and can look stupid to most everyone, ignorant or not.
A closed mouth gathers no foot.
Ed
2 of my cell phones are stolen. I stopped using a cell
phone. Unfortunately many suppliers of things make being a client
without a cell phone difficult.
(S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
On 11/11/2026 5:27 AM, ehsjr wrote:
On 11/10/2026 5:12 AM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
[...]
in areas where you are ignorant you
can end up looking pretty stupid to people who are less ignorant.
Conversely, in areas where you are knowledgeable, you can look stupid to >>> people who are ignorant.
And some who are knowledgeable use that knowledge stupidly,
and can look stupid to most everyone, ignorant or not.
A closed mouth gathers no foot.
Ed
While I am not certain that trying to /appear not stupid/ is a virtue.
Sometimes it's quite useful to get corrections from people who know
better. Other times, people use that /perceived stupidity/ to heap
abuse upon the unsuspecting enquirer, with predictable results.
In any case, trying to use /knowledge/ as a status symbol seems quite
stupid to me; yet a lot of people behave this way.
On Tue, 10 Nov 2026 16:18:38 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 10/11/2026 2:23 pm, john larkin wrote:
On Mon, 9 Nov 2026 23:31:54 +0800, Johann 'Myrkraverk' Oskarsson
<johann@myrkraverk.invalid> wrote:
On 10/31/2026 11:17 PM, Bill Sloman wrote:
I don't make a habit of it, but there's no diplomatic way of getting the >>>>> message across, when people are ignorant (which happens quite a lot), or >>>>> stupid (which is rarer).
Of course, you never see the same fault in yourself, you /fucking
moron/!
It's not anyone's fault that they are stupid. 50% of the population is
below the median IQ.
I'm not. It's hard to get a Ph.D. if you can't score higher than 115 on
a IQ test, and I didn't have any trouble doing that, though I did take
a while to finish the project. The IQ test is a cheap, simple and none
too reliable measure of intelligence, but stupid people do pay more
attention to IQ scores than they should.
Be kind to the people who weren't lucky to be born beautiful geniuses
like us.
John Larkin isn't a genius - neither is Donald Trump - but egomaniacs do
like to make those kinds of claims
It is people's fault if they are nasty.
In some situations being nasty is the only way to get the message across.
It's the stupid, nasty, lazy, least effective way.
Especially when you're not right.
I think that's recursive.
On Tue, 10 Nov 2026 16:18:38 +1100, Bill Sloman <bill.sloman@ieee.org> wrote:getting the
On 10/11/2026 2:23 pm, john larkin wrote:
On Mon, 9 Nov 2026 23:31:54 +0800, Johann 'Myrkraverk' Oskarsson
<johann@myrkraverk.invalid> wrote:
On 10/31/2026 11:17 PM, Bill Sloman wrote:
I don't make a habit of it, but there's no diplomatic way of
lot), ormessage across, when people are ignorant (which happens quite a
across.stupid (which is rarer).
Of course, you never see the same fault in yourself, you /fucking
moron/!
It's not anyone's fault that they are stupid. 50% of the population is
below the median IQ.
I'm not. It's hard to get a Ph.D. if you can't score higher than 115 on
a IQ test, and I didn't have any trouble doing that, though I did take
a while to finish the project. The IQ test is a cheap, simple and none
too reliable measure of intelligence, but stupid people do pay more
attention to IQ scores than they should.
Be kind to the people who weren't lucky to be born beautiful geniuses
like us.
John Larkin isn't a genius - neither is Donald Trump - but egomaniacs do
like to make those kinds of claims
It is people's fault if they are nasty.
In some situations being nasty is the only way to get the message
It's the stupid, nasty, lazy, least effective way.
Especially when you're not right.
I think that's recursive.
On 11/11/2026 5:27 AM, ehsjr wrote:
On 11/10/2026 5:12 AM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
[...]
in areas where you are ignorant you
can end up looking pretty stupid to people who are less ignorant.
Conversely, in areas where you are knowledgeable, you can look stupid to >>> people who are ignorant.
And some who are knowledgeable use that knowledge stupidly,
and can look stupid to most everyone, ignorant or not.
A closed mouth gathers no foot.
Ed
While I am not certain that trying to /appear not stupid/ is a virtue.
Sometimes it's quite useful to get corrections from people who know
better.-a Other times, people use that /perceived stupidity/ to heap
abuse upon the unsuspecting enquirer, with predictable results.
In any case, trying to use /knowledge/ as a status symbol seems quite
stupid to me; yet a lot of people behave this way.
On 11/10/2026 9:08 PM, Bill Sloman wrote:
On 10/11/2026 9:38 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 6:12 PM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
[1] If we use that term, the meme with the IQ curve I'm referring to has >>> a /moron/ on the left, and a /jedi master/ on the right.-a The terms do
not matter so much as long as we're being understood.
What's obvious that you understand IQ curves to be scoring a single-
valued parameter.
It's well known that there are lots of components to the faculty that
is usually described as intelligence. Quite a lot of work was done
early on om multifactor intelligence tests, but it didn't go anywhere
useful.
The people doing the work didn't have much of a clue what the
different factors might be, and didn't find any practical way of
teasing out what they might be. When people in recent years started
using magnetic resonance images of the brain to work out what was
going on in the brain, where, and in what sequence, they didn't do any
better.
It's complicated and we need tools with a lot better discrimination
than we have at the moment.
If you think that you can divide the world into a linear array of
people running from moron to the left to jedi master on the right,
you've put yourself into the moron category.
My late wife was a psycholinguist who spoke four languages fluently
and was a foreign member of the US Academy of Science and a Fellow of
the Royal Society of London, but she didn't know much about
electronics. At least she had enough sense not to post here.
Well, I never met your late wife, but I can tell you that I don't
believe anything about the current "understanding" of IQ.-a It's only
useful in one context, and that's measuring learning disability.
Anything else is just handwaving and useless twiddle twaddle among the academi-
cians.
This belief is based on actual /real life/ experience, something you
have never experienced yourself, demonstrating time and again that you
don't know how life works.
And, no; I'm not going to bother explaining anything to you, because
this is outside the scope of sci.electronics.design, and the rest of
the people aren't asking.-a /You/ personally are not worth explaining anything to.-a You know that, don't you?
Best wishes, and be even more miserable than usual!
On Tue, 10 Nov 2026 18:38:47 +0800, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:
On 11/10/2026 6:12 PM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
[...]
in areas where you are ignorant you
can end up looking pretty stupid to people who are less ignorant.
Conversely, in areas where you are knowledgeable, you can look stupid to >>> people who are ignorant.
And this happens all the time. It's kind of better to be a /midwit/
than a genius [1]. I've seen that a lot, in online /special interest/
groups, and be subject to such abuse myself. The problem when people
get abusive, and say someone is /incompetent/, is that they are gener-
ally wrong. First, the moron can learn, and become greater that the
person throwing the abuse. This is an effect of time. Second, the ab-
user rarely follows up with /why/ said abuse was thrown, so the receiver
is left to ponder -- is there something I don't know, or are you just a
moron?
Now, people been around the block a few times know that today's ignora-
mus can be a /jedi master/ in a few months, or years, and doesn't have
to tell the rest of the group about their knowledge accumulation. So
they always end up as /just another moron/ once the person knows better.
This is called /lack of social skills/, and has real consequences.
Something some members of sci.electronics.design have yet to learn.
Best wishes, and happy jedi mastery!
[1] If we use that term, the meme with the IQ curve I'm referring to has
a /moron/ on the left, and a /jedi master/ on the right. The terms do
not matter so much as long as we're being understood.
Some people have extreme talents. It might be math, music, tennis,
whatever. Some part of their brain is six-sigma good, often at the
expense of other parts.
The specialized-genius bit can also make them obnoxious.
On Wed, 11 Nov 2026 06:09:54 +0800, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:
On 11/11/2026 5:27 AM, ehsjr wrote:
On 11/10/2026 5:12 AM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
[...]
in areas where you are ignorant you
can end up looking pretty stupid to people who are less ignorant.
Conversely, in areas where you are knowledgeable, you can look stupid to >>>> people who are ignorant.
And some who are knowledgeable use that knowledge stupidly,
and can look stupid to most everyone, ignorant or not.
A closed mouth gathers no foot.
Ed
While I am not certain that trying to /appear not stupid/ is a virtue.
Sometimes it's quite useful to get corrections from people who know
better. Other times, people use that /perceived stupidity/ to heap
abuse upon the unsuspecting enquirer, with predictable results.
In any case, trying to use /knowledge/ as a status symbol seems quite
stupid to me; yet a lot of people behave this way.
If you are always right, you get all the blame when things go wrong.
On 11/10/2026 8:46 PM, Bill Sloman wrote:
On 10/11/2026 9:22 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 6:20 PM, Johann 'Myrkraverk' Oskarsson wrote:
And to finish this off with a warning, I have read the above forSorry, *written; I send before proof reading!
adults,
so if you less-than-jr-high-school reading comprehension isn't up to
the
task of figuring out what I'm saying, that's squarely on you.
"Sent" before proof reading. You imagine that you wrote your
pretentious twaddle for adults, not realising that the "adults" have
noticed that you don't have anything useful to say, and have mostly
got around to plonking you.
Speaking for yourself, are you?-a Because here in sci.electronics.design, you're the only one plonking.-a And you're plonking everyone else.
So you're the bully who has never faced the consequences of his own
actions.
And I'm here now, and I'll take none of it silently.-a You are a fucking bully, and you don't know it.
Now you do.
And everyone else here in sci.electronics.design knew it
too but was too polite to tell you -- maybe.
I didn't read the 30 year backlog.
Best wishes, and keep being miserable for the next fifty years -- at
least!
On Wed, 11 Nov 2026 02:21:09 +0800, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:
On 11/10/2026 11:59 PM, john larkin wrote:
On Tue, 10 Nov 2026 18:20:58 +0800, Johann 'Myrkraverk' OskarssonNow, please excuse my ignorance here [1], is that more or less expensive
<johann@myrkraverk.invalid> wrote:
On 11/10/2026 1:49 PM, Bill Sloman wrote:
On 10/11/2026 2:12 am, john larkin wrote:
On Mon, 9 Nov 2026 16:42:08 +1100, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:
On 9/11/2026 6:27 am, Waldek Hebisch wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown >>>>>>>>>>>>>>> <'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. >>>>>>>>>>>>>>>> Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over >>>>>>>>>>>>>> 3000
and they keep coming.
Real men code in binary using the front panel switches. >>>>>>>>>>>>>
I actually used a PDP-7 where you really did have to bootstrap >>>>>>>>>>>>> it that
way to read in a paper tape. It was a fun machine as it had a >>>>>>>>>>>>> vector
graphics display so was very good for asteroids, but cheated at >>>>>>>>>>>>> chess.
I did a lot of stuff in PDP-11 and 68K assembly languages. With >>>>>>>>>>>> a few
macros, they are almost higher-level languages.
All high level languages get compiled into assembly language >>>>>>>>>>> before they
can be run on a computer.
Well, no.
Counter-example?
As a compiler, you do seem to be sub-optimal, if not downright >>>>>>>>> afunctional. Ignoring implications you don't like isn't an option >>>>>>>>> for aBeing a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into >>>>>>>>>>> something
that can be run on hardware (which will have an architecture - it is
constructed from components that have been connected by some kind of
architect).
If that post were compiled to assembly language, it would be a nop. >>>>>>>>>
compiler. There can be functions they can't parse - in your case don't
want to parse - but that doesn't generate a nop.
You clearly go into an area where you are not an expert.
I'm not pretending to be an expert, just less of a clueless newbie in >>>>>>> the area that John Larkin has shown himself to be.
I've written several compilers and several RTOS's and a bunch of
system simulators and hundreds of application programs, a good chunk >>>>>> of a million lines of code. From PDP8 to ARM and one CPU that I
designed myself.
And I'm sure that you are perfectly happy with all of them. Egomaniacs >>>>> do go around describing themself as "stable geniuses".
What's your definition of newbie?
Somebody who doesn't know enough about what he his doing to be aware of >>>>> the areas he doesn't know enough about. It's not so much about what you >>>>> know, as what you know about the limits of your knowledge.
And then we have the military term "unknown unknown." For instance in >>>> business, you cannot prevent someone from inventing something else, that >>>> completely obsoletes your business.
In /tech/, this is not an unknown unknown, because it's been done so
many times in living memory. It can still happen in other fields, com- >>>> pletely blind-sighting the billionaires in charge of it.
Some people refer to this as a /black swan/ event, which I believe comes >>> >from the field of economics.
And, to combine this topic with another one, since we were talking about >>>> compilers, in the 90s, prior to the publication of GCC 2.95 [1], it
would have been considered an /unknown unknown/ that compilers could be- >>>> come malicious to security sensitive programming. I bring you [2] as
exhibit A, and give the relevant quote.
The short and long is that, today, the only way to access a constant >>>> time implementation from Rust is to write said implementation in
assembly.
I'll add that this is about comparing security sensitive strings, us-
ually of fixed length [3], and /not/ an O( 1 ) algorithm.
You can read this poster's point about why LLVM is not a polite com-
piler at [2].
Now, if you want to argue this conclusion, you'll have to make an acc- >>>> ount on Stack Overflow, and comment there.
In other words, the only way to write constant time cryptography, is ba- >>>> sically to do it in assembly, if any of GCC, LLVM, or MSVC are to com- >>>> pile it.
In that sense, the /social contract/ between security sensitive program- >>>> ming, and compiler makers has been broken.
And since we are in sci.electronics.design, we can also add that hard- >>>> ware manufacturers typically do not assert in their manuals that a spe- >>>> cific instruction is constant time, so now we get to wait and see if any >>>> of the x86, or ARM, or maybe even RISC-V manufacturers bring back the
evil that was -- to my recollection -- the original 68000 shift instruc- >>>> tion which spent more clock time for larger shift values.
And to finish this off with a warning, I have read the above for adults, >>>> so if you less-than-jr-high-school reading comprehension isn't up to the >>>> task of figuring out what I'm saying, that's squarely on you.
Best wishes, and happy constant time algorithms!
[1] Given Anton Ertl's research.
[2]
https://stackoverflow.com/questions/44691363/how-to-compare-strings-in-constant-time
[3] Hashed passwords are always the same length, but if the length
changes, comparing them in constant time doesn't work; this should be
obvious.
I'm always impressed by how few programmers have even a rough idea of
how much time it takes to execute their code. Guessing off by 10:1 is
common.
I get a scope and measure it.
We have a 75-cent dual-core ARM making a 100 MHz square wave, lines of
c setting a port bit up and down.
than a Yamaha OPL chip? I guess they aren't made anymore, since I can't
find anything on digikey quickly with the keywords "YMF262." So I just
don't know how expensive they were.
Of course, I'm sure your 75-cent dual-core ARM chips is doing something
else too, but I got curious, and couldn't find a price.
It's an RP2040 Raspberry Pi chip. The Pi folks recently authorized
clocking the CPUs at 200 MHz.
It's a wonderful part. They did everything right. We call the two CPUs
Alice and Bob.
Some lunatic ran a RP2040 at 1 GHz in liquid nitrogen.
On Tue, 10 Nov 2026 16:49:55 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 10/11/2026 2:12 am, john larkin wrote:
On Mon, 9 Nov 2026 16:42:08 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 9/11/2026 6:27 am, Waldek Hebisch wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
And I'm sure that you are perfectly happy with all of them. Egomaniacs
do go around describing themself as "stable geniuses".
I wouldn't do that!
What's your definition of newbie?
Somebody who doesn't know enough about what he his doing to be aware of
the areas he doesn't know enough about. It's not so much about what you
know, as what you know about the limits of your knowledge.
Electronic design talent is reality-checked by what works.
This worked first build. One of my guys wants to change one resistor,
so I guess I'll let him.
https://www.dropbox.com/scl/fi/69wwpsoc0o47cidxwust7/B360_20260813_110116.jpg?rlkey=y0sxkzswmgj3wa9lvf9ihbdio&raw=1
Actually, we may change the big yellow polyfuse too. Manufacturing--
wants to kink the leads for solderability, but that lifts it up and
then it hits the top cover and then we'd have to bend it over and that
would look goofy.
Life sucks.
On 11/11/2026 2:53 am, john larkin wrote:
On Tue, 10 Nov 2026 16:49:55 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 10/11/2026 2:12 am, john larkin wrote:
On Mon, 9 Nov 2026 16:42:08 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 9/11/2026 6:27 am, Waldek Hebisch wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
<snip>
And I'm sure that you are perfectly happy with all of them. Egomaniacs
do go around describing themself as "stable geniuses".
I wouldn't do that!
So you've got more sense than Donald J. Trump - not a whole lot more, >because you think that he has "common sense".
What's your definition of newbie?
Somebody who doesn't know enough about what he his doing to be aware of
the areas he doesn't know enough about. It's not so much about what you
know, as what you know about the limits of your knowledge.
Electronic design talent is reality-checked by what works.
And how well it works. There's a lot of stuff around that works well
enough to sell, but not well enough to work all that well. I've cleaned
up a few marginal production designs in my time.
This worked first build. One of my guys wants to change one resistor,
so I guess I'll let him.
https://www.dropbox.com/scl/fi/69wwpsoc0o47cidxwust7/B360_20260813_110116.jpg?rlkey=y0sxkzswmgj3wa9lvf9ihbdio&raw=1
A picture of the board isn't all that informative. The 360 on the label >suggests that it is one more of your waveform generators. Practice
doesn't always make perfect - it tends to re-iterate the original poor >choices.
On 11/11/2026 2:42 am, john larkin wrote:
On Tue, 10 Nov 2026 18:38:47 +0800, Johann 'Myrkraverk' Oskarsson
<johann@myrkraverk.invalid> wrote:
On 11/10/2026 6:12 PM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
[...]
in areas where you are ignorant you
can end up looking pretty stupid to people who are less ignorant.
Conversely, in areas where you are knowledgeable, you can look
stupid to
people who are ignorant.
And this happens all the time.-a It's kind of better to be a /midwit/
than a genius [1].-a I've seen that a lot, in online /special interest/
groups, and be subject to such abuse myself.-a The problem when people
get abusive, and say someone is /incompetent/, is that they are gener-
ally wrong.-a First, the moron can learn, and become greater that the
person throwing the abuse.-a This is an effect of time.-a Second, the ab- >>> user rarely follows up with /why/ said abuse was thrown, so the receiver >>> is left to ponder -- is there something I don't know, or are you just a
moron?
Now, people been around the block a few times know that today's ignora-
mus can be a /jedi master/ in a few months, or years, and doesn't have
to tell the rest of the group about their knowledge accumulation.-a So
they always end up as /just another moron/ once the person knows better. >>>
This is called /lack of social skills/, and has real consequences.
Something some members of sci.electronics.design have yet to learn.
Best wishes, and happy jedi mastery!
[1] If we use that term, the meme with the IQ curve I'm referring to has >>> a /moron/ on the left, and a /jedi master/ on the right.-a The terms do
not matter so much as long as we're being understood.
Some people have extreme talents. It might be math, music, tennis,
whatever. Some part of their brain is six-sigma good, often at the
expense of other parts.
The saving grace of IQ testing is that if you good in one area you tend
to be good in others - not perhaps as exceptionally good, but still
better than average. It may be that what is being tested for is more the absence of actual brain damage rather than some kind of superior
processing.
The specialized-genius bit can also make them obnoxious.
Not in my experience.
On 11/11/2026 12:30 am, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 8:46 PM, Bill Sloman wrote:
On 10/11/2026 9:22 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 6:20 PM, Johann 'Myrkraverk' Oskarsson wrote:
And to finish this off with a warning, I have read the above forSorry, *written; I send before proof reading!
adults,
so if you less-than-jr-high-school reading comprehension isn't up
to the
task of figuring out what I'm saying, that's squarely on you.
"Sent" before proof reading. You imagine that you wrote your
pretentious twaddle for adults, not realising that the "adults" have
noticed that you don't have anything useful to say, and have mostly
got around to plonking you.
Speaking for yourself, are you?-a Because here in sci.electronics.design,
you're the only one plonking.-a And you're plonking everyone else.
"Plonking" is not reading messages from from the people plonked, and - obviously - not responding to them.
So you're the bully who has never faced the consequences of his own
actions.
I rarely plonk anybody. Some people I don't bother reading --a if they do post anything interesting other people will respond to it.
And I'm here now, and I'll take none of it silently.-a You are a fucking
bully, and you don't know it.
Far from it.
Now you do.
You want to tell other people that I'm a bully. I've been posting here
for thirty years now, so this would be well known if it were true, so it looks to me as if you are deceiving yourself.
And everyone else here in sci.electronics.design knew it
too but was too polite to tell you -- maybe.
Jim Thompson was rude enough to claim that he'd reported me to the FBI
for anti-American attitudes, which was a bit silly of him since I been security cleared to a level that had got me into US Army ECOM in 1970
(back when it was at Fort Monmouth, New Jersey).
I didn't read the 30 year backlog.
And wouldn't have understood it if you had.
Best wishes, and keep being miserable for the next fifty years -- at
least!
My statistical expectation of survival is rather shorter than that. I'd
have to become ten years older the longest surviving human ever has so
far to get there.
On 11/11/2026 11:54 AM, Bill Sloman wrote:
On 11/11/2026 2:42 am, john larkin wrote:
On Tue, 10 Nov 2026 18:38:47 +0800, Johann 'Myrkraverk' Oskarsson
<johann@myrkraverk.invalid> wrote:
On 11/10/2026 6:12 PM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
Some people have extreme talents. It might be math, music, tennis,
whatever. Some part of their brain is six-sigma good, often at the
expense of other parts.
The saving grace of IQ testing is that if you good in one area you
tend to be good in others - not perhaps as exceptionally good, but
still better than average. It may be that what is being tested for is
more the absence of actual brain damage rather than some kind of
superior processing.
The specialized-genius bit can also make them obnoxious.
Not in my experience.
You are the obnoxious /specialized genius/, so of course you wouldn't
notice it.
The /obvious problem/ with IQ testing is that it only tests forfamiliar with
particular types of puzzles solved.-a To be clear, the experience of it.
So people with certain life experience tend to score higher than people without such life experiences.-a This has been a contention among > politically aligned people in recent years, so I'm sure you're
the phenomenon.
I could write more, but there's no point.-a /Why bother/.-a You're just a stubborn thick headed obnoxious self important academician who's deter-
mined not to learn from people with life experiences different from
yours.
Best wishes, and stay miserable!
Don Y <blockedofcourse@foo.invalid> wrote:No one (responsibly) builds things using modern C. Because
On 11/8/2026 12:27 PM, Waldek Hebisch wrote:
You clearly go into area were you are not an expert. Google a
bit about "undefined behaviour" in C and you will learn that
when source code makes no sense, then C compier can do
essentially anything, which in not so rare cases means that
compiler simply deletes what programmer wrote. Explicit nop-s
The compiler doesn't have THAT much license. It can't decide to
implement arbitrary operations just because you APPEAR to be
relying on a behavior that is undefined.
Compiler just uses rules, so writing about appearence makes no
sense. When optimizing compier performs a lot of transformations.
Validity of transformations may depend on conditions. When
checking conditions compiler assumes that program does not
contain undefined behaviour.
And yes, C standard gives such freedom to authors of C
compilers:
: undefined behavior
: behavior, upon use of a nonportable or erroneous program construct
: or of erroneous data, for which this document imposes no requirements
Do I need to explain to you what "no requirements" mean?
|------------------------------------------------------------------|
|"Or, that |
|"hard" is "more difficult" than "soft" (the opposite is true -- in|
|spades [. . .] |
|[. . .] |
| |
|[. . .]" | |------------------------------------------------------------------|
How do you mean?
On 11/11/2026 2:42 am, john larkin wrote:
On Tue, 10 Nov 2026 18:38:47 +0800, Johann 'Myrkraverk' Oskarsson
<johann@myrkraverk.invalid> wrote:
On 11/10/2026 6:12 PM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
[...]
in areas where you are ignorant you
can end up looking pretty stupid to people who are less ignorant.
Conversely, in areas where you are knowledgeable, you can look stupid to >>>> people who are ignorant.
And this happens all the time. It's kind of better to be a /midwit/
than a genius [1]. I've seen that a lot, in online /special interest/
groups, and be subject to such abuse myself. The problem when people
get abusive, and say someone is /incompetent/, is that they are gener-
ally wrong. First, the moron can learn, and become greater that the
person throwing the abuse. This is an effect of time. Second, the ab-
user rarely follows up with /why/ said abuse was thrown, so the receiver >>> is left to ponder -- is there something I don't know, or are you just a
moron?
Now, people been around the block a few times know that today's ignora-
mus can be a /jedi master/ in a few months, or years, and doesn't have
to tell the rest of the group about their knowledge accumulation. So
they always end up as /just another moron/ once the person knows better. >>>
This is called /lack of social skills/, and has real consequences.
Something some members of sci.electronics.design have yet to learn.
Best wishes, and happy jedi mastery!
[1] If we use that term, the meme with the IQ curve I'm referring to has >>> a /moron/ on the left, and a /jedi master/ on the right. The terms do
not matter so much as long as we're being understood.
Some people have extreme talents. It might be math, music, tennis,
whatever. Some part of their brain is six-sigma good, often at the
expense of other parts.
The saving grace of IQ testing is that if you good in one area you tend
to be good in others - not perhaps as exceptionally good, but still
better than average. It may be that what is being tested for is more the >absence of actual brain damage rather than some kind of superior
processing.
The specialized-genius bit can also make them obnoxious.
Not in my experience.
On 11/11/2026 7:41 am, john larkin wrote:
On Wed, 11 Nov 2026 02:21:09 +0800, Johann 'Myrkraverk' Oskarsson
<johann@myrkraverk.invalid> wrote:
On 11/10/2026 11:59 PM, john larkin wrote:
On Tue, 10 Nov 2026 18:20:58 +0800, Johann 'Myrkraverk' OskarssonNow, please excuse my ignorance here [1], is that more or less expensive >>> than a Yamaha OPL chip? I guess they aren't made anymore, since I can't >>> find anything on digikey quickly with the keywords "YMF262." So I just
<johann@myrkraverk.invalid> wrote:
On 11/10/2026 1:49 PM, Bill Sloman wrote:
On 10/11/2026 2:12 am, john larkin wrote:
On Mon, 9 Nov 2026 16:42:08 +1100, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:
On 9/11/2026 6:27 am, Waldek Hebisch wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown >>>>>>>>>>>>>>>> <'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. >>>>>>>>>>>>>>>>> Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are over >>>>>>>>>>>>>>> 3000
and they keep coming.
Real men code in binary using the front panel switches. >>>>>>>>>>>>>>
I actually used a PDP-7 where you really did have to bootstrap >>>>>>>>>>>>>> it that
way to read in a paper tape. It was a fun machine as it had a >>>>>>>>>>>>>> vector
graphics display so was very good for asteroids, but cheated at >>>>>>>>>>>>>> chess.
I did a lot of stuff in PDP-11 and 68K assembly languages. With >>>>>>>>>>>>> a few
macros, they are almost higher-level languages.
All high level languages get compiled into assembly language >>>>>>>>>>>> before they
can be run on a computer.
Well, no.
Counter-example?
As a compiler, you do seem to be sub-optimal, if not downright >>>>>>>>>> afunctional. Ignoring implications you don't like isn't an option >>>>>>>>>> for aBeing a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into >>>>>>>>>>>> something
that can be run on hardware (which will have an architecture - it is
constructed from components that have been connected by some kind of
architect).
If that post were compiled to assembly language, it would be a nop. >>>>>>>>>>
compiler. There can be functions they can't parse - in your case don't
want to parse - but that doesn't generate a nop.
You clearly go into an area where you are not an expert.
I'm not pretending to be an expert, just less of a clueless newbie in >>>>>>>> the area that John Larkin has shown himself to be.
I've written several compilers and several RTOS's and a bunch of >>>>>>> system simulators and hundreds of application programs, a good chunk >>>>>>> of a million lines of code. From PDP8 to ARM and one CPU that I
designed myself.
And I'm sure that you are perfectly happy with all of them. Egomaniacs >>>>>> do go around describing themself as "stable geniuses".
What's your definition of newbie?
Somebody who doesn't know enough about what he his doing to be aware of >>>>>> the areas he doesn't know enough about. It's not so much about what you >>>>>> know, as what you know about the limits of your knowledge.
And then we have the military term "unknown unknown." For instance in >>>>> business, you cannot prevent someone from inventing something else, that >>>>> completely obsoletes your business.
In /tech/, this is not an unknown unknown, because it's been done so >>>>> many times in living memory. It can still happen in other fields, com- >>>>> pletely blind-sighting the billionaires in charge of it.
Some people refer to this as a /black swan/ event, which I believe comes >>>> >from the field of economics.
And, to combine this topic with another one, since we were talking about >>>>> compilers, in the 90s, prior to the publication of GCC 2.95 [1], it
would have been considered an /unknown unknown/ that compilers could be- >>>>> come malicious to security sensitive programming. I bring you [2] as >>>>> exhibit A, and give the relevant quote.
The short and long is that, today, the only way to access a constant >>>>> time implementation from Rust is to write said implementation in >>>>> assembly.
I'll add that this is about comparing security sensitive strings, us- >>>>> ually of fixed length [3], and /not/ an O( 1 ) algorithm.
You can read this poster's point about why LLVM is not a polite com- >>>>> piler at [2].
Now, if you want to argue this conclusion, you'll have to make an acc- >>>>> ount on Stack Overflow, and comment there.
In other words, the only way to write constant time cryptography, is ba- >>>>> sically to do it in assembly, if any of GCC, LLVM, or MSVC are to com- >>>>> pile it.
In that sense, the /social contract/ between security sensitive program- >>>>> ming, and compiler makers has been broken.
And since we are in sci.electronics.design, we can also add that hard- >>>>> ware manufacturers typically do not assert in their manuals that a spe- >>>>> cific instruction is constant time, so now we get to wait and see if any >>>>> of the x86, or ARM, or maybe even RISC-V manufacturers bring back the >>>>> evil that was -- to my recollection -- the original 68000 shift instruc- >>>>> tion which spent more clock time for larger shift values.
And to finish this off with a warning, I have read the above for adults, >>>>> so if you less-than-jr-high-school reading comprehension isn't up to the >>>>> task of figuring out what I'm saying, that's squarely on you.
Best wishes, and happy constant time algorithms!
[1] Given Anton Ertl's research.
[2]
https://stackoverflow.com/questions/44691363/how-to-compare-strings-in-constant-time
[3] Hashed passwords are always the same length, but if the length
changes, comparing them in constant time doesn't work; this should be >>>>> obvious.
I'm always impressed by how few programmers have even a rough idea of
how much time it takes to execute their code. Guessing off by 10:1 is
common.
I get a scope and measure it.
We have a 75-cent dual-core ARM making a 100 MHz square wave, lines of >>>> c setting a port bit up and down.
don't know how expensive they were.
Of course, I'm sure your 75-cent dual-core ARM chips is doing something
else too, but I got curious, and couldn't find a price.
It's an RP2040 Raspberry Pi chip. The Pi folks recently authorized
clocking the CPUs at 200 MHz.
It's a wonderful part. They did everything right. We call the two CPUs
Alice and Bob.
Some lunatic ran a RP2040 at 1 GHz in liquid nitrogen.
What's lunatic about that? Liquid nitrogen is cheap and freely
available. 1GHz processors aren't.
On 11/11/2026 12:21 PM, Bill Sloman wrote:
On 11/11/2026 12:30 am, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 8:46 PM, Bill Sloman wrote:
On 10/11/2026 9:22 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 6:20 PM, Johann 'Myrkraverk' Oskarsson wrote:
Best wishes, and keep being miserable for the next fifty years -- at
least!
My statistical expectation of survival is rather shorter than that.
I'd have to become ten years older than longest surviving human ever
has so far to get there.
Don't let the statistical expectation stop you.
I mean, /I want you/ to
be here fifty years from now, and still posting your miserable drivel on sci.electronics.design, to the delight of the lurkers who simply enjoy
the consumption of popcorn and coca-cola.-a A good tradition among movie goers going back decades, if not centuries.
Bill Sloman <bill.sloman@IEEE.org> wrote: |-------------------------------------------------|
|"[. . .] my mobile |
|phone (which I do keep in my hip pocket). [. . .]|
|[. . .]" | |-------------------------------------------------|
When and why did this stop being illegal in Australia?
(S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
On Wed, 11 Nov 2026 14:54:11 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 11/11/2026 2:42 am, john larkin wrote:
On Tue, 10 Nov 2026 18:38:47 +0800, Johann 'Myrkraverk' Oskarsson
<johann@myrkraverk.invalid> wrote:
On 11/10/2026 6:12 PM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
The saving grace of IQ testing is that if you good in one area you tend
to be good in others - not perhaps as exceptionally good, but still
better than average. It may be that what is being tested for is more the
absence of actual brain damage rather than some kind of superior
processing.
The specialized-genius bit can also make them obnoxious.
Not in my experience.
Sometimes you actually, probably accidentally, approach humor.
On 11/10/2026 5:14 AM, Waldek Hebisch wrote:
Actually, at '-O2' version of 'gcc' that I use replaces explicit
division by 0 by the 'ud2' instruction.
Shouldn't that be considered /erroneous compilation/?-a I mean, you can
write a signal handler that catches all signals, and isn't /division by
zero/ one of the Posix signals?-a Is the compiler prescient and makes
sure this only happens if the binary is ever run when the user isn't ex- plictly expecting a division by zero -- rather than /invalid opcode/?
Does the question bother you?-a Am I too high, or too low on the /moron/
vs. /jedi master/ axis to be understood?-a Should we put all the GCC devs
in therapy for believing they are prescient?
You have to THINK about the problem instead of just naivelyHere's a simple, practical example that illustrates the costs and
assuming everything is important.
When deadlines are soft, the "value" of a task's completion
is no longer bi-valued (value vs. no value at all) but, rather,
some potentially complex function of lateness.-a Your goal,
then, is to sort out how to shuffle resources to "maximize value"
(across the set of tasks) instead of the all-or-nothing decision
that HRT suggests.
An SRT design tends to embed more intelligence in the
goal setting and resource management.-a You *shed*
tasks for which resource expenditure provides little
*value* at the possible expense of other MORE valuable
tasks.
On 11/10/2026 5:09 PM, Johann 'Myrkraverk' Oskarsson wrote:
On 11/11/2026 5:27 AM, ehsjr wrote:
On 11/10/2026 5:12 AM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
[...]
in areas where you are ignorant you
can end up looking pretty stupid to people who are less ignorant.
Conversely, in areas where you are knowledgeable, you can look
stupid to
people who are ignorant.
And some who are knowledgeable use that knowledge stupidly,
and can look stupid to most everyone, ignorant or not.
A closed mouth gathers no foot.
Ed
While I am not certain that trying to /appear not stupid/ is a virtue.
Sometimes it's quite useful to get corrections from people who know
better.-a Other times, people use that /perceived stupidity/ to heap
abuse upon the unsuspecting enquirer, with predictable results.
How pathetic to use one's (supposedly superior) intellect to heap
abuse on the unsuspecting enquirer.-a It besmirches the one doing
the heaping. What a waste of time and effort.
Instead, the knowledgeable person could choose to express helpful
ideas. For example, I like reading posts from Liz.-a She is highly knowledgeable; I've never seen her heap abuse.-a Rather, what she
has to say can be helpful to those interested in the area she's
posting about.
In any case, trying to use /knowledge/ as a status symbol seems quite
stupid to me; yet a lot of people behave this way.
On 11/9/2026 2:14 PM, Waldek Hebisch wrote:
Don Y <blockedofcourse@foo.invalid> wrote:No one (responsibly) builds things using modern C. Because
On 11/8/2026 12:27 PM, Waldek Hebisch wrote:
You clearly go into area were you are not an expert. Google a
bit about "undefined behaviour" in C and you will learn that
when source code makes no sense, then C compier can do
essentially anything, which in not so rare cases means that
compiler simply deletes what programmer wrote. Explicit nop-s
The compiler doesn't have THAT much license. It can't decide to
implement arbitrary operations just because you APPEAR to be
relying on a behavior that is undefined.
Compiler just uses rules, so writing about appearence makes no
sense. When optimizing compier performs a lot of transformations.
Validity of transformations may depend on conditions. When
checking conditions compiler assumes that program does not
contain undefined behaviour.
And yes, C standard gives such freedom to authors of C
compilers:
: undefined behavior
: behavior, upon use of a nonportable or erroneous program construct
: or of erroneous data, for which this document imposes no requirements
Do I need to explain to you what "no requirements" mean?
it is not a "practical" (as in "suitable for PRACTICE") language.
The same bit of source code written in a particular language
should result in the same general behavior regardless of processor
or compiler choice.
That contract was broken by C more than 20 years ago.
C is now an academic exercise and playground for c.l.c types.
All of my colleagues use C89 or K&R -- because we have to be able
to PROVE that the source code that the customer receives and
systematically reviews corresponds with what is happening in the
hardware.
Any "optimizations" have to be relatively trivial and intuitive
and visible at the preprocessor stage; the preprocessed output
should accuraely define what the code ACTUALLY does, not what the
developer HOPES it will do (subject to the compiler-writer's
whims).
Loop unrolling, function inlining, constant folding, constant
subexpression elimination, etc. -- all things that are OBVIOUS to
someone inspecting the source ("Yes, I understand that STRINGLENGTH+1
is intended to account for the NUL termination in a more visible manner"
or "OK, I see 3+3+4+1 is a good way of representing a telephone number"
or "Yeah, I guess you could do those steps N (constant) times in a row instead of wrapping them in a loop that is executed N times")
In that way, the "source" is a writing shorthand but one that still completely constrains the implementation.
E.g., I use a construct:
object=>method(arguments)
liberally in my code. The language doesn't support it (of course).
But, it is known to be a representational shorthand -- something to
unclutter the code and highlight the actual operation being performed.
There is no surprise when you look at the preprocessor output...
for ANY instance of such an expression.
Even the optimizing IDL compiler is obvious in the "optimizations"
that it makes (e.g., choosing effective marshalling sequences instead
of leaving that up to the developer)
On 11/11/2026 2:27 pm, ehsjr wrote:
On 11/10/2026 5:09 PM, Johann 'Myrkraverk' Oskarsson wrote:
On 11/11/2026 5:27 AM, ehsjr wrote:
On 11/10/2026 5:12 AM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
[...]
in areas where you are ignorant you
can end up looking pretty stupid to people who are less ignorant.
Conversely, in areas where you are knowledgeable, you can look
stupid to
people who are ignorant.
And some who are knowledgeable use that knowledge stupidly,
and can look stupid to most everyone, ignorant or not.
A closed mouth gathers no foot.
Ed
While I am not certain that trying to /appear not stupid/ is a virtue.
Sometimes it's quite useful to get corrections from people who know
better.-a Other times, people use that /perceived stupidity/ to heap
abuse upon the unsuspecting enquirer, with predictable results.
How pathetic to use one's (supposedly superior) intellect to heap
abuse on the unsuspecting enquirer.-a It besmirches the one doing
the heaping. What a waste of time and effort.
What's being complained about here isn't so much "heaping abuse" as not providing the level of flattery that some posters feel they deserve.
Instead, the knowledgeable person could choose to express helpful
ideas. For example, I like reading posts from Liz.-a She is highly
knowledgeable; I've never seen her heap abuse.-a Rather, what she
has to say can be helpful to those interested in the area she's
posting about.
She is frequently helpful.
In any case, trying to use /knowledge/ as a status symbol seems quite
stupid to me; yet a lot of people behave this way.
Correcting errors isn't "using knowledge as a status symbol", except in
the sense that being able to correct errors does involve asserting a superior status, but since the alternative is to leave errors unremarked
and uncorrected, it is also taking responsibility.
No one (responsibly) builds things using modern C. BecauseThe compiler doesn't have THAT much license. It can't decide to
implement arbitrary operations just because you APPEAR to be
relying on a behavior that is undefined.
Compiler just uses rules, so writing about appearence makes no
sense. When optimizing compier performs a lot of transformations.
Validity of transformations may depend on conditions. When
checking conditions compiler assumes that program does not
contain undefined behaviour.
And yes, C standard gives such freedom to authors of C
compilers:
: undefined behavior
: behavior, upon use of a nonportable or erroneous program construct
: or of erroneous data, for which this document imposes no requirements
Do I need to explain to you what "no requirements" mean?
it is not a "practical" (as in "suitable for PRACTICE") language.
The "problem" first appeared in context of optimizing Fortran
compliers and AFAIK while wording is different and specific
conditions differs in effect Fortran standard allows the
same. Also Pascal standard. IIUC Ada mandates runtime checks
for a lot of things and many other things lead to compile time
errors. But programmer determided to write programs in C
style still can inject equivalent of undefined behaviour with
consequences the same as in C.
AFAIK a lot of folks use C for important software. Some claim
that their code contains no bugs, so in particular no undefiend
behaviour. Some use tools like CompCert. IIUC some safety
standard certify _object_ code, it does not matter how good or
buggy is C compiler that generated object code, you are
supposed to review generated code and verify that it is doing
what it is supposed to do (and presumably you need to keep
appropriate document trail to show that you really did that).
Some people think that software is serious when it brings money
to its creators. AFAIK most optimizations in gcc and clang
are funded by commercial companies which see gains from
those optimizations. Most of this is motivated by C++,
where you really need those optimizations for decent speed.
But problems with undefined bahaviour are almost the same.
The same bit of source code written in a particular language
should result in the same general behavior regardless of processor
or compiler choice.
It will, if it is defined code.
That contract was broken by C more than 20 years ago.
C is now an academic exercise and playground for c.l.c types.
All of my colleagues use C89 or K&R -- because we have to be able
to PROVE that the source code that the customer receives and
systematically reviews corresponds with what is happening in the
hardware.
Use of K&R C for new code looks irresponsible to me: checking that
code accepted by K&R compiler has no bugs is more effort than
the same for modern C. C89 looks reasonable, but it gains you
a little. Main thing are compilers. There are two mainstream
ones with multiple targets, that is gcc and clang. There were
few respectable compilers from specific vendors targeting their
targets, but most seem to be gone now. And all compilers beside
gcc and clang seem to get much less use and consequently are
less tested.
When using C compiler you may have trouble for various reasons.
One thing are ordinary bugs in C code. Other thing are bugs
which cause undefined behaviour. Third thing are compiler bugs,
when source code is well defined, but compiler produces wrong
object code. AFAICS modern compilers are much more helpful
with catching ordinary bugs. Concerning wrong code, they
seem to be better, but larger size of compiler and increased
complexity may leave some doubts. Undefined behaviour could
catch you even 35 years ago: at that time users complained
that their working code is broken by new C compilers. Users
learned that old code was wrong and how to write correct
code. I do not see much difference now: you learn to write
code in a different way, which has additional advantage that
code avoinding risky constructs usually is also clearer.
Any "optimizations" have to be relatively trivial and intuitive
and visible at the preprocessor stage; the preprocessed output
should accuraely define what the code ACTUALLY does, not what the
developer HOPES it will do (subject to the compiler-writer's
whims).
You preach specifications yet you have trouble that compiler also
have specification. Stay withing specified (defined) constructs
and your code will have expected effect. If you expect more
than is specified, then you expect too much.
Concerning "what the code ACTUALLY does", I expect compiler
to delete checks that are known to pass at compile time
(such checks may be generated from macros and I want to keep
my macros). I expect compiler to expand inline simple functions,
when it leads to smaller code size. In general generated
code may look quite different than expectation of some
folks. What counts is the effect.
For delay loop I have assembly code: C compiler may and shouldThe compiler understands the target hardware. The preprocessor
collapse to nothing loops that take time but otherwise do not
contribute to the result. And I find atempts to cripple
optimization in order to preserve delay loop to be too
unreliable. But otherwise C allows me to write what
should be done and compiler generates appropriate code.
Loop unrolling, function inlining, constant folding, constant
subexpression elimination, etc. -- all things that are OBVIOUS to
someone inspecting the source ("Yes, I understand that STRINGLENGTH+1
is intended to account for the NUL termination in a more visible manner"
or "OK, I see 3+3+4+1 is a good way of representing a telephone number"
or "Yeah, I guess you could do those steps N (constant) times in a row
instead of wrapping them in a loop that is executed N times")
In that way, the "source" is a writing shorthand but one that still
completely constrains the implementation.
E.g., I use a construct:
object=>method(arguments)
liberally in my code. The language doesn't support it (of course).
But, it is known to be a representational shorthand -- something to
unclutter the code and highlight the actual operation being performed.
There is no surprise when you look at the preprocessor output...
for ANY instance of such an expression.
Even the optimizing IDL compiler is obvious in the "optimizations"
that it makes (e.g., choosing effective marshalling sequences instead
of leaving that up to the developer)
That is slightly different thing. Optimizations require some effort.
If you have preprocessor/precompiler it makes no sense to duplicate optimizations done by C compiler. Only things that C compiler
can not optimize are worth optimization in a precompiler and only
when they are important enough. More optimizations in C compiler
means that your precompiler may be simpler. For example
precompiler may naively insert code trusting that C compiler
will remove it in cases where it is not needed.
Don Y <blockedofcourse@foo.invalid> wrote: |--------------------------------------------------------------|
|"Perhaps we should let hardware people write code and publicly|
|critique their failures? Or, let software people design the |
|hardware and let the hardware folks write the code??" | |--------------------------------------------------------------|
VHDL
(S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
On 10/11/2026 10:02 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 5:14 AM, Waldek Hebisch wrote:
Actually, at '-O2' version of 'gcc' that I use replaces explicit
division by 0 by the 'ud2' instruction.
Shouldn't that be considered /erroneous compilation/?-a I mean, you can
write a signal handler that catches all signals, and isn't /division by
zero/ one of the Posix signals?-a Is the compiler prescient and makes
sure this only happens if the binary is ever run when the user isn't ex-
plictly expecting a division by zero -- rather than /invalid opcode/?
Does the question bother you?-a Am I too high, or too low on the /moron/
vs. /jedi master/ axis to be understood?-a Should we put all the GCC devs
in therapy for believing they are prescient?
I imagine that there are situations where the programmer can be
confident that the divisor is never going to be zero.
A cautious programmer might test for a zero divisor and run an error recovery routine rather than doing the division.
To me it does look as if you've posted an under-informed response.
On 11/11/2026 2:50 PM, Don Y wrote:
You have to THINK about the problem instead of just naively
assuming everything is important.
When deadlines are soft, the "value" of a task's completion
is no longer bi-valued (value vs. no value at all) but, rather,
some potentially complex function of lateness.-a Your goal,
then, is to sort out how to shuffle resources to "maximize value"
(across the set of tasks) instead of the all-or-nothing decision
that HRT suggests.
An SRT design tends to embed more intelligence in theHere's a simple, practical example that illustrates the costs and
goal setting and resource management.-a You *shed*
tasks for which resource expenditure provides little
*value* at the possible expense of other MORE valuable
tasks.
value of a single "task" and how it might be instantiated:
E.g., if I want to "water the citrus", I need the hardware interface to the irrigation valves that is present on the irrigation controller.-a Otherwise, I can't "gate" water to that portion of the yard.-a I need the "grey water" supply and its metering hardware (another node) to source the water.-a And, possibly, the municipal water supply and its metering hardware -- in the event that-a there is insufficient grey water available.
I need the database that tracks weather history so I can determine how *much*
water will be required (based on precipitation, temperatures, wind, etc.).
If it rained recently -- or, if it has been hot/windy/dry -- then the current
needs of those plants will differ.
And, I need memory and "MIPS-seconds" on each of these nodes to actually do the "work" required.-a So, those devices must be powered up and have sufficient
"spare" resources to host the activities that I will require of them.
During daylight hours, I'll likely have a surplus of electrical power (assuming the power system's estimate of the remaining available solar
power will suffice to top of the storage batteries).-a At night, power
may be in shorter supply (or, "more costly" so this has to be justified
by the "value" of getting the task accomplished!).-a OTOH, irrigation is
more effective at night as evaporative losses are greatly reduced and
the flora will be most receptive to water uptake as the sun rises.
OToOH, if the power has failed, then power will be even more precious; perhaps risk the fruit taking a hit so some more important task can be accomplished?
The scheduler now has to find a time when those resources are available
(or, can be MADE available -- powering hardware on if presently off,
evicting jobs of lower priority, etc.) and then admit the task to the
run queue.
*Hoping* that conditions don't change significantly before it finishes
(a minute from now, an occupant may want to take a shower and the drop
in water pressure caused by the huge load represented by the citrus
might be objectionable -- so, that task will have to be paused or
aborted)
If I had taken the attitude that "everything is important and of immediate need", then I would have had to increase the size of the grey water tank
(and the pump and piping that distributes its contents as I might have had
to irrigate EVERYTHING on the property at the same instant!), the diameter
of the municipal water main to handle those cases where the grey water
supply was inadequate, the size of the storage battery in case lots of things
wanted to happen "after dark", the number and capabilities of the CPUs
doing the work, etc.
[Irrigation is much easier for people to wrap their heads around than
the effort and resources required to train a speech model or update a
scene analysis, hence my reliance on it as an example]
This, of course, is just stupid.-a A smarter approach is to juggle priorities
so you can do everything with *less*.-a By recognizing that not everything has to happen immediately.-a By treating most "deadlines" as ADVISORY and
not HARD REQUIREMENTS.
[You can see there are far more design decisions involved in this
approach!]
[Irrigation is much easier for people to wrap their heads around than
the effort and resources required to train a speech model or update a
scene analysis, hence my reliance on it as an example]
This, of course, is just stupid.-a A smarter approach is to juggle priorities
so you can do everything with *less*.-a By recognizing that not everything >> has to happen immediately.-a By treating most "deadlines" as ADVISORY and
not HARD REQUIREMENTS.
[You can see there are far more design decisions involved in this approach!]
Thank you.-a My SO has plants as a hobby, but I have not thought to
create automated irrigation systems, so this example hits perfectly
home.
One thing you can add is the failure mode: when the irrigation system completely gives up, it can decide to /phone home/ and irritate a human.
That said, it's also best to keep a mark-one-eyeball on the growing
plants, and not be completely dependent upon an automated system that
can decide to fail silently.-a Such as if someone steals the battery.
In any case, trying to use /knowledge/ as a status symbol seems quite
stupid to me; yet a lot of people behave this way.
Correcting errors isn't "using knowledge as a status symbol", except in
the sense that being able to correct errors does involve asserting a superior status, but since the alternative is to leave errors unremarked
and uncorrected, it is also taking responsibility.
It does level the playing field, but if you write VHDL as if you're
doing software, you kind of fail.-a At least, that's what I got from the
free VHDL book I found online a few years ago.
Personally, I think it's very instructive to design and implement a
circuit using 74xx logic and a breadboard.-a At least, that hammers home
that you're designing hardware, and not just writing software.
There are some more intricacies involved, such as -- and I never exper- ienced this -- is wires so close together they become capacitors, or something along those lines.-a It was just one of these off hand remarks
by the teachers in my /coding school/.-a And then I never took any of the more advanced electronics classes, as they weren't in my curriculum.
So I have a lot to catch up on, if I'm to do this for real.
On 11/12/2026 10:31 PM, Bill Sloman wrote:
In any case, trying to use /knowledge/ as a status symbol seems quite
stupid to me; yet a lot of people behave this way.
Correcting errors isn't "using knowledge as a status symbol", except
in the sense that being able to correct errors does involve asserting
a superior status, but since the alternative is to leave errors
unremarked and uncorrected, it is also taking responsibility.
Of course you think so, but leaving errors is fine too.
-aAfter all, I'm not being paid to educate you on the errors of your ways.
On 11/12/2026 12:35 PM, Bill Sloman wrote:
On 10/11/2026 10:02 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 5:14 AM, Waldek Hebisch wrote:
Actually, at '-O2' version of 'gcc' that I use replaces explicit
division by 0 by the 'ud2' instruction.
Shouldn't that be considered /erroneous compilation/?-a I mean, you can
write a signal handler that catches all signals, and isn't /division by
zero/ one of the Posix signals?-a Is the compiler prescient and makes
sure this only happens if the binary is ever run when the user isn't ex- >>> plictly expecting a division by zero -- rather than /invalid opcode/?
Does the question bother you?-a Am I too high, or too low on the /moron/ >>> vs. /jedi master/ axis to be understood?-a Should we put all the GCC devs >>> in therapy for believing they are prescient?
I imagine that there are situations where the programmer can be
confident that the divisor is never going to be zero.
A cautious programmer might test for a zero divisor and run an error
recovery routine rather than doing the division.
To me it does look as if you've posted an under-informed response.
You should try to write a signal handler that looks at the offending instruction or something.
On 12/11/2026 11:50 am, john larkin wrote:
On Wed, 11 Nov 2026 14:54:11 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 11/11/2026 2:42 am, john larkin wrote:
On Tue, 10 Nov 2026 18:38:47 +0800, Johann 'Myrkraverk' Oskarsson
<johann@myrkraverk.invalid> wrote:
On 11/10/2026 6:12 PM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
The saving grace of IQ testing is that if you good in one area you tend
to be good in others - not perhaps as exceptionally good, but still
better than average. It may be that what is being tested for is more the >>> absence of actual brain damage rather than some kind of superior
processing.
The specialized-genius bit can also make them obnoxious.
Not in my experience.
Sometimes you actually, probably accidentally, approach humor.
Back in about 1968 I wrote a few scripts for the Melbourne University Architects Revue. Some of them got into the revue and got laughs. Rowan Atkinson did much better when he was at Cambridge, and dropped his
master's degree in electronics in favour of a theatrical career.
Your own credentials as a judge of humour are even less impressive.
There were a few specialised genius types around EMI Central Research
when I worked there, and only one of them was obnoxious. It wasn't his genius that was the problem, but his irresponsible antics.
William S. Percival was probably cleverer, but quite easy to get on with.
https://en.wikipedia.org/wiki/Distributed_amplifier
On 11/12/2026 4:55 AM, C||il|!n Niocl|is|!n Glost|-ir wrote:
Don Y <blockedofcourse@foo.invalid> wrote:
|--------------------------------------------------------------|
|"Perhaps we should let hardware people write code and publicly|
|critique their failures?-a Or, let software people design the-a |
|hardware and let the hardware folks write the code??"-a-a-a-a-a-a-a-a |
|--------------------------------------------------------------|
VHDL
(S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
It does level the playing field, but if you write VHDL as if you're
doing software, you kind of fail.-a At least, that's what I got from the
free VHDL book I found online a few years ago.
Personally, I think it's very instructive to design and implement a
circuit using 74xx logic and a breadboard.-a At least, that hammers home
that you're designing hardware, and not just writing software.
There are some more intricacies involved, such as -- and I never
experienced this -- is wires so close together they become capacitors,
or something along those lines.
It was just one of these off hand remarks
by the teachers in my /coding school/.-a And then I never took any of the more advanced electronics classes, as they weren't in my curriculum.
So I have a lot to catch up on, if I'm to do this for real.
On 11/12/2026 1:58 PM, Johann 'Myrkraverk' Oskarsson wrote:
It does level the playing field, but if you write VHDL as if you're
doing software, you kind of fail.-a At least, that's what I got from the
free VHDL book I found online a few years ago.
Hardware works in parallel.-a Most software people think serially;
this is why multithreading and multiprocessing are such stumbling
blocks for neophytes.
But, hardware makes things like hazzards and races more obvious.
When you encounter them in your software, you can understand
their analogs if you have a hardware background.
Likewise, atomic operations.
Personally, I think it's very instructive to design and implement a
circuit using 74xx logic and a breadboard.-a At least, that hammers home
that you're designing hardware, and not just writing software.
The problem with hardware is that it IS hardware.-a You actually need physical devices if you want to BUILD a prototype.
The advantage to VHDL and other simulation technologies is you can
*emulate* the hardware to see how it works (as well as how it fails
to work) without having to invest all that time and hassle.
There's nothing worse than being handed a prototype that someone
built incorrectly and you now have to debug their assembly errors
before you can examine the behavior of your circuit.
There are some more intricacies involved, such as -- and I never
experienced this -- is wires so close together they become capacitors, or
something along those lines.-a It was just one of these off hand remarks
by the teachers in my /coding school/.-a And then I never took any of the
more advanced electronics classes, as they weren't in my curriculum.
When I was working with large wirewrap panels (think 10+ square feet
per panel), we also had to worry about "cold flow" if the wires were
pulled too tight as the panel was wrapped.-a For "hand wrapped" panels,
you had to rely on the skillset of the technician.
[I still have my two WW guns, slit-n-wrap bits, no-niks, needle-nose strippers (worth their weight in gold!) and embroidery hooks!]
So I have a lot to catch up on, if I'm to do this for real.
On 11/12/2026 2:16 PM, Johann 'Myrkraverk' Oskarsson wrote:
[Irrigation is much easier for people to wrap their heads around than
the effort and resources required to train a speech model or update a
scene analysis, hence my reliance on it as an example]
This, of course, is just stupid.-a A smarter approach is to juggle
priorities
so you can do everything with *less*.-a By recognizing that not
everything
has to happen immediately.-a By treating most "deadlines" as ADVISORY and >>> not HARD REQUIREMENTS.
[You can see there are far more design decisions involved in this
approach!]
Thank you.-a My SO has plants as a hobby, but I have not thought to
create automated irrigation systems, so this example hits perfectly
home.
Irrigation (for folks who don't want "natural" landscapes) is essential
here as we don't get much precipitation.-a If you don't water it (whatever "it" happens to be), then it likely dies.
Except the weeds, of course!
One thing you can add is the failure mode: when the irrigation system
completely gives up, it can decide to /phone home/ and irritate a human.
My goal is to address the needs of people later in life who may not *remember* to irrigate -- which would lead to plants needing to be
replaced or removed and a decrease in the value of the property.
Not to mention the value to the resident.
That said, it's also best to keep a mark-one-eyeball on the growing
plants, and not be completely dependent upon an automated system that
can decide to fail silently.-a Such as if someone steals the battery.
No batteries.-a But, there are many failure modes that you can
detect (if so instrumented).
E.g., I watch the rate of water consumption while irrigating.
No idea what it *should* be (numerically) BUT it should be
very similar to what it was the last time this "zone" was
irrigated.-a-a An increase could represent an emitter that
has come off (allowing water to flow at a higher rate than
prescribed) or a failed distribution line.-a A decrease
could mean a clogged emitter or blocked distribution line.
A traditional (non-instrumented) irrigation system would
rely on the user (resident) to "notice" these things, either
by noting unexpected pools of water (or "gushers") or
plants that are dried out (or overwatered).-a Expecting a
resident to be capable of noticing these things *and* to
actually notice them time can be difficult for folks later
in life.
In either case, "service" is required (without relying on the
resident to perform that action).-a So, call for it directly or
advise a "caretaker" to do so.
Thank you for that exposition.-a You said there were no batteries, and I
want to add real life experience to your /threat model/.-a Here in this
part of the world, it's common to cut off the electricity if the condo- minium dues are not paid on time, and if that happens during an extended vacation -- which did happen to me -- it can be several weeks, or months until someone notices the power is off.
And during that time, the plants would die, with the irrigation system
unable to even phone home to irritate a human.
For your given target market, that can also happen if a /helpful family member/ comes along and turns off the breaker to save a few dollars dur-
ing an extended vacation away from home.
Now, whether people are willing to pay for the extra expense of a bat-The problem with batteries is that they require maintenance. And,
tery addition is another matter, but you can always add such stories to
your sales spiel and see what happens.
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 7/11/2026 5:54 am, john larkin wrote:
Being a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into something >>>> that can be run on hardware (which will have an architecture - it is
constructed from components that have been connected by some kind of
architect).
If that post were compiled to assembly language, it would be a nop.
As a compiler, you do seem to be sub-optimal, if not downright
afunctional. Ignoring implications you don't like isn't an option for a
compiler. There can be functions they can't parse - in your case don't
want to parse - but that doesn't generate a nop.
You clearly go into area were you are not an expert. Google a
bit about "undefined behaviour" in C and you will learn that
when source code makes no sense, then C compier can do
essentially anything, which in not so rare cases means that
compiler simply deletes what programmer wrote.
Explicit nop-s are rarely emited by compilers,
but one can get 'return'
(if compiler decides that garbage source is doing nothing
useful, but it will eventually finish) or executing whatever
happens to be after deleted code (if compiler decides that
code should be never executed because it performed illegal
operation).
On 11/12/2026 10:39 AM, Bill Sloman wrote:
On 12/11/2026 11:50 am, john larkin wrote:
On Wed, 11 Nov 2026 14:54:11 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 11/11/2026 2:42 am, john larkin wrote:
On Tue, 10 Nov 2026 18:38:47 +0800, Johann 'Myrkraverk' Oskarsson
<johann@myrkraverk.invalid> wrote:
On 11/10/2026 6:12 PM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
The point of all of this?-a Comedy is fun, you should try it.-a It's
merely a matter of practice.
On 13/11/2026 5:47 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/12/2026 10:39 AM, Bill Sloman wrote:
On 12/11/2026 11:50 am, john larkin wrote:
On Wed, 11 Nov 2026 14:54:11 +1100, Bill Sloman <bill.sloman@ieee.org> >>>> wrote:
On 11/11/2026 2:42 am, john larkin wrote:
On Tue, 10 Nov 2026 18:38:47 +0800, Johann 'Myrkraverk' Oskarsson
<johann@myrkraverk.invalid> wrote:
On 11/10/2026 6:12 PM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
<snip>
The point of all of this?-a Comedy is fun, you should try it.-a It's
merely a matter of practice.
Comedy can be fun, and I've done a bit of it. Claiming that it is just a matter of practice means that you don't know what you are talking about,
as usual.
<snip>
All my stolen phones became stolen indoors - one of them became stolen
in a home (when I was away).
(S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
On 11/13/2026 7:05 PM, Bill Sloman wrote:
On 13/11/2026 5:47 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/12/2026 10:39 AM, Bill Sloman wrote:
On 12/11/2026 11:50 am, john larkin wrote:
On Wed, 11 Nov 2026 14:54:11 +1100, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:
On 11/11/2026 2:42 am, john larkin wrote:
On Tue, 10 Nov 2026 18:38:47 +0800, Johann 'Myrkraverk' Oskarsson >>>>>>> <johann@myrkraverk.invalid> wrote:
On 11/10/2026 6:12 PM, Liz Tuddenham wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
<snip>
The point of all of this?-a Comedy is fun, you should try it.-a It's
merely a matter of practice.
Comedy can be fun, and I've done a bit of it. Claiming that it is just
a matter of practice means that you don't know what you are talking
about, as usual.
<snip>
Dear Bill,
Now you're so wrong you have egg on your face.-a How does it feel?
Trying to claim comedy isn't about practice is just your coping mechanism
for being so unfunny in life everyone stopped talking to you.
So don't project your coping mechanism on other people, it's not
healthy.
On 10/11/2026 9:20 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 1:49 PM, Bill Sloman wrote:
On 10/11/2026 2:12 am, john larkin wrote:
On Mon, 9 Nov 2026 16:42:08 +1100, Bill Sloman <bill.sloman@ieee.org>
wrote:
On 9/11/2026 6:27 am, Waldek Hebisch wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman
<bill.sloman@ieee.org>
wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. >>>>>>>>>>>>>> Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are >>>>>>>>>>>> over 3000
and they keep coming.
Real men code in binary using the front panel switches.
I actually used a PDP-7 where you really did have to
bootstrap it that
way to read in a paper tape. It was a fun machine as it had a >>>>>>>>>>> vector
graphics display so was very good for asteroids, but cheated >>>>>>>>>>> at chess.
I did a lot of stuff in PDP-11 and 68K assembly languages. >>>>>>>>>> With a few
macros, they are almost higher-level languages.
All high level languages get compiled into assembly language >>>>>>>>> before they
can be run on a computer.
Well, no.
Counter-example?
As a compiler, you do seem to be sub-optimal, if not downrightBeing a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into >>>>>>>>> something
that can be run on hardware (which will have an architecture - >>>>>>>>> it is
constructed from components that have been connected by some >>>>>>>>> kind of
architect).
If that post were compiled to assembly language, it would be a nop. >>>>>>>
afunctional. Ignoring implications you don't like isn't an option >>>>>>> for a
compiler. There can be functions they can't parse - in your case >>>>>>> don't
want to parse - but that doesn't generate a nop.
You clearly go into an area where you are not an expert.
I'm not pretending to be an expert, just less of a clueless newbie in >>>>> the area that John Larkin has shown himself to be.
I've written several compilers and several RTOS's and a bunch of
system simulators and hundreds of application programs, a good chunk
of a million lines of code. From PDP8 to ARM and one CPU that I
designed myself.
And I'm sure that you are perfectly happy with all of them.
Egomaniacs do go around describing themself as "stable geniuses".
What's your definition of newbie?
Somebody who doesn't know enough about what he his doing to be aware
of the areas he doesn't know enough about. It's not so much about
what you know, as what you know about the limits of your knowledge.
<snipped pretentious twaddle>
On 11/11/2026 4:35 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/11/2026 12:21 PM, Bill Sloman wrote:
On 11/11/2026 12:30 am, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 8:46 PM, Bill Sloman wrote:
On 10/11/2026 9:22 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 6:20 PM, Johann 'Myrkraverk' Oskarsson wrote:
<snip>
Best wishes, and keep being miserable for the next fifty years -- at
least!
My statistical expectation of survival is rather shorter than that.
I'd have to become ten years older than longest surviving human ever
has so far to get there.
Don't let the statistical expectation stop you.
Statistical expectation isn't any kind of barrier. It's just a
prediction based on what has happened in the past.
Modern medical science does keep people alive for longer than they used
to manage to survive, but 133 would be a very ripe old age.
I mean, /I want you/ to
be here fifty years from now, and still posting your miserable drivel on
sci.electronics.design, to the delight of the lurkers who simply enjoy
the consumption of popcorn and coca-cola.-a A good tradition among movie
goers going back decades, if not centuries.
What you perceive as miserable drivel may not look quite so miserable
and drivel-like to better-informed observers (who seem to be fairly numerous).
And I really don't care what you want. The peanut gallery isn't a discriminating audience.
On 13/11/2026 9:19 am, Johann 'Myrkraverk' Oskarsson wrote:
On 11/12/2026 10:31 PM, Bill Sloman wrote:
In any case, trying to use /knowledge/ as a status symbol seems quite >>>>> stupid to me; yet a lot of people behave this way.
Correcting errors isn't "using knowledge as a status symbol", except
in the sense that being able to correct errors does involve asserting
a superior status, but since the alternative is to leave errors
unremarked and uncorrected, it is also taking responsibility.
Of course you think so, but leaving errors is fine too.
You may think so but you aren't any kind of exemplary character.
-aAfter all, I'm not being paid to educate you on the errors of your ways.
What you post isn't exactly educational. It's sort of useful as an
example of how silly you can get if you don't know what you are talking about, but we aren't short of those kinds of posts here.
Bollocks snipped..
The rest of sci.electronics.design will just have to sit on the side-
lines for this, and eat popcorn. I hope they don't run out.
On Sat, 14 Nov 2026 07:44:45 +0800, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:
Bollocks snipped..
The rest of sci.electronics.design will just have to sit on the side-
lines for this, and eat popcorn. I hope they don't run out.
Can't you just go and play somewhere else?
Perhaps come back when (or if) you grow up?
On Sat, 14 Nov 2026 07:44:45 +0800, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:
Bollocks snipped..
The rest of sci.electronics.design will just have to sit on the side-
lines for this, and eat popcorn. I hope they don't run out.
Can't you just go and play somewhere else?
Perhaps come back when (or if) you grow up?
On 11/12/2026 10:16 AM, Bill Sloman wrote:
On 11/11/2026 4:35 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/11/2026 12:21 PM, Bill Sloman wrote:
On 11/11/2026 12:30 am, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 8:46 PM, Bill Sloman wrote:
On 10/11/2026 9:22 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 6:20 PM, Johann 'Myrkraverk' Oskarsson wrote:
<snip>
Best wishes, and keep being miserable for the next fifty years -- at >>>>> least!
My statistical expectation of survival is rather shorter than that.
I'd have to become ten years older than longest surviving human ever
has so far to get there.
Don't let the statistical expectation stop you.
Statistical expectation isn't any kind of barrier. It's just a
prediction based on what has happened in the past.
Modern medical science does keep people alive for longer than they
used to manage to survive, but 133 would be a very ripe old age.
I mean, /I want you/ to
be here fifty years from now, and still posting your miserable drivel on >>> sci.electronics.design, to the delight of the lurkers who simply enjoy
the consumption of popcorn and coca-cola.-a A good tradition among movie >>> goers going back decades, if not centuries.
What you perceive as miserable drivel may not look quite so miserable
and drivel-like to better-informed observers (who seem to be fairly
numerous).
And I really don't care what you want. The peanut gallery isn't a
discriminating audience.
What?-a You want to check out early because you're too lazy to live for
fifty more years?-a I mean, sure, I don't control your life, but still
you've been here for thirty years, so what's fifty more to you?
And after fifty more years, perhaps you want to be here for another
fifty years.-a Don't stop posting on my account.-a That's just silly.
On 11/10/2026 8:41 PM, Bill Sloman wrote:
On 10/11/2026 9:20 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 1:49 PM, Bill Sloman wrote:
On 10/11/2026 2:12 am, john larkin wrote:
On Mon, 9 Nov 2026 16:42:08 +1100, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:
On 9/11/2026 6:27 am, Waldek Hebisch wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman
<bill.sloman@ieee.org>
wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and data. >>>>>>>>>>>>>>> Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are >>>>>>>>>>>>> over 3000
and they keep coming.
Real men code in binary using the front panel switches. >>>>>>>>>>>>
I actually used a PDP-7 where you really did have to
bootstrap it that
way to read in a paper tape. It was a fun machine as it had >>>>>>>>>>>> a vector
graphics display so was very good for asteroids, but cheated >>>>>>>>>>>> at chess.
I did a lot of stuff in PDP-11 and 68K assembly languages. >>>>>>>>>>> With a few
macros, they are almost higher-level languages.
All high level languages get compiled into assembly language >>>>>>>>>> before they
can be run on a computer.
Well, no.
Counter-example?
Being a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into >>>>>>>>>> something
that can be run on hardware (which will have an architecture - >>>>>>>>>> it is
constructed from components that have been connected by some >>>>>>>>>> kind of
architect).
If that post were compiled to assembly language, it would be a >>>>>>>>> nop.
As a compiler, you do seem to be sub-optimal, if not downright >>>>>>>> afunctional. Ignoring implications you don't like isn't an
option for a
compiler. There can be functions they can't parse - in your case >>>>>>>> don't
want to parse - but that doesn't generate a nop.
You clearly go into an area where you are not an expert.
I'm not pretending to be an expert, just less of a clueless newbie in >>>>>> the area that John Larkin has shown himself to be.
I've written several compilers and several RTOS's and a bunch of
system simulators and hundreds of application programs, a good chunk >>>>> of a million lines of code. From PDP8 to ARM and one CPU that I
designed myself.
And I'm sure that you are perfectly happy with all of them.
Egomaniacs do go around describing themself as "stable geniuses".
What's your definition of newbie?
Somebody who doesn't know enough about what he his doing to be aware
of the areas he doesn't know enough about. It's not so much about
what you know, as what you know about the limits of your knowledge.
<snipped pretentious twaddle>
What?-a For once I'm trying to have a normal conversation with you, and
you pull this asinine stunt?
-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a You
-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a punk!
Let me tell you something, punk!-a You are not the first punk!-a I've
dealt with in life, real life, and online; you punk!
You started to talk about the limits of knowledge, and I added the
obvious corollary that sometimes even you don't know what you don't know.
Phrased slightly more politely, you punk!
It's not my fault you're too lazy to look in a dictionary, you punk!
-a https://en.wiktionary.org/wiki/unknown_unknown
-a https://en.wikipedia.org/wiki/Black_swan_theory
So now I have done so for you, you punk!
I don't know why you always think you know best about everything, you
punk!
On 11/14/2026 10:04 AM, JM wrote:
On Sat, 14 Nov 2026 07:44:45 +0800, Johann 'Myrkraverk' Oskarsson
<johann@myrkraverk.invalid> wrote:
Bollocks snipped..
The rest of sci.electronics.design will just have to sit on the side-
lines for this, and eat popcorn.-a I hope they don't run out.
Can't you just go and play somewhere else?
Perhaps come back when (or if) you grow up?
What is this?-a The in-group vs. the newcomer?-a Why are you antagonistic too?
And why do you think Bill Sloman shouldn't face the consequences of his
own action?-a Is he somehow an anointed priest of sci.electronics.design?
On 14/11/2026 5:20 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/14/2026 10:04 AM, JM wrote:
On Sat, 14 Nov 2026 07:44:45 +0800, Johann 'Myrkraverk' Oskarsson
<johann@myrkraverk.invalid> wrote:
Bollocks snipped..
The rest of sci.electronics.design will just have to sit on the side-
lines for this, and eat popcorn.-a I hope they don't run out.
Can't you just go and play somewhere else?
Perhaps come back when (or if) you grow up?
What is this?-a The in-group vs. the newcomer?-a Why are you antagonistic
too?
And why do you think Bill Sloman shouldn't face the consequences of his
own action?-a Is he somehow an anointed priest of sci.electronics.design?
You do seem to think that your own actions are consquential. JM and Phil Hobbs have been around here long enough to have seen any number of
voluble half-wits run out of steam.
On 14/11/2026 10:40 am, Johann 'Myrkraverk' Oskarsson wrote:
On 11/12/2026 10:16 AM, Bill Sloman wrote:
On 11/11/2026 4:35 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/11/2026 12:21 PM, Bill Sloman wrote:
On 11/11/2026 12:30 am, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 8:46 PM, Bill Sloman wrote:
On 10/11/2026 9:22 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 6:20 PM, Johann 'Myrkraverk' Oskarsson wrote:
<snip>
Best wishes, and keep being miserable for the next fifty years -- at >>>>>> least!
My statistical expectation of survival is rather shorter than that. >>>>> I'd have to become ten years older than longest surviving human
ever has so far to get there.
Don't let the statistical expectation stop you.
Statistical expectation isn't any kind of barrier. It's just a
prediction based on what has happened in the past.
Modern medical science does keep people alive for longer than they
used to manage to survive, but 133 would be a very ripe old age.
I mean, /I want you/ to
be here fifty years from now, and still posting your miserable
drivel on
sci.electronics.design, to the delight of the lurkers who simply enjoy >>>> the consumption of popcorn and coca-cola.-a A good tradition among movie >>>> goers going back decades, if not centuries.
What you perceive as miserable drivel may not look quite so miserable
and drivel-like to better-informed observers (who seem to be fairly
numerous).
And I really don't care what you want. The peanut gallery isn't a
discriminating audience.
What?-a You want to check out early because you're too lazy to live for
fifty more years?-a I mean, sure, I don't control your life, but still
you've been here for thirty years, so what's fifty more to you?
Staying alive as you get older takes progressively more effort. I used
to be able walk for miles, but now I find it difficult to cover the half-mile to the local hospital. I've done it twice this week - once to
get the blood samples taken that my urologist wants to have before he
talk s to me in a-a fortnight and once again to take back the 24-hour
urine sample that he wants analysed.
And after fifty more years, perhaps you want to be here for another
fifty years.-a Don't stop posting on my account.-a That's just silly.
Responding to you at all is totally silly. But it keeps me in practice
for more worthwhile targets.
On 14/11/2026 10:33 am, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 8:41 PM, Bill Sloman wrote:
On 10/11/2026 9:20 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 1:49 PM, Bill Sloman wrote:
On 10/11/2026 2:12 am, john larkin wrote:
On Mon, 9 Nov 2026 16:42:08 +1100, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:
On 9/11/2026 6:27 am, Waldek Hebisch wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman
<bill.sloman@ieee.org>
wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown >>>>>>>>>>>>>>> <'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and >>>>>>>>>>>>>>>> data. Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are >>>>>>>>>>>>>> over 3000
and they keep coming.
Real men code in binary using the front panel switches. >>>>>>>>>>>>>
I actually used a PDP-7 where you really did have to >>>>>>>>>>>>> bootstrap it that
way to read in a paper tape. It was a fun machine as it had >>>>>>>>>>>>> a vector
graphics display so was very good for asteroids, but >>>>>>>>>>>>> cheated at chess.
I did a lot of stuff in PDP-11 and 68K assembly languages. >>>>>>>>>>>> With a few
macros, they are almost higher-level languages.
All high level languages get compiled into assembly language >>>>>>>>>>> before they
can be run on a computer.
Well, no.
Counter-example?
Being a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed into >>>>>>>>>>> something
that can be run on hardware (which will have an architecture >>>>>>>>>>> - it is
constructed from components that have been connected by some >>>>>>>>>>> kind of
architect).
If that post were compiled to assembly language, it would be a >>>>>>>>>> nop.
As a compiler, you do seem to be sub-optimal, if not downright >>>>>>>>> afunctional. Ignoring implications you don't like isn't an
option for a
compiler. There can be functions they can't parse - in your >>>>>>>>> case don't
want to parse - but that doesn't generate a nop.
You clearly go into an area where you are not an expert.
I'm not pretending to be an expert, just less of a clueless
newbie in
the area that John Larkin has shown himself to be.
I've written several compilers and several RTOS's and a bunch of
system simulators and hundreds of application programs, a good chunk >>>>>> of a million lines of code. From PDP8 to ARM and one CPU that I
designed myself.
And I'm sure that you are perfectly happy with all of them.
Egomaniacs do go around describing themself as "stable geniuses".
What's your definition of newbie?
Somebody who doesn't know enough about what he his doing to be
aware of the areas he doesn't know enough about. It's not so much
about what you know, as what you know about the limits of your
knowledge.
<snipped pretentious twaddle>
What?-a For once I'm trying to have a normal conversation with you, and
you pull this asinine stunt?
-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a You
-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a punk!
Let me tell you something, punk!-a You are not the first punk!-a I've
dealt with in life, real life, and online; you punk!
You started to talk about the limits of knowledge, and I added the
obvious corollary that sometimes even you don't know what you don't know.
Phrased slightly more politely, you punk!
It's not my fault you're too lazy to look in a dictionary, you punk!
I mostly don't need to. I read lot when young, and do have a good memory.
-a-a https://en.wiktionary.org/wiki/unknown_unknown
-a-a https://en.wikipedia.org/wiki/Black_swan_theory
So now I have done so for you, you punk!
You didn't need to bother
/wiki/The_Black_Swan:_The_Impact_of_the_Highly_Improbable
I bought the book when-a Nassim Nicholas Taleb first published it in
2007and read it from cover to cover, which wasn't difficult.
It's sort of interesting.
I don't know why you always think you know best about everything, you
punk!
I don't. I frequently know better than the self-important twits who post here from time to time, but I have had a good enough education to know
how little I know. I read enough to learn more as it gets discovered and publicised, and I know enough to be well aware that a lot of interesting stuff isn't interesting to enough people to get publicised.
The punk here is you. You wouldn't waste your time boasting about
"dealing with me" if you had any grasp of reality.
Donald J. Trump boasts about writing "The Art of the Deal" when it is
well known that it was ghost-written for him. You seem to have the same
kind of delusions about what "dealing with" actually implies.
On 11/14/2026 3:20 PM, Bill Sloman wrote:
On 14/11/2026 5:20 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/14/2026 10:04 AM, JM wrote:You do seem to think that your own actions are consequential. JM and
On Sat, 14 Nov 2026 07:44:45 +0800, Johann 'Myrkraverk' Oskarsson
<johann@myrkraverk.invalid> wrote:
Bollocks snipped..
The rest of sci.electronics.design will just have to sit on the side- >>>>> lines for this, and eat popcorn.-a I hope they don't run out.
Can't you just go and play somewhere else?
Perhaps come back when (or if) you grow up?
What is this?-a The in-group vs. the newcomer?-a Why are you antagonistic >>> too?
And why do you think Bill Sloman shouldn't face the consequences of his
own action?-a Is he somehow an anointed priest of sci.electronics.design? >>
Phil Hobbs have been around here long enough to have seen any number
of voluble half-wits run out of steam.
You have nothing to worry about.-a I deleted my Steam account, so I won't
run out of Steam!-a I already did.
On 11/14/2026 2:54 PM, Bill Sloman wrote:
On 14/11/2026 10:40 am, Johann 'Myrkraverk' Oskarsson wrote:
On 11/12/2026 10:16 AM, Bill Sloman wrote:
On 11/11/2026 4:35 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/11/2026 12:21 PM, Bill Sloman wrote:
On 11/11/2026 12:30 am, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 8:46 PM, Bill Sloman wrote:
On 10/11/2026 9:22 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 6:20 PM, Johann 'Myrkraverk' Oskarsson wrote:
<snip>
Best wishes, and keep being miserable for the next fifty years -- at >>>>>>> least!
My statistical expectation of survival is rather shorter than
that. I'd have to become ten years older than longest surviving
human ever has so far to get there.
Don't let the statistical expectation stop you.
Statistical expectation isn't any kind of barrier. It's just a
prediction based on what has happened in the past.
Modern medical science does keep people alive for longer than they
used to manage to survive, but 133 would be a very ripe old age.
I mean, /I want you/ to
be here fifty years from now, and still posting your miserable
drivel on
sci.electronics.design, to the delight of the lurkers who simply enjoy >>>>> the consumption of popcorn and coca-cola.-a A good tradition among
movie
goers going back decades, if not centuries.
What you perceive as miserable drivel may not look quite so
miserable and drivel-like to better-informed observers (who seem to
be fairly numerous).
And I really don't care what you want. The peanut gallery isn't a
discriminating audience.
What?-a You want to check out early because you're too lazy to live for
fifty more years?-a I mean, sure, I don't control your life, but still
you've been here for thirty years, so what's fifty more to you?
Staying alive as you get older takes progressively more effort. I used
to be able walk for miles, but now I find it difficult to cover the
half-mile to the local hospital. I've done it twice this week - once
to get the blood samples taken that my urologist wants to have before
he talk s to me in a-a fortnight and once again to take back the
24-hour urine sample that he wants analysed.
And after fifty more years, perhaps you want to be here for another
fifty years.-a Don't stop posting on my account.-a That's just silly.
Responding to you at all is totally silly. But it keeps me in practice
for more worthwhile targets.
It's good that you're staying in practice.-a Both at staying alive, and responding to me.-a I have no problems with either.
On 14/11/2026 10:54 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/14/2026 3:20 PM, Bill Sloman wrote:
On 14/11/2026 5:20 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/14/2026 10:04 AM, JM wrote:
On Sat, 14 Nov 2026 07:44:45 +0800, Johann 'Myrkraverk' Oskarsson
<johann@myrkraverk.invalid> wrote:
Bollocks snipped..
The rest of sci.electronics.design will just have to sit on the side- >>>>>> lines for this, and eat popcorn.-a I hope they don't run out.
Can't you just go and play somewhere else?
Perhaps come back when (or if) you grow up?
What is this?-a The in-group vs. the newcomer?-a Why are you antagonistic >>>> too?
And why do you think Bill Sloman shouldn't face the consequences of his >>>> own action?-a Is he somehow an anointed priest of
sci.electronics.design?
You do seem to think that your own actions are consequential. JM and
Phil Hobbs have been around here long enough to have seen any number
of voluble half-wits run out of steam.
You have nothing to worry about.-a I deleted my Steam account, so I won't
run out of Steam!-a I already did.
The phrase is rather older than computer gaming, and refers to steam engines. Think George Stevensons's Rocket of 1829.
https://en.wikipedia.org/wiki/Stephenson%27s_Rocket
On 11/14/2026 3:13 PM, Bill Sloman wrote:
On 14/11/2026 10:33 am, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 8:41 PM, Bill Sloman wrote:
On 10/11/2026 9:20 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 1:49 PM, Bill Sloman wrote:
On 10/11/2026 2:12 am, john larkin wrote:
On Mon, 9 Nov 2026 16:42:08 +1100, Bill Sloman
<bill.sloman@ieee.org>
wrote:
On 9/11/2026 6:27 am, Waldek Hebisch wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman
<bill.sloman@ieee.org>
wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown >>>>>>>>>>>>>>>> <'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and >>>>>>>>>>>>>>>>> data. Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There are >>>>>>>>>>>>>>> over 3000
and they keep coming.
Real men code in binary using the front panel switches. >>>>>>>>>>>>>>
I actually used a PDP-7 where you really did have to >>>>>>>>>>>>>> bootstrap it that
way to read in a paper tape. It was a fun machine as it >>>>>>>>>>>>>> had a vector
graphics display so was very good for asteroids, but >>>>>>>>>>>>>> cheated at chess.
I did a lot of stuff in PDP-11 and 68K assembly languages. >>>>>>>>>>>>> With a few
macros, they are almost higher-level languages.
All high level languages get compiled into assembly language >>>>>>>>>>>> before they
can be run on a computer.
Well, no.
Counter-example?
Being a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed >>>>>>>>>>>> into something
that can be run on hardware (which will have an architecture >>>>>>>>>>>> - it is
constructed from components that have been connected by some >>>>>>>>>>>> kind of
architect).
If that post were compiled to assembly language, it would be >>>>>>>>>>> a nop.
As a compiler, you do seem to be sub-optimal, if not downright >>>>>>>>>> afunctional. Ignoring implications you don't like isn't an >>>>>>>>>> option for a
compiler. There can be functions they can't parse - in your >>>>>>>>>> case don't
want to parse - but that doesn't generate a nop.
You clearly go into an area where you are not an expert.
I'm not pretending to be an expert, just less of a clueless
newbie in
the area that John Larkin has shown himself to be.
I've written several compilers and several RTOS's and a bunch of >>>>>>> system simulators and hundreds of application programs, a good chunk >>>>>>> of a million lines of code. From PDP8 to ARM and one CPU that I
designed myself.
And I'm sure that you are perfectly happy with all of them.
Egomaniacs do go around describing themself as "stable geniuses". >>>>>>> What's your definition of newbie?
Somebody who doesn't know enough about what he his doing to be
aware of the areas he doesn't know enough about. It's not so much >>>>>> about what you know, as what you know about the limits of your
knowledge.
<snipped pretentious twaddle>
What?-a For once I'm trying to have a normal conversation with you, and
you pull this asinine stunt?
-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a You
-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a punk! >>>
Let me tell you something, punk!-a You are not the first punk!-a I've
dealt with in life, real life, and online; you punk!
You started to talk about the limits of knowledge, and I added the
obvious corollary that sometimes even you don't know what you don't
know.
Phrased slightly more politely, you punk!
It's not my fault you're too lazy to look in a dictionary, you punk!
I mostly don't need to. I read lot when young, and do have a good memory.
-a-a https://en.wiktionary.org/wiki/unknown_unknown
-a-a https://en.wikipedia.org/wiki/Black_swan_theory
So now I have done so for you, you punk!
You didn't need to bother
/wiki/The_Black_Swan:_The_Impact_of_the_Highly_Improbable
I bought the book when-a Nassim Nicholas Taleb first published it in
2007and read it from cover to cover, which wasn't difficult.
It's sort of interesting.
I don't know why you always think you know best about everything, you
punk!
I don't. I frequently know better than the self-important twits who
post here from time to time, but I have had a good enough education to
know how little I know. I read enough to learn more as it gets
discovered and publicised, and I know enough to be well aware that a
lot of interesting stuff isn't interesting to enough people to get
publicised.
The punk here is you. You wouldn't waste your time boasting about
"dealing with me" if you had any grasp of reality.
Donald J. Trump boasts about writing "The Art of the Deal" when it is
well known that it was ghost-written for him. You seem to have the
same kind of delusions about what "dealing with" actually implies.
I don't really understand why you bring him up.-a I don't know the guy,
as I've never met him.-a And I haven't even read his book, whoever wrote
it.
A much more interesting book is /The End of Alchemy/ (2017) by Mervyn
King.-a It is not about alchemy, nor chemistry [1] and the byline gives
it away, /Money, Banking, and the Future of Global Economy/.
Mervyn King was a member of the Royal Mint I believe, but it's been a
while since I read it.
Now, since you've read the book /The Black Swan/, how many black swan
events have you caused?
Or do you think there's no correlation between
reading a book, and causing an event?-a Can Karl Marx say the same [2]?
Anyway, don't stop on my account, you can still cause a few black swan
events in your life, if you're not lazy.
[1] Which could be interesting enough, given your background in
chemistry.
[2] Well, technically, it's /writing a book/ for him, but that's just
a minor difference, isn't it?
On 14/11/2026 11:06 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/14/2026 3:13 PM, Bill Sloman wrote:
On 14/11/2026 10:33 am, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 8:41 PM, Bill Sloman wrote:
On 10/11/2026 9:20 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 1:49 PM, Bill Sloman wrote:
On 10/11/2026 2:12 am, john larkin wrote:
On Mon, 9 Nov 2026 16:42:08 +1100, Bill Sloman
<bill.sloman@ieee.org>
wrote:
On 9/11/2026 6:27 am, Waldek Hebisch wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman
<bill.sloman@ieee.org>
wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown >>>>>>>>>>>>>>>>> <'''newspam'''@nonad.co.uk> wrote:
segmented memory and hard separation of program and >>>>>>>>>>>>>>>>>> data. Signed drivers
Not a Lisp fan then?
People love to invent weird computer languages. There >>>>>>>>>>>>>>>> are over 3000
and they keep coming.
Real men code in binary using the front panel switches. >>>>>>>>>>>>>>>
I actually used a PDP-7 where you really did have to >>>>>>>>>>>>>>> bootstrap it that
way to read in a paper tape. It was a fun machine as it >>>>>>>>>>>>>>> had a vector
graphics display so was very good for asteroids, but >>>>>>>>>>>>>>> cheated at chess.
I did a lot of stuff in PDP-11 and 68K assembly languages. >>>>>>>>>>>>>> With a few
macros, they are almost higher-level languages.
All high level languages get compiled into assembly >>>>>>>>>>>>> language before they
can be run on a computer.
Well, no.
Counter-example?
Being a compiler is tedious.
Unlike some architectures that I might name.
A language isn't an architecture. It has to be processed >>>>>>>>>>>>> into something
that can be run on hardware (which will have an
architecture - it is
constructed from components that have been connected by >>>>>>>>>>>>> some kind of
architect).
If that post were compiled to assembly language, it would be >>>>>>>>>>>> a nop.
As a compiler, you do seem to be sub-optimal, if not downright >>>>>>>>>>> afunctional. Ignoring implications you don't like isn't an >>>>>>>>>>> option for a
compiler. There can be functions they can't parse - in your >>>>>>>>>>> case don't
want to parse - but that doesn't generate a nop.
You clearly go into an area where you are not an expert.
I'm not pretending to be an expert, just less of a clueless >>>>>>>>> newbie in
the area that John Larkin has shown himself to be.
I've written several compilers and several RTOS's and a bunch of >>>>>>>> system simulators and hundreds of application programs, a good >>>>>>>> chunk
of a million lines of code. From PDP8 to ARM and one CPU that I >>>>>>>> designed myself.
And I'm sure that you are perfectly happy with all of them.
Egomaniacs do go around describing themself as "stable geniuses". >>>>>>>> What's your definition of newbie?
Somebody who doesn't know enough about what he his doing to be
aware of the areas he doesn't know enough about. It's not so much >>>>>>> about what you know, as what you know about the limits of your
knowledge.
<snipped pretentious twaddle>
What?-a For once I'm trying to have a normal conversation with you, and >>>> you pull this asinine stunt?
-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a You
-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a punk! >>>>
Let me tell you something, punk!-a You are not the first punk!-a I've
dealt with in life, real life, and online; you punk!
You started to talk about the limits of knowledge, and I added the
obvious corollary that sometimes even you don't know what you don't
know.
Phrased slightly more politely, you punk!
It's not my fault you're too lazy to look in a dictionary, you punk!
I mostly don't need to. I read lot when young, and do have a good
memory.
-a-a https://en.wiktionary.org/wiki/unknown_unknown
-a-a https://en.wikipedia.org/wiki/Black_swan_theory
So now I have done so for you, you punk!
You didn't need to bother
/wiki/The_Black_Swan:_The_Impact_of_the_Highly_Improbable
I bought the book when-a Nassim Nicholas Taleb first published it in
2007and read it from cover to cover, which wasn't difficult.
It's sort of interesting.
I don't know why you always think you know best about everything, you
punk!
I don't. I frequently know better than the self-important twits who
post here from time to time, but I have had a good enough education
to know how little I know. I read enough to learn more as it gets
discovered and publicised, and I know enough to be well aware that a
lot of interesting stuff isn't interesting to enough people to get
publicised.
The punk here is you. You wouldn't waste your time boasting about
"dealing with me" if you had any grasp of reality.
Donald J. Trump boasts about writing "The Art of the Deal" when it is
well known that it was ghost-written for him. You seem to have the
same kind of delusions about what "dealing with" actually implies.
I don't really understand why you bring him up.-a I don't know the guy,
as I've never met him.-a And I haven't even read his book, whoever wrote
it.
But you do share one of his intellectual weaknesses.
A much more interesting book is /The End of Alchemy/ (2017) by Mervyn
King.-a It is not about alchemy, nor chemistry [1] and the byline gives
it away, /Money, Banking, and the Future of Global Economy/.
Mervyn King was a member of the Royal Mint I believe, but it's been a
while since I read it.
Now, since you've read the book /The Black Swan/, how many black swan
events have you caused?
I've got three patents, which probably do qualify as black swan events -
it the ideas had been predictable they would have been obvious to those skilled in the art.
Or do you think there's no correlation between
reading a book, and causing an event?-a Can Karl Marx say the same [2]?
Jonathon Israel thinks that Spinoza writing a couple of books had a lot
to do with the democratic revolution.
https://www.jstor.org/stable/j.ctt7t0f8
he's written more and longer books on that and related subjects. I got
onto him when I moved to the Netherlands and read his history of the
Dutch Republic.
Books reflect the issues of the day, and can influence them. Karl Marx
was a remarkably influential figure, and his ideas about "the leading
role of the party" were unfortunately influential. Much of what he had
to say was very sensible, but that lot wasn't.
Anyway, don't stop on my account, you can still cause a few black swan
events in your life, if you're not lazy.
Laziness probably doesn't come into it. Black swan events are
unpredictable, and if you can't predict what effect unexpected idea will have you can't put a lot of energy into encouraging the effects.
[1] Which could be interesting enough, given your background in
chemistry.
It wasn't just my background. Both my parents had university degrees in chemistry,-a but nether was remotely interested in alchemy.
[2] Well, technically, it's /writing a book/ for him, but that's just
a minor difference, isn't it?
The guy who ghost-wrote "The Art of the Deal" for Donald Trump had to
put a lot of effort making what he wrote look as if Donald Trump might
have written it, and he complained afterwards that it was difficult to
get enough out of Donald Trump on the subject to create a document that might look as if Donald Trump had written it. A ninety-second attention
span doesn't generate a lot of text in one hit, so the ghost-writer had
to glom together a lot of sound-bites.
On 11/14/2026 11:53 PM, Bill Sloman wrote:
On 14/11/2026 11:06 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/14/2026 3:13 PM, Bill Sloman wrote:
On 14/11/2026 10:33 am, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 8:41 PM, Bill Sloman wrote:
On 10/11/2026 9:20 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/10/2026 1:49 PM, Bill Sloman wrote:
On 10/11/2026 2:12 am, john larkin wrote:
On Mon, 9 Nov 2026 16:42:08 +1100, Bill Sloman
<bill.sloman@ieee.org>
wrote:
On 9/11/2026 6:27 am, Waldek Hebisch wrote:
Bill Sloman <bill.sloman@ieee.org> wrote:
On 7/11/2026 3:57 pm, john larkin wrote:
On Sat, 7 Nov 2026 15:38:13 +1100, Bill Sloman
<bill.sloman@ieee.org>
wrote:
On 7/11/2026 5:54 am, john larkin wrote:
On Fri, 6 Nov 2026 10:24:07 +0000, Martin Brown
<'''newspam'''@nonad.co.uk> wrote:
On 30/10/2026 16:15, john larkin wrote:
On Fri, 30 Oct 2026 15:36:05 +0000, JM
<sunaecoNoChoppedPork@gmail.com> wrote:
On Thu, 29 Oct 2026 17:36:05 +0000, Martin Brown >>>>>>>>>>>>>>>>>> <'''newspam'''@nonad.co.uk> wrote:
It's not my fault you're too lazy to look in a dictionary, you punk!
I mostly don't need to. I read lot when young, and do have a good
memory.
-a-a https://en.wiktionary.org/wiki/unknown_unknown
-a-a https://en.wikipedia.org/wiki/Black_swan_theory
So now I have done so for you, you punk!
You didn't need to bother
/wiki/The_Black_Swan:_The_Impact_of_the_Highly_Improbable
I bought the book when-a Nassim Nicholas Taleb first published it in
2007and read it from cover to cover, which wasn't difficult.
It's sort of interesting.
I don't know why you always think you know best about everything, you >>>>> punk!
I don't. I frequently know better than the self-important twits who
post here from time to time, but I have had a good enough education
to know how little I know. I read enough to learn more as it gets
discovered and publicised, and I know enough to be well aware that a
lot of interesting stuff isn't interesting to enough people to get
publicised.
The punk here is you. You wouldn't waste your time boasting about
"dealing with me" if you had any grasp of reality.
Donald J. Trump boasts about writing "The Art of the Deal" when it
is well known that it was ghost-written for him. You seem to have
the same kind of delusions about what "dealing with" actually implies.
I don't really understand why you bring him up.-a I don't know the guy,
as I've never met him.-a And I haven't even read his book, whoever wrote >>> it.
But you do share one of his intellectual weaknesses.
So do you,
so why is that relevant to anything?-a I mean, the guy's famous
]sure, but that's no reason to bring him into this conversation,
unless you want to invite him to post here in sci.electronics.design.
Now, that would be something.
A much more interesting book is /The End of Alchemy/ (2017) by Mervyn
King.-a It is not about alchemy, nor chemistry [1] and the byline gives
it away, /Money, Banking, and the Future of Global Economy/.
Mervyn King was a member of the Royal Mint I believe, but it's been a
while since I read it.
Now, since you've read the book /The Black Swan/, how many black swan
events have you caused?
I've got three patents, which probably do qualify as black swan events
- it the ideas had been predictable they would have been obvious to
those skilled in the art.
Congratulations-ish on that.
Or do you think there's no correlation between
reading a book, and causing an event?-a Can Karl Marx say the same [2]?
Jonathon Israel thinks that Spinoza writing a couple of books had a
lot to do with the democratic revolution.
https://www.jstor.org/stable/j.ctt7t0f8
I've added this book to my /saved for later/ on Abebooks.-a I won't do
more for now.
He's written more and longer books on that and related subjects. I got
onto him when I moved to the Netherlands and read his history of the
Dutch Republic.
Books reflect the issues of the day, and can influence them. Karl Marx
was a remarkably influential figure, and his ideas about "the leading
role of the party" were unfortunately influential. Much of what he had
to say was very sensible, but that lot wasn't.
Anyway, don't stop on my account, you can still cause a few black swan
events in your life, if you're not lazy.
Laziness probably doesn't come into it. Black swan events are
unpredictable, and if you can't predict what effect unexpected idea
will have you can't put a lot of energy into encouraging the effects.
[1] Which could be interesting enough, given your background in
chemistry.
It wasn't just my background. Both my parents had university degrees
in chemistry,-a but nether was remotely interested in alchemy.
Alchemy as the precursor to modern chemistry is quite fascinating.
I did read up on Antoine Lavoisier, but only the superficial stuff
readily available on the web.-a I haven't dug into any detailed > biographies yet.
Abu Musa Jabir ibn Hayyan is more famous for bringing us the term /gibberish/ with which I'm sure you're well acquainted.
[2] Well, technically, it's /writing a book/ for him, but that's just
a minor difference, isn't it?
The guy who ghost-wrote "The Art of the Deal" for Donald Trump had to
put a lot of effort making what he wrote look as if Donald Trump might
have written it, and he complained afterwards that it was difficult to
get enough out of Donald Trump on the subject to create a document
that might look as if Donald Trump had written it. A ninety-second
attention span doesn't generate a lot of text in one hit, so the
ghost-writer had to glom together a lot of sound-bites.
Well, as I don't know Trump personally, I don't feel any need to bring
him up in every conversation.-a I suggest you do the same.
I'm not interested in /The Art of the Deal/, and not because Trump did
not write it himself.-a It would be much more interesting /had/ he writ-
ten it himself, I admit.-a I mean, the man must have learned to type at
some point in life, if only to play /Leather Goddesses of Phobos/.
I never finished the game myself, but I'm sure I'll get to it /one of
these years/.-a Did you play it?
On 11/14/2026 10:14 PM, Bill Sloman wrote:
On 14/11/2026 10:54 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/14/2026 3:20 PM, Bill Sloman wrote:
On 14/11/2026 5:20 pm, Johann 'Myrkraverk' Oskarsson wrote:
On 11/14/2026 10:04 AM, JM wrote:
On Sat, 14 Nov 2026 07:44:45 +0800, Johann 'Myrkraverk' Oskarsson
<johann@myrkraverk.invalid> wrote:
You do seem to think that your own actions are consequential. JM and
Phil Hobbs have been around here long enough to have seen any number
of voluble half-wits run out of steam.
You have nothing to worry about.-a I deleted my Steam account, so I won't >>> run out of Steam!-a I already did.
The phrase is rather older than computer gaming, and refers to steam
engines. Think George Stevensons's Rocket of 1829.
https://en.wikipedia.org/wiki/Stephenson%27s_Rocket
Yes, I know that.-a I just don't care.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 55:41:40 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,687 |