refactor(common): move low level utilities to @endo/common

[erights]

closes: #XXXX
refs: #1815

Description

Successor to #1815 with utilities moved to a new @endo/utils package.

Note: I did not label this refactor(utils)!: ... because I intend to add reexports to keep compat before declaring this ready for review.

Security Considerations

Scaling Considerations

Documentation Considerations

Testing Considerations

Upgrade Considerations

[kriskowal]

I want this to be called @endo/score as a pun on underscore.

To allow manual minimization of the weight of a program’s dependency graph, each utility function should be separately importable, like @endo/score/list-difference.js.

[erights]

I want this to be called @endo/score as a pun on underscore.

No single entendre puns. I'll allow it if you also have some rationalization, however bizarre or awkward, why "score" is a sensible name for this package. ;)

[kriskowal]

I want this to be called @endo/score as a pun on underscore.

No single entendre puns. I'll allow it if you also have some rationalization, however bizarre or awkward, why "score" is a sensible name for this package. ;)

I can only appeal to the tradition of:

• https://jquery.com/ for establishing the use of a single symbol ($) for a utility module
• https://underscorejs.org/ for establishing the use of (_) in particular as a utility module name
• https://lodash.com/ for riffing on synonyms of underscore (_)
• endo and under sounding similar

However, I cannot think of a winning pun on “score” that cuts it, which is a strike that really underlines your point. Scratch that.

[erights]

However, I cannot think of a winning pun on “score” that cuts it, which is a strike that really underlines your point. Scratch that.

I asked for a double entendre and got a meta entendre. Serves me right ;)

[erights]

On a slack channel, we settled on a package name of common