> But then, at that point, you're saying something pretty profound about computer science (roughly: that there was no meaningfully more sophisticated and complex place to go from where we are today).
Or that human taste and expertise cannot helpfully guide a project there.
> that's what "productivity", in the economic sense, means
That's too strong. It does mean we can do the same work with fewer people, but depending on the shape of the demand curve that can mean more jobs exist doing that thing than otherwise would (an instance of the Jevons Paradox).
I guess we may be talking at cross purposes here - idiomatic usages of the pin macros don't really mean you need to understand whats going on here (beyond "async futures need to be pinned in order to repeatedly mutate them").
If you need to produce a type that interacts with Pin, it's a whole other level of hell.
Or that human taste and expertise cannot helpfully guide a project there.