Post

I did some writing about @nodejs.org streams earlier this year that I think you will all enjoy. First article is about custom stream implementations, and the second is all about optimization. Enjoy ✨ 🚀 🐢 ethanarrowood.com/blog/buildin... ethanarrowood.com/blog/profili...

ethanarrowood.comBuilding Custom Node.js Streams: Splitting a 1GB File Without Running Out of Memory | Ethan ArrowoodWhat started as generating prime numbers for Project Euler problems evolved into a ~1GB file that broke my development tools. Follow along as I build custom Node.js Writable and Transform streams to e...

24/6/26, 11:31 pm3 reposts18 likes

tierney cyren

@bnb.im

25 June

If you’ve got a bit of spare time (I know you probably don’t) you should try setting up your blog to integrate into the atmosphere with standard.site :)))

standard.siteStandard.site - One schema. Every platform.Standard.site provides shared lexicons for long-form publishing on AT Protocol. Making content easier to discover, index, and move across the ATmosphere.

Ethan Arrowood

@arrowood.dev

25 June

It’s on the list! I’m only learning about atproto now so diving headfirst into all of it as much as I can

tierney cyren

@bnb.im

25 June

hell yeah, it’s super sick. Legitimately the first software I’ve been excited about since AI made everything… much less fun.

Alexey Chechet

@gissen-dev.bsky.social

25 June

the bit that'll stick: 33k garbage collections that turned out to be ~4% of runtime. counting --trace-gc lines instead of summing pause times is such an easy trap as it makes the output stream look like a crime scene when it's just noise 👌