raf-signal: shared requestAnimationFrame scheduler.
Coalesces all rAF callbacks into one, reduces main thread overhead & makes frame timing predictable.
Useful for animations, Canvas, WebGL & game loops.
#javascript#performance#requestAnimationFrame
https://t.co/TntIygfhnA
First snow about to fall here in Calgary βοΈ Drew it on my canvas before it hits the ground. Thanks @code_laboratory for amazing lessons; pure excellence!
#CreativeCoding#JavaScript#Canvas
https://t.co/MMBQjNy7rx
And thatβs the difference between Promise.all() and Promise.allSettled(). Use Promise.all when all promises need to succeed together, and Promise.allSettled when you want to handle every result, success or failure. Debug smarter!
Writing await Promise.all() without understanding how it handles rejections is a rite of passage for every JS dev. Pro tip: one failure doesnβt just fail the taskβit nukes the whole operation. Handle errors smarter ...π§΅
Promise.allSettled(): It waits for every promise to finish, no matter what. You get a status (fulfilled or rejected) and value/error for each promise. Perfect for partial success cases.
Promise.all(): It short-circuits. If one promise rejects, the whole operation stops, and you get the rejection. Great when all promises must succeed together.
Letβs dive into error handling with Promise.all() and Promise.allSettled(). These two methods might seem similar, but their behavior with errors is vastly differentβand knowing when to use each is key. π
π Just launched Buflux: a high-performance buffer for Node.js & browsers!
β Fixed-capacity
β Overflow strategies: EVICT/REJECT
β Event-driven & zero deps
Perfect for task queues, caching & rate-limiting!
https://t.co/sZ48g346ab
#nodejs#javascript#queue#buffer
What a remarkable BFCM weekend. The power of entrepreneurship was on full display. Congrats everyone.
β£ $11.5B global sales on Shopify, up 24% on last year
β£ 76M+ people bought from Shopify-powered brands, up 25% on last year
β£ 67,000+ merchants had their highest-selling day ever
β£ 16,500+ entrepreneurs made their first sale
β£ 57.3 PB of data processed and served from our infrastructure
β£ 1.19 trillion total edge requests
β£ 10.5 trillion total database queries
β£ 1.17 trillion database writes
Yesterday was an incredible day for our merchants and for Shopify:
* Merchants drove a record-breaking $5 billion Black Friday in sales (GMV)
* Peak sales / minute for yesterday = $4.6 million
* Shopify's egress processed more than 173B requests
* Peak requests per minute was at 284 million on edge, with more than 80 million on app servers pushing 12TB a minute
* 45 million peak database queries per second, peak database writes was 7.6 million per second
* We rely on Kafka. At peak we hit 66 million messages per second
Let's keep going π₯
Recursive templating can be tricky, especially when base conditions are driven by API data. It's akin to painting a tree in the browser with wildly growing nodes, until your browser crashes from memory leaks!