Nostr Web Client

no, i'm talking about much simpler to parse data formats than all these retarded new things, JSON is just really messy and very often javascript programmers violate the requirements for static typing and in my Go code i am forced to do dozens of type assertions based on field string values, which can end up being hundreds of lines of code for their retarded "convenient" "flexible" data structure (just had to deal with this in my job, cost me about 10 hours of work implementing it so far)

have you ever read the raw data of an email?

can you tell me what justification there is for making nostr events more complicated than emails?

though i am sure it would pain them these clowns i speak of could actually write a parser for a text format like email...

https://docs.aws.amazon.com/ses/latest/dg/send-email-raw.html

it would take me, in contrast to the inordinate amount of type voodoo caused by javascript buffoons less time to write the whole parser that could work with a more logically structured, simple text format

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 10mo ago

and yeah, you mention JSONRPC

if you read nip-01 with the question in your mind "how complex is it going to be to parse these "envelopes" compared to using a common, old format like JSONRPC?"

implicit context isn't as bad as types specified in fields of dynamic typed wrappers but the code that parses it has to have the extra context of "is this a request or a response" in order to determine how to decode it

that annoyed the bejesus out of me because i shouldn't have to have this context missing from the message format

why did i write my own bespoke parser, btw?

because it's more than 3x faster than using even the best library for the task, and part of the reason is that it doesn't check for syntax violations that simply are not going to appear or have material impact on nostr JSON encoding for filter and event

Reply to this note

Please Login to reply.

Discussion

No replies yet.