I think thatβs a DAW
I think thatβs a DAW
The hsl(from β¦) syntax thankfully makes this obsolete. CSS written like that was a real pain to maintain!
I had this "problem" just last week.
TS only allow property access for known properties, even when it's optional. In other words, even though `null?.a` is valid, TS is saying `null` doesn't have a known property `a`.
Iβm okay with this. Classes for styling, IDs for behavior and tags for semantics.
Mixing these concepts used to lead to bad code, like using the a semantically wrong element for its styles.
I think decoupling is the right move.
why are there stars in front of the moon?
`take` and `sample` are basically the same method, but the rest look good.
I'd love for it to take any sequence, and not only arrays. For example, Object.entries() and Node.children are iterators. Sampling those look useful, but I have no idea how that could be implemented.
One of my favorite Brave features is that it swallows most cookie consent screens (which I doubt sites are honoring anyway)
Helping modernize a 15yo system that was running on python 2 until a month ago. Itβs been a huge pain but gratifying at the same time.
No links, only divs
Pottetris effect.
hahaha that's crazy! I could swear I remember listening to you saying those things! thanks! :)
@dylanbeatt.ie maybe I'm suffering from the Mandela effect, but haven't you posted a video somewhere about AI being good at programs but not products? I'm trying to help a fellow dev in an existential crisis, but I can't find itβ¦
My dream is having browsers implement the line-height-step property. I have no idea how that would interact with the lh unit, though.
Fuck. Keep your head up, youβre an amazing professional and an inspiration.
Iβm sorry. itβs stronger than me π
@bram.us I finished writing something about how color scheme switching should be a browser control just to discover you wrote the exact same thing in 2022. :P
Any news about that since then?
That's awesome! I had no idea that existed. I went looking for ideas like this but googling it I could only find tutorial after tutorial (since they so necessary with the current solutions).
Thanks for the pointer. :)
ERRATA: It should be "Let's make dark mode *switching* a browser-native feature." At least this proves I'm not AI. π
@nerdy.dev @syntax.fm @kevinpowell.co I'm sorry for the spam, but I just wrote a piece on why we should stop writing dark mode switches and I'd like to know your opinion (and maybe some help getting this to people who could act on it).
bsky.app/profile/did:...
Dark mode toggles should be a per-site browser preference, just like zoom.
Why are we still reinventing the wheel with JavaScript? Let's make dark mode a browser-native feature.
bit.ly/dark-mode-is...
semantic ID is a new one for me
I think April Foolβs lost a lot of its appeal in the post truth eraβ¦
My pet peeves are nucular (nuclear) and anenemy (anemone). English pronunciation is so far from how itβs written that anything goes!
that's one of the most thing ever generated by AI
Just tangentially related, a margin-vertical/horizontal would be great too. Not necessary, just neat. :)
This inspired me to be sassier with my bots.
That's pretty cool! What were the biggest challenges you had so far while building this lib? Any challenges you still have?
You havenβt written enough bad TS.
As much as I dislike Tailwind, I admit it has its uses, and generated code is one of them. In my experience, AIs are not that great with CSS, but Tailwind helps a little.