A corrollary to reaching the Lone Wolf Horizon is that maintaining client libraries in various languages will become essential. NDK is a good start.
No one reimplements HTTP, they just use a library. Building those tools for Nostr will be the next big step.
it always starts with one good implementation that people can actually use
there is usually several attempts to do this but only one of them actually works properly at first and this momentum grows
one nice thing about this is that the seeming disarray of the specification comes into clear focus once someone builds a proper structure around it
i dunno about other languages but the Go versions i'm working with are a hellstorm of tight coupling, poor architecture and bad names,
not gonna totally hate on the people who scratch it together but it bewilders me how someone can build up such an artifice with such bad architecture without one day waking up and saying "ok, why is this thing impossible to change?"
no, i do understand it, i just write a lot more tests before i run off and try to implement, i have big codebases that had some nasty brittleness in them and this is my third major cycle of development working with nostr so maybe i'll get it right this time 😀
Maybe it'll all level out over time. We're still in the early days of Nostr, and everyone is throwing out whatever they think will be a good idea. Inertia and stability will come with longevity, most likely.
