niallyoung on Nostr: HELP i need a better name for this #golang repo for #nostr 😭 Any ideas? 🙏 ...
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? 🙏
Published at
2024-03-30 23:02:44Event JSON
{
"id": "4dac8db1f360af231f1d1a9a7cfa6ec052c42bdd27a8a2ea66de7b8a61e15aa9",
"pubkey": "234dd2c21135830a960a462defdb410ac26f178cbf8e13fbe43890f8656ee983",
"created_at": 1711839764,
"kind": 1,
"tags": [],
"content": "HELP i need a better name for this #golang repo for #nostr 😭 Any ideas? 🙏 🙇♂️ \n\ngoNDK (no capitals sob)\ngondk\ngondo\ngonzo\nndkgo\nnostrgo\ngonostr\ngostr (already a client)\n\nYes, 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.\n\nThe 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 …. 😬 \n\nAny ideas for a name? 🙏",
"sig": "7df208f9c15bf69bf8b678823d11d0ccdcd701bd37112b9552bc05977f7433189b28a3d4227f6bc63d27eee552e89cc2e138e5719ee7a349c2177379625eba0e"
}