Didn't actually get the difference between specifying desired state at "50%" instead of "to" (with "alternate" and half of duration)
@himalayagupta774429 күн бұрын
You talk more instead of the real content. Show me what I am here for.
@DavidEast28 күн бұрын
Yes my bad. I lost the screen recording. Stay tuned for the next episode. There will be a lot more.
@himalayagupta774428 күн бұрын
@@DavidEast ok waiting subscribed for that
@xkeshav29 күн бұрын
using `will-change` property can help us to re paint better
@xkeshav29 күн бұрын
Today I thought the same about the sibling thing because nth-child have value but we can't get it.
@camoman100029 күн бұрын
There is a count() that counts the number of elements selected I believe...
@patriciocifredo29 күн бұрын
cool hack! :)
@jadenmartАй бұрын
We need more of the screen. You talk how cool it is and we can't see it
@Killyspudful29 күн бұрын
Agreed - share your screen, please :)
@DavidEast29 күн бұрын
This was a big fail by me. I lost the screen recording so I tried to edit in the keyframe code. We have another visual episode planned and I promise we'll have a lot more to share.
@johnrioАй бұрын
+1 on the "dumb/thin" container node just for setting name/type. Ive been shipping production container queries for a while now and this saves the headache of remembering which properties are/aren't off limits to change because you set them on the root container. Everything is fair game.
@DavidEastАй бұрын
It takes a bit of thinking upfront but it saves so much time in the long run. Thanks for giving us a listen 🙏
@CraigShearerАй бұрын
Great content! You need more subscribers!
@AlexisMorin3 ай бұрын
I'm so excited for color-contrast 👏 here's to hoping it moves forward!
@claasdev3 ай бұрын
I felt this episode. Another fun quirk I encountered with range inputs is that they scroll the page on touch as soon as you use custom styles for them
@AlexisMorin3 ай бұрын
I'm onboard with David. GUI Challenges were flawless execution. I had nothing to contribute to that conversation. After years of watching Adam's content, I know the humility is real but as an audience, we're usually not even gonna try to improve something made by a Googler.
@brianmpdotdev3 ай бұрын
So glad y'all are bringing this back! I've learned a whole lot from the episodes so far!
@DavidEast3 ай бұрын
fun fact: I built the badatcss site without a single CSS class. Don't look it's really bad lol
@simonswiss3 ай бұрын
Amazing conversation! I absolutely love CSS and funnily enough I love Tailwind because it lets me write the CSS I want in a way that can survive all the curved balls of life, marketing department, performance etc. I know many people use Tailwind to "avoid learning CSS" - but I see Taliwind as a tool to write CSS - I use mini classes but I know exactly what CSS I am composing with it, instead of writing it by hand. And Tailwind is an excellent tool to teach CSS, thanks to the Intellisense hover info. I still get told to "just learn CSS" every week, but oh well 🤣
@simonswiss3 ай бұрын
Damn that Argyle intro was FIRE
@AlexisMorin4 ай бұрын
Magic Move is Keynote :P
@keteremillpario5 ай бұрын
Thank you for this, I needed it. Adams take are like oxygen to me 🤗
@SebastianFinkel7 ай бұрын
This was so funny! 😂 Thank you, I enjoyed it very much!
@oenophile7 ай бұрын
Appreciate the container query confession. I'm not alone!
@cdvillard7 ай бұрын
That intro, wow!
@JaneOri7 ай бұрын
Great episode. Loved hearing pro CSS Modules discussion and 55:30 Totally 100% agree with Jason here. Back in the day, CanJS was easily my favorite framework. Cool ideas, great code structure, fun to use... then they released like 3 major versions in a short span of time and, totally predictably, fractured and killed almost all the small brand loyalty it had. Such a bummer because CanJS is awesome.
@JaneOri9 ай бұрын
Adam's argument at 38:29 was so well said, completely accurate, and absolutely hilariously perfectly delivered 👏😂
@abenezermelaku28829 ай бұрын
I'm bad at css I need help 😅😅
@frontendfyi10 ай бұрын
This is so great! We need more humble content like this! Thank you so much for making this!
Пікірлер
Didn't actually get the difference between specifying desired state at "50%" instead of "to" (with "alternate" and half of duration)
You talk more instead of the real content. Show me what I am here for.
Yes my bad. I lost the screen recording. Stay tuned for the next episode. There will be a lot more.
@@DavidEast ok waiting subscribed for that
using `will-change` property can help us to re paint better
Today I thought the same about the sibling thing because nth-child have value but we can't get it.
There is a count() that counts the number of elements selected I believe...
cool hack! :)
We need more of the screen. You talk how cool it is and we can't see it
Agreed - share your screen, please :)
This was a big fail by me. I lost the screen recording so I tried to edit in the keyframe code. We have another visual episode planned and I promise we'll have a lot more to share.
+1 on the "dumb/thin" container node just for setting name/type. Ive been shipping production container queries for a while now and this saves the headache of remembering which properties are/aren't off limits to change because you set them on the root container. Everything is fair game.
It takes a bit of thinking upfront but it saves so much time in the long run. Thanks for giving us a listen 🙏
Great content! You need more subscribers!
I'm so excited for color-contrast 👏 here's to hoping it moves forward!
I felt this episode. Another fun quirk I encountered with range inputs is that they scroll the page on touch as soon as you use custom styles for them
I'm onboard with David. GUI Challenges were flawless execution. I had nothing to contribute to that conversation. After years of watching Adam's content, I know the humility is real but as an audience, we're usually not even gonna try to improve something made by a Googler.
So glad y'all are bringing this back! I've learned a whole lot from the episodes so far!
fun fact: I built the badatcss site without a single CSS class. Don't look it's really bad lol
Amazing conversation! I absolutely love CSS and funnily enough I love Tailwind because it lets me write the CSS I want in a way that can survive all the curved balls of life, marketing department, performance etc. I know many people use Tailwind to "avoid learning CSS" - but I see Taliwind as a tool to write CSS - I use mini classes but I know exactly what CSS I am composing with it, instead of writing it by hand. And Tailwind is an excellent tool to teach CSS, thanks to the Intellisense hover info. I still get told to "just learn CSS" every week, but oh well 🤣
Damn that Argyle intro was FIRE
Magic Move is Keynote :P
Thank you for this, I needed it. Adams take are like oxygen to me 🤗
This was so funny! 😂 Thank you, I enjoyed it very much!
Appreciate the container query confession. I'm not alone!
That intro, wow!
Great episode. Loved hearing pro CSS Modules discussion and 55:30 Totally 100% agree with Jason here. Back in the day, CanJS was easily my favorite framework. Cool ideas, great code structure, fun to use... then they released like 3 major versions in a short span of time and, totally predictably, fractured and killed almost all the small brand loyalty it had. Such a bummer because CanJS is awesome.
Adam's argument at 38:29 was so well said, completely accurate, and absolutely hilariously perfectly delivered 👏😂
I'm bad at css I need help 😅😅
This is so great! We need more humble content like this! Thank you so much for making this!
Great start!