Nostr Web Client

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/1494

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

this is the thing about OOP programmers, they are retarded

c++, java, rust, javascript... retarded

functional, imperative and structural typed have proven to be more efficient to compile and easier to reason about, many times over, these people are literally dumb turds

Reply to this note

Please Login to reply.

Discussion

Silberengel 1y ago

I just rewrote everything from functional to OO and now it's a hot mess and I can barely understand what I built.

Having OO regret.

Silberengel 1y ago

Code blew up to 3 times the size and now I'm trying to refactor it back down. 😏

Agonizing over which class to put in which method and stuff, and I only have 4 classes, so far.