> From: Lassi Kortela <xxxxxx@lassi.io>
> Date: Tuesday, June 09, 2020 9:42 AM
>
>> BTW, I agree that using "threading" is a bad idea.  "Pipelining"
>> strikes me as the best, it's more unique (sorry) than "sequencing".
>
> First associations:
>
> threading ~ OS/VM stuff
>
> pipelining ~ CPU instruction-level optimization
>
> piping ~ Unix shell pipelines
>
> sequencing ~ data structures, concurrency functional programming
>
> I guess sequencing is least confusing from that standpoint :)

I would argue that *strong* associations are more important than first
ones, it's easier to get past the first than the second.  I gather
we're all agreeing that threading is out, especially since that's a
concept in many Scheme implementations.

Pipelining in CPUs is quite removed from programming in as high a
level language as a Lisp, and another reason I prefer it to sequencing
is that the former fits better with passing data from a to b to c.  To
me it has more of a data connotation than sequencing, which could for
example be for side effects, like sequencing a fireworks show.

- Harold