Phew! An update of my past 2 days: 964 changed files with 23,240 additions and 24,273 deletions (~6600 individual cases in ~1220 tests)...
Almost all tests are now using https://bun.sh and its test runner which executes everything in 23 seconds now vs. the previous 10-15 mins on GitHub CI. Only a small 25-35x(!) speed up... 🤯🤩
This is also great (if small fry for now) for saving energy! Right now, the main build step for all 184 packages is still using Yarn & Typescript and still taking ~23 mins on the Github CI (vs. ~4 mins on my MBA M1). This is because for each package Yarn also launches a new TS instance, which has huge overhead... Once this issue with Bun will be fixed, I'm sure I can get this time _drastically_ down too!
If JS had checked exceptions, that would make it very convincing as a suitable Go replacement for my work.
🔥 New episode of JS Party!
We get into it all: what problem he’s solving, how it’s so fast, why no Windows support, answering the critics, the (not real) beef between Bun and Node, how the VC-backed startup will sustain & more.
I've been moving all our #Jest tests to #NodeJS’s test runner as some sort of a wind-down task before I sign off for a few days. Learned about it while playing around with #BunJS. Finally got to the last test today and was able to remove Jest entirely from our dependency tree. It shaved off ~7% of our lock file: https://github.com/microsoft/react-native-test-app/pull/1622
🚢 New episode of JS Party!
They’re joined by @mcollina & @jasnell who are here to dispel Bun antagonism rumors, discuss the pros/cons of each runtime, explain how Node continues to thrive & even announce a VERY big upcoming feature!
This is actually a pretty awesome (but lengthy) post about Bun and why you probably shouldn't jump on the train already.
Bun hype. How we learned nothing from Yarn
I guess I will give #bun a try... these numbers aren't that bad, considering that in my test, the server handles 100 parallel requests for ~10 minutes and converts a big XML to JSON....
#ebay wants a response within 3000ms... when handing thousands of incoming notifications, this is getting tough.... this needs more testing 🤓 🔍 🕵️
The #BunJS experience
no but in all seriousness it's great, bun.sh ftw
I just did a bunch of reading on #zig (it’s what #bunjs is written in, and I love bun) and now I’m wondering whether I should spend time learning #zig or #rust (which is more mature, and has similar goals but more emphasis on safety).
I’m curious to hear people’s thoughts. It seems like in a nutshell, zig is an rethinking of C and rust is a rethinking of C++ but maybe I’m wrong on that too. Both seem better than go.