ChipTuner on Nostr: I don't want nips to tell me how to design my data structures and API. Too many of ...
I don't want nips to tell me how to design my data structures and API. Too many of you OOP devs leaking code abstractions into the protocol specs IMO. nip44 was a lot of work to abstract away from the API into an architectural blueprint. I enjoy reading scientific white papers and RFCs way more because it doesn't tell me how to write code. Even NIP01 couldn't explain the spec without code.
I'm just grumpy when reading
https://github.com/nostr-protocol/nips/pull/1494Published at
2024-09-13 14:20:00Event JSON
{
"id": "4e03330258af6f1fd2b25e96fde801796e98878395047b9f574d686e71ee4989",
"pubkey": "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58",
"created_at": 1726237200,
"kind": 1,
"tags": [],
"content": "I don't want nips to tell me how to design my data structures and API. Too many of you OOP devs leaking code abstractions into the protocol specs IMO. nip44 was a lot of work to abstract away from the API into an architectural blueprint. I enjoy reading scientific white papers and RFCs way more because it doesn't tell me how to write code. Even NIP01 couldn't explain the spec without code. \n\nI'm just grumpy when reading \nhttps://github.com/nostr-protocol/nips/pull/1494",
"sig": "bf6288809b2fa8c44f8854a6de206539be707ad848d247e9f66399a37e281baa4f07a25c8cf1c157cc0d48c3cde0732ff339cc98fba32d8ecbe6c19d72a274d3"
}
