Regarding the name... while I get the value of cool, mysterious-sounding
names for public-facing (or maybe at minimum cross-platform) projects, I'd
rather these small tools that we often make be named as intention-revealing
as possible. I've felt at times some unnecessary complication translating
#(starfish shovel sandcastle) -> #(Socket Debugger Array) ;-p
Indeed… I used to be a fan of cute names, but now when looking at the packages
it makes it very hard for people to understand what is what.
but this is just a tooling issue. With package metadata, people can add
information.
For example, if you add catalog metadata to a configuration, you get the
description in the fly by help.
Stef
Marcus
