You hear that devs? Stop sucking 🤣 🤗
nostr:note18jvg0veu5a4qv0kstusmr36s33kxmrytwk49sgfg489z3ynqy7cqwfkezz
You hear that devs? Stop sucking 🤣 🤗
nostr:note18jvg0veu5a4qv0kstusmr36s33kxmrytwk49sgfg489z3ynqy7cqwfkezz
Yeah I used to suck with websockets a lot before I could get them right, there are still horrors in parts of the code that hasn't been touched in a while.
But, in my defense AI sucks at it too 😂 , you really have to understand what's going on at the connection level, libraries abstract it and you keep making stupid mistakes.
He probably only coded websockets in his 10gb ethernet connection
My phone Nostr is considerably slower than wifi Nostr
for most purposes, a simple request/response pattern is a better fit. the merging of subscriptions and queries in the nostr protocol is likely a huge cause of problems with performance because of badly written code and filter templates.
due to a mis-identified cable, my desktop has 100Mbit