If you also want to change your token architecture/semantics, why not decouple that from the visual change?
If you also want to change your token architecture/semantics, why not decouple that from the visual change?
Today while riding #MTB in the woods we crossed paths with my niece three times, but she was on a horse instead. Not that different perhaps...
www.goodreads.com/book/show/17...
Today while riding #MTB in the woods we crossed paths with my niece three times, but she was on a horse instead. Not that different perhaps...
www.goodreads.com/book/show/17...
This API is really convenient, importing everything, nice to not have to care about tree shaking and bundle size as much.
Me 10 minutes later:
Still waiting for the build to finish since the icon library 10xed the build time.
Some things are the same.
This API is really convenient, importing everything, nice to not have to care about tree shaking and bundle size as much.
Me 10 minutes later:
Still waiting for the build to finish since the icon library 10xed the build time.
Some things are the same.
It's such a bummer when you read a 2019 article about the "current state" of something, and it's still the case in 2025 :(
It's such a bummer when you read a 2019 article about the "current state" of something, and it's still the case in 2025 :(
There’s very little material about this online though. Anyone here used it?
How would you even go about creating a design token for something like a “time-colon” glyph variant? Should you? 🤔
There’s very little material about this online though. Anyone here used it?
How would you even go about creating a design token for something like a “time-colon” glyph variant? Should you? 🤔
I can say “what have you done to my app?!”, Claude will take a screenshot and apologize
Nope. SwiftUI.
Haven't touched XCode in 6 years when I did a tiny bit of Objective C, but Swift is not bad, actually. It's so quick to pick up new languages in the LLM era.
I guess this is now a #swiftui account.
I'm not a luddite, I think we probably still need ~50% of the abstractions created the last decade. But which half? You need to feel some of the pain to know.
I can say “what have you done to my app?!”, Claude will take a screenshot and apologize
Nope. SwiftUI.
Haven't touched XCode in 6 years when I did a tiny bit of Objective C, but Swift is not bad, actually. It's so quick to pick up new languages in the LLM era.
I guess this is now a #swiftui account.
I'm not a luddite, I think we probably still need ~50% of the abstractions created the last decade. But which half? You need to feel some of the pain to know.
Nope. SwiftUI.
Haven't touched XCode in 6 years when I did a tiny bit of Objective C, but Swift is not bad, actually. It's so quick to pick up new languages in the LLM era.
I guess this is now a #swiftui account.
☝️ These things will make your tests shine.
☝️ These things will make your tests shine.
I just want an app on my phone that I can tell “summarize that Notion link that Bla bla what’s their name posted on Slack yesterday”
I just want an app on my phone that I can tell “summarize that Notion link that Bla bla what’s their name posted on Slack yesterday”
import { Input } from 'ds/forms/top-label';
import { Input } from 'ds/forms/floating-label';
instead of 🤢
<Input variant="top-label" />
<Input variant="floating-label" />
import { Input } from 'ds/forms/top-label';
import { Input } from 'ds/forms/floating-label';
instead of 🤢
<Input variant="top-label" />
<Input variant="floating-label" />
Still also just share the types from the workers to types in JSDoc on the client.
Still also just share the types from the workers to types in JSDoc on the client.
Also this pattern is really not used enough:
Also this pattern is really not used enough:
issues.chromium.org/issues/42192...
Claude Code is so good at understanding stuff like my little homegrown router, made a perfect rewrite.
I'm not a luddite, I think we probably still need ~50% of the abstractions created the last decade. But which half? You need to feel some of the pain to know.
Claude Code is so good at understanding stuff like my little homegrown router, made a perfect rewrite.
I did not expect that 2025 would be the first year with a 5 days a week work-from-office policy.
I did not expect that 2025 would be the first year with a 5 days a week work-from-office policy.
- start with no or light bundling
- dynamically bundle in prod based on usage
If modules A–F are often requested together in a short window, bundle them.
G–H might stay separate. I–Z in a different bundle. Could even be different for different user segments.
- start with no or light bundling
- dynamically bundle in prod based on usage
If modules A–F are often requested together in a short window, bundle them.
G–H might stay separate. I–Z in a different bundle. Could even be different for different user segments.
I'm not a luddite, I think we probably still need ~50% of the abstractions created the last decade. But which half? You need to feel some of the pain to know.
I'm not a luddite, I think we probably still need ~50% of the abstractions created the last decade. But which half? You need to feel some of the pain to know.
`rel=noopener` has been the default for `target=_blank` links for years.
`rel=noreferrer` is an optional privacy feature, not a reasonable default
`rel=noopener` has been the default for `target=_blank` links for years.
`rel=noreferrer` is an optional privacy feature, not a reasonable default
blog.jim-nielsen.com/2025/be-mind...
blog.jim-nielsen.com/2025/be-mind...
Maybe `calc-size()` could be extended to support this? It already has a custom `content` param so there's "room" in the API
Maybe `calc-size()` could be extended to support this? It already has a custom `content` param so there's "room" in the API