I’ve been benchmarking it a bunch and it seems like we’re the fastest Node.js tar library on all benchmarks.
Especially in a big way for many small files which are typical for node_modules like directories 🚀
I’ve been benchmarking it a bunch and it seems like we’re the fastest Node.js tar library on all benchmarks.
Especially in a big way for many small files which are typical for node_modules like directories 🚀
huge thanks to everyone involved 🎉 much more to come very soon, and we have a roadmap of some super useful tools in the works
huge thanks to everyone involved 🎉 much more to come very soon, and we have a roadmap of some super useful tools in the works
#golang
https://blog.cloudflare.com/unpacking-cloudflare-workers-cpu-performance-benchmarks/
https://blog.cloudflare.com/unpacking-cloudflare-workers-cpu-performance-benchmarks/
We originally converted Web Streams into Node Streams to make maintaining cross compatibility manageable… but synchronising those two felt very incomplete and was prone to so so many race conditions 👾
We originally converted Web Streams into Node Streams to make maintaining cross compatibility manageable… but synchronising those two felt very incomplete and was prone to so so many race conditions 👾
After joining the @opensourcepledge.com last year, we are increasing our annual commitment to $48,360 for 2025.
Take a look at our full 2025 report on which vital projects we're sponsoring and how the money is distributed.
voidzero.dev/posts/oss-pl...
After joining the @opensourcepledge.com last year, we are increasing our annual commitment to $48,360 for 2025.
Take a look at our full 2025 report on which vital projects we're sponsoring and how the money is distributed.
voidzero.dev/posts/oss-pl...
Uninlined generic functions have a "dict" arg, since Go generics are neither erased nor monomorphized, but instead instantiated for each "GC shape" (e.g. T=*int and T=*float64 get the same code, but T=int32 and T=int64 do not).
Uninlined generic functions have a "dict" arg, since Go generics are neither erased nor monomorphized, but instead instantiated for each "GC shape" (e.g. T=*int and T=*float64 get the same code, but T=int32 and T=int64 do not).
But I absolutely enjoy working with JavaScript as a hobby, whilst Go feels a little bit more like a chore.
Both communities are 🔥 though
But I absolutely enjoy working with JavaScript as a hobby, whilst Go feels a little bit more like a chore.
Both communities are 🔥 though
I don’t expect it to be faster at all as some alternatives use specialised dependencies to replace Node streams entirely. But I also don’t believe the difference is significant.
I don’t expect it to be faster at all as some alternatives use specialised dependencies to replace Node streams entirely. But I also don’t believe the difference is significant.
I just released a new zero dependency streaming tar parser and writer that is built with the browser-native Web Streams API!
Please check it out! It's awesome 📼
github.com/ayuhito/mode...
I just released a new zero dependency streaming tar parser and writer that is built with the browser-native Web Streams API!
Please check it out! It's awesome 📼
github.com/ayuhito/mode...
Here's the post: brooker.co.za/blog/2025/09...
Here's the post: brooker.co.za/blog/2025/09...
⚡ macOS Performance Boost: 10%-30% faster bundling, up to 45% in extreme cases.
🎯 Cross-Chunk Optimization: Support for __NO_SIDE_EFFECTS__ annotation, as well as
better tree-shaking across module boundaries and more efficient DCE
⚡ macOS Performance Boost: 10%-30% faster bundling, up to 45% in extreme cases.
🎯 Cross-Chunk Optimization: Support for __NO_SIDE_EFFECTS__ annotation, as well as
better tree-shaking across module boundaries and more efficient DCE
Google Fonts is incredibly dynamic serving completely different files depending on your useragent, so often there are tradeoffs that lead to worse situations for one type of user over another
Google Fonts is incredibly dynamic serving completely different files depending on your useragent, so often there are tradeoffs that lead to worse situations for one type of user over another
if it works out, it lets us close tons of issues and even makes reaching the fabled zero issues repo a realistic goal!
if it works out, it lets us close tons of issues and even makes reaching the fabled zero issues repo a realistic goal!
webassembly.org/news/2025-09...
This includes major features like GC, 64-bit memories, exceptions, and tail calls.
webassembly.org/news/2025-09...
This includes major features like GC, 64-bit memories, exceptions, and tail calls.
With a ready to use GC and a packed standard library for I/O, I wonder if JS->Go native could be a thing.
(There’s definitely limitations, but it could be worth it)
With a ready to use GC and a packed standard library for I/O, I wonder if JS->Go native could be a thing.
(There’s definitely limitations, but it could be worth it)