HELP i need a better name for this #golang repo for #nostr ๐Ÿ˜ญ Any ideas? ๐Ÿ™ ๐Ÿ™‡โ€โ™‚๏ธ

goNDK (no capitals sob)

gondk

gondo

gonzo

ndkgo

nostrgo

gonostr

gostr (already a client)

Yes, projectโ€™s goals are ambitious, so a suitable name to reflect this: cohesive, well tested, injectable, idiomatic low-level types and funcs, interfaces for rapidly prototyping and building out prod-ready solutions, at scale ๐Ÿ‘A common base layer, other layers above. Smallish and focused first repo, intended as a solid foundation.

The problem is Go couples the repo name with the top-level package name, and package naming standard is lowercaseoneword, so I canโ€™t use the ideal goNDK or goNOSTR as every symbol import youโ€™d have to type that out โ€ฆ. ๐Ÿ˜ฌ

Any ideas for a name? ๐Ÿ™

Reply to this note

Please Login to reply.

Discussion

OR

should I just keep the good stuff behind more useful dirs/ and have a stub at top?

OR skip the stub and top-level go.mod and spin up N individual dir/go.mod sub-projects rather than 1?

naming being one-of-two of the hardest problems, behind cache invalidation and off-by-one^H^H^H but throw in repo naming and package naming ๐Ÿ˜–