mary 🐇
shot myself by having the CBOR decoder lazily serializing to atproto's lex-json format, in operator is a perf killer and I can't remove it from the encoder side
Nov 2 at 1:55amWeb
Show threadmary 🐇Nov 2
i certainly don't have to focus on perf any further but it's just nice if it can do it honestly
Show threadmary 🐇Nov 2
"hold on, in operator is slow?" it is, that's why there's a check for undefined before checking if the key even exists
Show threadNelson LopezNov 2

@mary_ext I have a special grudge against operators that do all sorts of weird shit behind the courtains

operators should only do math stuff, logic stuff and comparisons, whoever came up with << for streams in C++ is going to have a fist fight with me

Show threadmary 🐇Nov 2
@nelson tbh I'd assume the way JS object prototypes had been implemented in engines makes it such that retrieval is faster than existence checks
Show threadSun Microdevil Pte LtdDec 11
@mary_ext What does it do that makes `in` slow anyway?
If input is something like a hash table then it should be just as fast as grabbing the value no?