Today marks the first illegal Budapest Pride march 🏳️‍🌈 🇭🇺 Just a reminder how brittle democracy can be, despite the citizens becoming more inclusive over time. Evil triumphs when the good do nothing…

Styling HTML form controls is something web designers & developers have wanted for years! My team is working on a solution — apply `appearance: base` and switch to a new interoperable consistent default control. Then override it using new pseudo-elements. See the details: drafts.csswg.org/css-forms/

Here's the math needed to adjust a color's lightness and eliminate the gray area where WCAG2 and APCA conflict on black/white foregrounds. Yes, it's CSS. And yes, it's blazingly fast. Usage: background: oklch⁠(⁠from⁠ ⁠<⁠color⁠>⁠ ⁠var⁠(⁠-⁠-⁠_⁠ak⁠-⁠safe⁠-⁠l⁠)⁠ ⁠c⁠ ⁠h⁠)⁠;

Reduce should never be used with a non-primitive accumulator imo. We have more semantic alternatives like: • Object.fromEntries() + entries​.map() • Object.groupBy() / Map.groupBy() Even for primitives we’ll have Math.sumPrecise() soon ⏳ github.com/tc39/proposa...

Visually-hidden elements should be preferred over explicit labeling. Despite being aware of that, I could never explain the “whys” before this article.

Had to use Safari for browsing the @npmjs.bsky.social ‘Versions’ tab of @astro.build The ‘astro’ package has 1,000+ releases and the associated page just froze while searching on Chrome: www.npmjs.com/package/astr... Perhaps the ‘content-visibility’ CSS property could help? web.dev/articles/con...

Just upgraded kripod.dev to Astro v5. While the migration took some effort, I could pull it off in one go thankfully to the well-written guidelines. It took less than an hour, running stronger than ever 🚀

I wish the @tailwindcss.com will revise some changes before releasing v4, especially concerning accessibility. It’s such a responsibility to get things right at their scale. Perhaps advanced features like breaking out of atomicity might be put behind a flag or at least discouraged by the docs? 🤔

I never really found an ESLint config that’s fairly strict without going overboard So I went through hundreds of core + @typescript-eslint.io rules 1 by 1, hand-picking the severity and options for each. This project culminates all my years of experience with JS/TS so far github.com/kripod/eslin...

The deterministic nature of feeds here feels underappreciated in comparison to X. Finally I don’t lose track of where I’ve been when refreshing. I wish there was a catch-up marker splitting read and unread posts apart, like on Slack.

So ironic how JavaScript is among the most forgiving languages and yet TypeScript offers mind-boggling safety & convenience features built on top of such a flexible base.

“You either die a hero or you live long enough to see yourself become the villain.” Not quite literally but it’s so disheartening to see past role models showing their true colors.

Updated socials on my blog 🦋 to get rid of that confusing ‘X’ icon in the corner. It’s a great relief 💆 www.kripod.dev

Hello, Bluesky 👋 Feeds bring a breath of fresh air over here 🌬️