Justin Fagnani
banner
justinfagnani.com
Justin Fagnani
@justinfagnani.com
Building something new... Previously at Google. Web maximalist. Web components. Creator of Lit. Oakland.
So you build even more. The solution to too much demand is more supply.

But a huge problem is building codes that make it very difficult to build enough 3+BR apartments. When I was looking for my family, they were incredibly rare.
January 13, 2026 at 5:54 PM
We just need Safari to get off the pot, and for `@sheet()` to move forward, and we're in business!
January 13, 2026 at 5:35 PM
Reposted by Justin Fagnani
The Minneapolis observers are driving them absolutely crazy and they're likely spending as much time fighting against us as they are doing abductions - which is good, and the goal - but also deranged. At this point their primary mission is terrorizing the people who oppose them being here.
January 12, 2026 at 5:26 PM
Ironically, the first framework to actually go to space used HTML Imports! 😳
January 11, 2026 at 11:27 PM
Yeah, I didn't want to bake anything in at this point. The existing signals package should be easy to copy tho.

One big change I want to make is fused function return and signal update messages, so if you call a mutation fn, you know all the signals it changed are updated when the fn returns.
January 11, 2026 at 5:15 PM
Via this same extension API (similar to Comlink's but locally configured and allows for subscriptions) I plan to add Observable, Map & Set, and DOM Event support packages.
January 11, 2026 at 1:45 AM
I also added a signals integration package: get signals from the worker, and when they update in the worker then update on the receiver side!

www.npmjs.com/package/@sup...
www.npmjs.com
January 11, 2026 at 1:43 AM
Supertalk is highly inspired by Comlink ❤️

But it does things for me that I found hard to get Comlink to do with very complex data structures and async flows. Things like auto-proxying of function arguments and returns, nested proxy handling, & tighter TypeScript types.
January 11, 2026 at 1:43 AM
I think using metadata as keys into maps is strictly better. No multi-actor or prototype concerns ever.
January 10, 2026 at 10:03 PM
I would treat the metadata object as opaque myself, and only use it as a key into maps. I think it was a mistake to make it mutable.

You'd also hit problems if you happened to have another decorate that used a .properties property on metadata.
January 10, 2026 at 3:47 PM
Do you think the Wiz really want to keep Trae, or is this another step in the long Beal trade?

Can they convince Trae to play defense?

Will they shut Trae down for the season to preserve the tank?

Given the choice, do they draft Peterson, or go with Dybantsa to pair w/ Trae (or b/c durability)?
January 8, 2026 at 11:25 PM
Kind of funny, but it would hit a lot harder if Obama were a little more vocally anti-fascist right now.
January 8, 2026 at 10:31 PM
The risk is they win and lose out on Peterson or Dybantsa. It would be soo Wizards to screw up the tank in the last year of needing to suck.
January 8, 2026 at 3:07 AM