Sign in with Twitter

Username:

Krist贸f Poduszl贸 馃 @kripod97 Budapest, Magyarorsz谩g

Openly experimenting with the web as a Front-End Developer @UXstudio. Currently working on @UXfolio to make building portfolios a breeze. Views are my own.

223 Following   297 Followers   2,540 Tweets

Joined Twitter 2/13/16


From now, this is my preferred way to manage app state. Building bottom-up, increasing complexity only when necessa鈥 https://t.co/Upitv3UTuc @ryanflorence You might like this one: https://t.co/rnIj7UoVZR
Retweeted by Krist贸f Poduszl贸 馃
9/19
2020
TypeScript 4.1 Beta is now available! Check out what's coming in this release, including template literal types, ke鈥 https://t.co/lebfeePj1E
Retweeted by Krist贸f Poduszl贸 馃
9/18
2020
I just made my first financial contribution towards OSS. @tannerlinsley deserves sponsorship for all the hard work鈥 https://t.co/NQP73gRewS
9/17
2020
This makes Next.js capable of dynamic image optimization at scale. Designed to work with 1 image or 100 million i鈥 https://t.co/5qHfaxDZLI
Retweeted by Krist贸f Poduszl贸 馃I think a lot about how much the idea of 鈥減rofessionalism鈥 is concocted by wealthy white men as a form of gatekeepi鈥 https://t.co/2WkncK6vAD
Retweeted by Krist贸f Poduszl贸 馃
9/16
2020
Today's request for @github. Crossing fingers 馃 https://t.co/G8xgveqCXM
Retweeted by Krist贸f Poduszl贸 馃
9/15
2020
What if we could replace unnecessarily commercialized, exploitative browsers instead? 馃 I鈥檓 wondering what the鈥 https://t.co/lqVuahgGWD @Daniel_Tonon I have no intentions of writing a parser for grid-related properties. No transformation is made other鈥 https://t.co/bdT9pJKYYi @Daniel_Tonon @rendall Great example, I really appreciate it! Changing the readme soon. @Daniel_Tonon @rendall Good idea, I鈥檓 considering it, thank you!Since it keeps being brought up in the context of Moment this weekend: I remain extremely skeptical that sponsorshi鈥 https://t.co/hdy2IOHlX7
Retweeted by Krist贸f Poduszl贸 馃 @kuldeepkeshwar @_philpl @MozDevNet @filbert_js Wonderful, thank you! Feel free to ask if you have any questions 馃槉 @NicoloRibaudo @_jeysal_ @rustlang That鈥檚 great! Sounds like some very interesting material to make videos about, if you have any time 馃槉 @kuldeepkeshwar @_philpl @MozDevNet The code behind tiny-css-prefixer is generated with babel-plugin-codegen, while鈥 https://t.co/r3eiJ1zGiV @_philpl @MozDevNet Aww, I didn鈥檛 mean to make that project obolete 馃槙 Just wanted to do something similar from a n鈥 https://t.co/gi6wRh2I5t
9/14
2020
@souporserious Thank you! No, the alias mapper translates standard property names into their non-standard alternat鈥 https://t.co/Q1UMUHE0Pa @rendall Yes, it鈥檚 like that, but mainly targeted for runtime solutions like CSS-in-JS libraries. Please feel free鈥 https://t.co/zC6h543sbaSpecial thanks to @_philpl for the inspiration by tiny-css-prefixer, and @MozDevNet for providing browser compatibility test vectors! @jon_neal I finally had some time to publish my method of processing mdn-browser-compat-data. Currently using it to鈥 https://t.co/vrdd3T8NNZ @thysultan @probablyup @_philpl It's now available as a standalone package! 馃槉 Feel free to ask if you have any ques鈥 https://t.co/X2mN69xYdmI'm glad to announce style-vendorizer, a tiny CSS vendor prefixer and non-standard property alias mapper within onl鈥 https://t.co/KAwCSn6KKAThis is a must-read: plastic recycling is largely a lie, foisted on consumers by oil companies to make them feel be鈥 https://t.co/klXbVG5MOD
Retweeted by Krist贸f Poduszl贸 馃Finally got around to implementing a custom test matcher for screen reader output https://t.co/uyiaBJDliw https://t.co/2fZkzdjvLc
Retweeted by Krist贸f Poduszl贸 馃
9/13
2020
This would be yet another game-changer: https://t.co/kZvZFYjsre The ability to model type errors themselves. No mo鈥 https://t.co/yzq3Lxuiwi
Retweeted by Krist贸f Poduszl贸 馃Scrapped together a tool that analyzes any npm package and tells you its ES version. 91% of browsers are ES2017-co鈥 https://t.co/555IpRguBO
Retweeted by Krist贸f Poduszl贸 馃
9/11
2020
Depfu looks really promising: https://t.co/wgs3wOI8dn https://t.co/qV6ETu3YPv
9/10
2020
@notrab @github https://t.co/jcCvFFHUGP
9/9
2020
Tailwind almost got everything figured out. The only thing I miss sometimes is style injection on the fly. Atomic C鈥 https://t.co/Ps8sAYdlckAnd it pairs *REALLY* nicely with #ReactQuery IMO. Zustand: Client State React Query: Server State Done. https://t.co/xFIJ9H2T7R
Retweeted by Krist贸f Poduszl贸 馃I found a tool online that creates the code for CSS animations for you. Yes, I could figure it out by myself, but t鈥 https://t.co/Chf7RGxUBL
Retweeted by Krist贸f Poduszl贸 馃The otion project has just received its second financial contribution 馃帀 I'm very grateful for @ruedap and鈥 https://t.co/2WyOZ6fTyH @jon_neal Whoa, you seem to have a project for every CSS-related problem 馃槃 Nice work! It鈥檚 a good idea to make a separate package for this.
9/8
2020
@jon_neal (As the browser IDs used by MDN and Browserslist/CanIUse are not interchangeable, unfortunately) @jon_neal Great! I just came across your Gist and saw that it utilizes network requests. My approach involves using鈥 https://t.co/5Pf1sYoPpZAmazing! 馃挴 https://t.co/xw6Trnn5Ll @jon_neal I鈥檝e also been working on data extraction and processing from MDN lately. My use-case is to provide data-鈥 https://t.co/28gkErjh2y @JoshWComeau Opening modals with consent may also help, I think. Overlays shouldn鈥檛 pop out of nowhere without prior user interaction.Retweeting for reach: A detailed analysis on the UI dev ecosystem would be stunning! https://t.co/1aQ58a6DmNToday I had the chance to set up and try @chromaui for the first time. Visual tests have never been easier to perfo鈥 https://t.co/IaMoXQOUt0 @_philpl @lukejacksonn I鈥檓 so glad for all your OSS contributions. Otion wouldn鈥檛 be the same without tiny-css prefixer. Thank you! 馃槉What a wonderful use of otion! 馃槺 https://t.co/Jp6seMysuU
9/7
2020
Another use of @TypeScript 4.1's template literal types: extracting the URL parameters from an express route. Prett鈥 https://t.co/2MnDOy2IqH
Retweeted by Krist贸f Poduszl贸 馃 @Katy_Wings @tailwindcss Thanks, I鈥檒l do my best! 馃槉 @Katy_Wings @tailwindcss Yes, I鈥檓 implementing a complete design with pre-defined tokens and components available.鈥 https://t.co/M00KJhV6Yt
9/5
2020
The Google Chrome team wrote a RFC for an image components built into Next.js: 鈼 Aims to improve performance (LCP鈥 https://t.co/TL3curL51Z
Retweeted by Krist贸f Poduszl贸 馃I've just created a @tailwindcss proposal for polyfilling flex gap properties. The implementation is already availa鈥 https://t.co/DqLRF4OuU1Mind-blowing! 馃槺 Imagine all the possibilities with TypeScript 4.1鈥 The next generation of template metaprogramming鈥 https://t.co/K7kTLLjGUB @harrysolovay What an idea! I鈥檒l definitely keep that in mind, thank you! 馃槉 @Katy_Wings @tailwindcss It鈥檚 a breeze, things are so fast and convenient to do with configurable utilities. I even鈥 https://t.co/1O83sUgp6w @harrysolovay It opens wonderful new possibilities for sure, especially when it comes to theming. For instance, we鈥 https://t.co/ON7lDQDMFO
9/4
2020
Using HTML, but just the `div` element 鈥s the same as鈥 Using TypeScript, but just the `any` type 鈥r鈥 Building鈥 https://t.co/rSps0UaRzF
Retweeted by Krist贸f Poduszl贸 馃 @_philpl @peduarte Yeah, exactly! I鈥檓 also working on a value prefixer and an alias mapper between standard and non-standard properties.You might of missed this is the web of replies in the other thread. But this is the magnitude of the sort of change鈥 https://t.co/hOljrzcshK
Retweeted by Krist贸f Poduszl贸 馃Hopefully, the library I'll be including this in will never need any additions. The time of vendor prefixes has com鈥 https://t.co/On9JlnT90GThe function returns boolean flags about which vendor prefixes should be prepended to the given property: 鈥 0b001鈥 https://t.co/OO4E9RGoVx @peduarte Similar solutions have been in use for a while (e.g. in Preact or even jQuery), but tiny-css-prefixer by鈥 https://t.co/NZny56A2HW @peduarte It took quite a bit of time to gather and then verify every property to be prefixed. I even downloaded Ch鈥 https://t.co/X0Ta4nx70jSupported Browsers: - Baidu Android 7.12+ - Chrome 83+ - Chrome Android 81+ - Edge 18+ - Firefox 77+, ESR 68 - Fir鈥 https://t.co/auI9xdaE2IBrowserslist-based modern CSS property prefixer in a tweet 鈥 Coming Soon function prefix(e){var o=/^(?:(text-(?:de鈥 https://t.co/PnO59b72qo @crswll @malfaitrobin You may want to give react-polymorphic-box a try 馃槉 https://t.co/gtYTQsA8M7 @ryanmr Me too. Components should encapsulate multiple HTML elements or offer a common styling *and behavior* for a鈥 https://t.co/UofoayjitP @ryanmr Yeah, that鈥檚 a nice analogy indeed, thank you! @aarongarciah Yeah, that sounds like a plan! 馃檶 General availability of the gap property would make all the layout鈥 https://t.co/OlujKnMa2HLayout components start to feel limiting in contrast to what鈥檚 possible with utility classes Also, there isn鈥檛 a s鈥 https://t.co/1lcKGp7jAIMy guess would be that Tailwind components could reduce the need for polymorphism. However, polymorphism in React鈥 https://t.co/itNSoYjKU6Working with Tailwind CSS was a pleasure today. I鈥檓 curious about when to abstract away React components from inlin鈥 https://t.co/njNpD3yxYx @peduarte @TailwindcssBot Yeah, it's just plain wrong鈥 In before people start making bots for technologies they do鈥 https://t.co/4dcSj3VdhE @kentcdodds @Listefano_ @tailwindcss I may be a bit late to the party, but this @PrettierCode plugin looks even mor鈥 https://t.co/aFjewvOPSKThis is so cool! A @PrettierCode plugin for @tailwindcss which is editor-independent, but follows the ordering rule鈥 https://t.co/wvpMRgR1eN @jamannnnnn @tailwindcss Otion is still under development. As the deadline for the product is very close, I decided鈥 https://t.co/WjZNZpGmoF @ryanmr @tailwindcss I鈥檓 really excited about exploring it. At the company I鈥檓 working at, we already have a design鈥 https://t.co/b2BRF9stAr
9/3
2020
I think it's really important to include situational disability (ie. holding a baby) & temporary disability (ie. br鈥 https://t.co/16quOHOsLV
Retweeted by Krist贸f Poduszl贸 馃I鈥檓 eager to try @tailwindcss tomorrow for the first time, along with my CSS reset based on comparing browser UA st鈥 https://t.co/2XzzbW5ApQFeels like a very significant DX improvement over the original behavior. I鈥檒l definitely give this a try! https://t.co/qRsVdQvltP @flybayer Awesome! A GUI for setting up applications like that would be mind-blowing 馃くOtion, the atomic CSS-in-JS library, has just reached 400 猸愶笍 Thanks for all the support I鈥檝e got! It feels like a鈥 https://t.co/ZAjR1w680r
9/2
2020
Looks very promising, I鈥檓 looking forward to see the friendly competition between CSS-in-JS solutions unfold 馃槉 https://t.co/LNGYMtRBo2 @buildsghost @souporserious @marvinhagemeist I also prefer using a vertical Stack component and a horizontal but wr鈥 https://t.co/5d353VMqojSwiftUI inspired Web Components using preact-custom-elemet and otion 鈿涳笍馃寠馃槏 thanks for these wonderful libraries鈥 https://t.co/095jJLooXa
Retweeted by Krist贸f Poduszl贸 馃 @jamesqquick I鈥檝e been working on atomic CSS-in-JS solutions with a microscopic footprint. Being very interested in鈥 https://t.co/pQbIDQ7X0hWhoa, CSS vendor prefixes are getting way easier to type properly 馃槃 https://t.co/03BnRymSGt @RiaCorpeno Emotion for sure 馃槄
9/1
2020
Let's just take some time to appreciate all the efforts invested in writing code with output minification in mind 馃槃鈥 https://t.co/IdYC4zXVYmQuick question 馃敟馃挩 In React, and many CSS-in-JS libraries, unitless CSS values get converted to px This: <div styl鈥 https://t.co/kxdJxjZUIf
Retweeted by Krist贸f Poduszl贸 馃 @peduarte Also, from a library authoring perspective, maintaining the list of unitless properties can be cumbersome鈥 https://t.co/ScaTt5GKO1 @peduarte I used to like the numeric syntax, but it may be confusing with design system tokens in place. For insta鈥 https://t.co/7J0jPKql3m @harrysolovay @tinkertamper Thank you, that really just made my day 鈽猴笍
8/31
2020
I'm done collecting prefixes and aliases for CSS properties and values. Now it's time to work on some regular expre鈥 https://t.co/EflfUVniXU @sitnikcode @caniuse No, I meant a build-time size reduction, as the amount of required vendor prefixes will be low鈥 https://t.co/MH5J8SYI5s
8/30
2020
As I'm working on a new lightweight CSS autoprefixer, I came across some missing info for mdn/browser-compat-data (鈥 https://t.co/pFPU4ZTuFWLearning about Erlang made me a better TypeScript programmer. The former knowledge feels almost invaluable when I鈥檓鈥 https://t.co/bGDjLznxkCThis looks great, but be reminded about the capabilities of progressive enhancement and only block legacy browsers鈥 https://t.co/CqrSCPK2gV @peduarte @Modulz Awesome, I'm eager to see what you've come up with 馃檶#StyledComponents has the same behavior. No matter what a media query refers to, the last one being composed should鈥 https://t.co/vDofm4W9KeWondering how the atomic CSS-in-JS library of @Modulz will solve this: https://t.co/nGpRSC6ajIDo we need composition for CSS media queries? E.g.: compose( { "@ media(min-width: 600px)": { color: "鈥 https://t.co/cDEcKQ5eFF
8/29
2020
I've just polished the code for retrieving alternative CSS property names in use with @Browserslist and @MozDevNet'鈥 https://t.co/MqnNX2jOoe @traversymedia I鈥檝e just started working on my own lightweight CSS prefixer, based on Browserslist and MDN Browser Compat Data @siddharthkp @chromaui Goreous, thank you!
8/27
2020

0