fancypenguin.party - Profile | ThreadSky | a Reddit-style client for Bluesky

fancypenguin.party

Engineer, reader, amateur artist in many forms, sometimes writer, Pac-Man aficionado. CTO at The Astro Technology Company https://astro.build/ Builder of https://yums.email/

804 posts 2,325 followers 552 following

Posts 13 Comments 37

"____ is inaccessible" is very rarely a true statement. Accessibility is not a boolean. Doing one thing can reduce inaccessibility for one set of users but improve it for another. Reducing accessibility in one place can be compensated for in another. UX is a balancing act, accessibility is as well.

submitted 5 hours ago • 0 comments

My favorite new thing is function scoped types like `type Foo = ....`. Most code I read uses module-scoped types almost exclusively. This is how I've always done it in the past too. But why not scope it to where it's actually used?

submitted 2 days ago • 1 comment

Reactivity is just not good at side-effects. It doesn't matter if its hooks based or signals or anything else. That's really the fundamental problem. You inevitable run into "why did this run" questions. Because reactivity is meant to run arbitrarily. Square peg, round hole.

submitted 6 days ago • 4 comments

Half-baked idea: client state management that's purely derived from an append-only log.

submitted 7 days ago • 2 comments

Me: Unhinged rant on something technical that less than 10 people agree with me on. LLM: You've nailed it.

submitted 8 days ago • 1 comment

I had planned a post about reactivity for my newsletter next week, but this Remix stuff is too juicy to not write about. So yeah, that's going to be my topic for next week. Subscribe link below. 👇

submitted 8 days ago • 1 comment

i was born to make websites, fun websites, silly websites, curious websites, websites that bend, delight, amuse and entertain, websites for people on planet earth and there will be no shareholder value, but the websites will be built, and they will be enjoyed

submitted 9 days ago • 7 comments

Preact now powers more major frameworks than React.

submitted 8 days ago • 0 comments

Node.js is thriving. It's not dying. Join me at JS Nation to know why. → My talk: The State of Node.js 2025. Get ready to debunk the myths. → Enhancements? Plenty. Recent updates make it stronger than ever. → Performance? Remarkable. Node.js shines in server-side programming.

submitted 8 days ago • 2 comments

The new test for LLMs coding ability is giving it a challenge for writing complex type-level TS. Consistently seeing current gen struggling with it. Not sure what a good test would actually look like.

submitted 8 days ago • 1 comment

"____ is inaccessible" is very rarely a true statement. Accessibility is not a boolean. Doing one thing can reduce inaccessibility for one set of users but improve it for another. Reducing accessibility in one place can be compensated for in another. UX is a balancing act, accessibility is as well.

My favorite new thing is function scoped types like `type Foo = ....`. Most code I read uses module-scoped types almost exclusively. This is how I've always done it in the past too. But why not scope it to where it's actually used?

Reactivity is just not good at side-effects. It doesn't matter if its hooks based or signals or anything else. That's really the fundamental problem. You inevitable run into "why did this run" questions. Because reactivity is meant to run arbitrarily. Square peg, round hole.

Half-baked idea: client state management that's purely derived from an append-only log.

Me: Unhinged rant on something technical that less than 10 people agree with me on. LLM: You've nailed it.

I had planned a post about reactivity for my newsletter next week, but this Remix stuff is too juicy to not write about. So yeah, that's going to be my topic for next week. Subscribe link below. 👇

i was born to make websites, fun websites, silly websites, curious websites, websites that bend, delight, amuse and entertain, websites for people on planet earth and there will be no shareholder value, but the websites will be built, and they will be enjoyed

Preact now powers more major frameworks than React.

Node.js is thriving. It's not dying. Join me at JS Nation to know why. → My talk: The State of Node.js 2025. Get ready to debunk the myths. → Enhancements? Plenty. Recent updates make it stronger than ever. → Performance? Remarkable. Node.js shines in server-side programming.

The new test for LLMs coding ability is giving it a challenge for writing complex type-level TS. Consistently seeing current gen struggling with it. Not sure what a good test would actually look like.

NASA needed a new site that was out of this world Houston, we have a solution kennedyspacecenter.com, built with Astro + WordPress

Peas are very gross

Blogs are dying, again. outbox.matthewphillips.info/archive/seco...