Challenge 3:
Dog

#pa

Pooya is cooking

https://x.com/_pi0_/status/2100678127580287044

Advocaat: https://github.com/pithings/advocaat

#jev

Challenge 4:
Tree

#pa

And a Gmail widget (WIP)

#qs

Node.JS 26.10.0 has added built-in throttle and debounce utilities 🎉
Time to upgrade and ditch the third-party libs.

import { throttle } from 'node:util';

const request = throttle(async (id) => {
  const response = await fetch(`https://example.com/items/${id}`);
  return response.json();
}, 2, 1_000);

// At most two requests begin during each one-second interval. All other calls
// remain queued and retain their original arguments.
const results = await Promise.all([
  request(1),
  request(2),
  request(3),
  request(4),
]);

#nodejs #news

There's been a lot of discussion around out-of-order HTML streaming.
The idea is simple, stream the parts of the page that are ready immediately, leave placeholders for the parts that are still being computed, and patch those placeholders later as the data becomes available.

This maps naturally to how most web applications work. different pieces of data resolve asynchronously. Modern frameworks already take advantage of this, but until now they’ve needed framework-specific JavaScript and conventions to make the streamed pieces land in the right place.

The good news is that this capability is now part of HTML itself!
The newly added <template for> allows a later part of the HTML stream to target a marker earlier in the document and replace it (without JavaScript).

For example, the server can immediately send:

<main>
  <h1>My dashboard</h1>

  <?start name="recommendations">
    <div class="skeleton">Loading recommendations…</div>
  <?end>

  <p>The rest of the page can continue streaming…</p>
</main>

While recommendations are still being computed.
Later, when they're ready, the same response can stream:

<template for="recommendations">
  <ul>
    <li>Declarative Shadow DOM</li>
    <li>View Transitions</li>
    <li>Popover API</li>
  </ul>
</template>

The browser replaces the placeholder range with the template contents.

No client-side script looking up an ID.
No custom payload format.
No framework-specific DOM patching runtime.
Just HTML arriving asynchronously and the browser putting it where it belongs.

Read the WICG
Proposal Issue
WHATWG PR

#html #news

This is mind blowing.
Video: https://www.youtube.com/watch?v=5EoO5413dBY
Repo: https://github.com/mexicat/pdoom-video/tree/main

#ai #art

Challenge 5:
Button

#pa

I'm refactoring the shell to make the UI more consistent. To achieve that, I'm implementing a QML module based on Google Material Design 3.

#qs

Challenge 6:
Boy

#pa

Knowledge Universe.

#design

Challenge 7:
Giraffe

#pa

Challenge 8:
Bush

#pa

Here is how I create these arts (I forgot to record the first 10 minutes)

#pa