@jarredsumner Love the vision, but after trying to use Bun.SQL this week, there’s a lot of polish required before it’s usable. Maybe a third of the bugs in a task worker system I wrote are bugs in Bun
People are asking me what I’ll do if and when Twitter starts to fall apart. I am not looking for a replacement and will ride this plane all the way to the ground, at which point I’ll be free. Thank you.
@jarredsumner Reminds me of some code I wrote to parse url params at Stripe. Try `[card]number=4242424242424242` or `card][[[[[number=4242424242424242`
@jarredsumner TextDecoder performance bit me recently when trying to use apache-arrow in node. There was a ~2x improvement between 16.x and 18.x, but both were hilariously slow. Excited you’re working on this!
Just passed a very important moment in @watershed's growth: we added animated Slack emoji for all of our operating principles! (most of the credit goes to @_yuhsin, who was up until midnight drawing some of the gifs frame-by-frame!)
@dgryski At @stripe we took a very similar approach to protecting credit card data. For us, I think it was a struct with a private member, plus redacting String(), MarshalText(), MarshalJSON(), etc. We named our Unwrap() “UnsafeString()” to make it more obvious in code review