Kristóf Poduszló (@kripod97) profile picture

Software engineer with a special interest in accessibility. Builds for the web, mainly using React and Tailwind CSS nowadays. Currently @Rollstack, ex-@Wise.

Budapest, Hungary
Joined February 2016
Photo by Kristóf Poduszló (@kripod97)Photo by Kristóf Poduszló (@kripod97)Photo by Kristóf Poduszló (@kripod97)Photo by Kristóf Poduszló (@kripod97)Photo by Kristóf Poduszló (@kripod97)Photo by Kristóf Poduszló (@kripod97)Photo by Kristóf Poduszló (@kripod97)Photo by Kristóf Poduszló (@kripod97)Photo by Kristóf Poduszló (@kripod97)Photo by Kristóf Poduszló (@kripod97)
New article about type-safe polymorphism in React ⚛️ Addressing a long-standing performance issue within `@​types/react` in the process, this took quite some time to write. Let your peers know about getting the ‘as’ prop right 🔁 kripod.dev/blog/behind-the-a…
3
3
1
16
2,553
Ten years of accessibility links in a private note. One question kept coming back. Who decided this, and where do I go to disagree? There’s almost always an answer, and it’s rarely where you’d look first. kripod.dev/blog/accessibilit…
2
186
🦋 @​kripod​.dev
1
129
Kristóf Poduszló retweeted
Congrats to the team @Rollstack (YC W23) on the $11M Series A! Rollstack automates your data-driven slide decks and documents using AI. rollstack.com/articles/rolls…
4
14
1
81
16,759
Kristóf Poduszló retweeted
More design systems should use utilities over style components. 🚫 <Box as="section" bg="red-400"> <Text font="body-xl"> <HeadlessButton as={Box} bg="blue-400" /> ✅ <section className="bg-red-400"> <span className="font-body-xl"> <HeadlessButton className="bg-blue-400" /> This might look slightly longer, but gives you flexibility to apply styles to any component or element, with no need for polymorphism (which might not even be supported on every component). You can also create utility functions that apply multiple properties, and give you autocomplete, type checking, and design system constraints: <ul className={stack({density: 'spacious'})}> Separating reusable styles and reusable behavior (e.g. headless components) makes it super flexible to apply the design system anywhere you need to. This makes it extensible to new use cases with much less complexity.
28
31
7
458
79,752
Happy to announce that I’m starting @Rollstack as a Senior Software Engineer next week 🎉
5
136
I’m excited to publish juvo, a balanced design system built around the @evilmartians Harmony color palette. Especially proud about how `TextBoxGroupProvider` turned out for attaching addons on top of inputs. github.com/kripod/juvo
1
13
602
Who knew that a post about HTML paragraphs—or, more accurately, paragraphs in HTML—could be so entertaining. You may (and probably will) learn a fun new thing or two. Fun but also practical. Strongly recommend read 👇
paragraphs. i wrote about freakin paragraphs. scottohara.me/blog/2024/08/2…
6
50
6,399
Kristóf Poduszló retweeted
Or use this CSS: ``` .log { scroll-snap-type: y proximity; align-content: end; } .log::after { display: block; content: ""; scroll-snap-align: end; } ``` “… remains snapped to the bottom …unless the user has scrolled away from that edge” — drafts.csswg.org/css-scroll-…
To automatically scroll down when new messages arrive in an chat like Chat-GPT, use the following hook.
8
69
7
947
102,131
Kristóf Poduszló retweeted
📝 I set off to find the best way to make video with transparency work on the web. Over 10 bug reports later, it turns out it's better to handle the transparency manually with WebGL. Here's how: jakearchibald.com/2024/video…
21
39
254
51,340
Kristóf Poduszló retweeted
Here it is! Patterns for Memory Efficient DOM Manipulation in Modern Vanilla JavaScript frontendmasters.com/blog/pat…
13
89
19
539
105,679
24px? 44px ? Wait, 48dp on Android, hu? What is the size of an accessible button exactly? Well, it depends (haha). @ericwbailey clarifies a lot of miss conceptions around the minimum WCAG-conformant interactive element size.
1
13
62
5,854
Kristóf Poduszló retweeted
🚀 New in-depth article! A complete guide on how, when, and why you should make your components composable. I put a lot of effort into this one, it even contains an interactive component API design wizard! dio.la/article/the-everythin…
6
18
3
120
11,722
What a bittersweet moment to end the last @jsconfbp with 😫 And yet @AnjanaVakil & @TejasKumar_ kept our chins up all the time. This picture doesn’t do justice to how incredible all the speakers and organizers are 👏👏👏
1
4
13
1,260
Key takeaway is to hydrate as if you were a React component to get all the cheers on stage 😄
1
84
“Being a developer is an inherently creative profession” — @hey_amandam gets it 💯 @jsconfbp We all need the space to embrace our childlike curiosity.
2
7
254
Temporal is here to save the day for the web – amazing overview by @NicoloRibaudo presenting new JS features @jsconfbp ✨
2
10
542
🌶️ take: Next.js 15 is what v14 pursued to be And I’m happy for them to fix all the major pain points emerging with the app router 🎊
Next.js 15 RC ◆ React 19 + React Compiler support ◆ `fetch` and Route Handlers no longer cached by default ◆ Incrementally adopt Partial Prerendering ◆ New `create-next-app` design ◆ next/after (Experimental) nextjs.org/15-rc
2
209
Or just think about `useState` as an instance variable with a getter and an optional setter returned as a tuple.
Even better, hide it so you show intent and have less questions in PRs asking if it's a mistake or not
120
Kristóf Poduszló retweeted
it'd be so cool if someone could make compiler theory content more accessible by taking apart the react compiler this is the first time i've seen traditional compiler optimisations implemented in an accessible language
2
2
2
67
8,330
Kristóf Poduszló retweeted
My "as few deps as possible" monorepo setup
25
38
4
672
64,137