🔥The 9th Round of Easy Loan, Earn $40 Reward is in progress❗️ ⏰ Promotion Period: January 15th - Feburary 15th, 2025 👉 Register now and check more details at gate.io/campaigns/358

it feels like multithreading the act of writing code. similar potential for wins and similar tradeoffs. the codebase has to be organized well enough with repeatable patterns in small files bun’s JS parser is still a 20k file, but fortunately most of bun isn’t like that nowadays

guess what the next slide shows

Bun v1.2.16 - Fixes 73 issues (addressing 124 👍) - Serve files with `Bun.serve` in `routes` - `vm.SyntheticModule` & `node:http_parser` - Rewrote much of node:net for improved Node.js compatibility - Bun.spawn uses less ram Thanks 25 contributors! bun.sh/blog/bun-v1.2.…

Darren Shepherd Honestly think they are a great primitive, really in the sweet spot of abstraction. And support across the stack is usually good enough. Did a test the other day with >250k concurrent clients on Bun with <500MB ram and ~9ms broadcasts, pretty decent backend

NotebookLM's overview of Bun's docs isn't bad

In the next version of Bun setTimeout() & setImmediate() use 15% less memory

Bun v1.2.17 ships tomorrow

excited to try this