API naming, StructuredTaskScope

[Eirik Bjørsnøs]

On Fri, Nov 8, 2024 at 3:32 PM Viktor Klang <viktor.klang at oracle.com> wrote:

> Thanks for your thoughts!

Happy to help :-)

> As you can imagine, we have performed numerous experiments with different
naming structures and themes, and the current selection came out as the
winner.

Sure. Just remember that sometimes being an expert makes it very hard to
see the world like a new user does. Anchoring and Curse of Knowledge is
real. The first-use, fresh-eye experience happens just once, my feedback
here comes from that viewpoint.

While today is my first time sitting down actually coding with this
feature, I did watch some presentations in the past (by Alan, IIRC). My
thought seeing those was "This API seems raw, like work in progress, naming
will probably converge / settle on something simpler once the myopticy of
the first rounds of experimentation and implementation is over". Seeing
that didn't seem to happen, I sat down to code with a goal to find some
actual inherent complexity warranting the current naming. So far I've had
no luck. But fine, I guess we can always disagree on naming. It should be
easy enough to user test this on non-expert users, but yeah it's work..

> Besides the naming, do you have more feedback on the feature itself?

Probably, I need some more exploration time first.

Eirik.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/loom-dev/attachments/20241108/d60f8936/attachment.htm>