Saw an interesting hover effect on the web, thought I would try building it with @tailwindcss 4.0. Then I played around and ended up with this
No customization, no tw plugins, just out of the box Tailwindcss classes.
@adamwathan I'm surprised underscores is so low.
My thought with voting that way is that is consistent with the calc syntax. "calc(100%_-_10rem)"
If that did not already exist I think the pipes would be my second choice. And that is mostly because commas and plus mean something in css
@calebporzio "variant" wins.
"type" on button or input then requires something for htmlType or something like that. So "variant" allows devs to already intuitively know the api of <Button> because it can basically stay the same as a html <button>
An item is not "done" because it meets the initial spec.
Practically none of this is "done" ever.
An item is done when the users stop requesting features
In software development, you really have to resist the urge to do all the cool things immediately. Focus on shipping; add the cool things when you KNOW it's something your users want. A cool animation, while nice, can likely be unnoticed by users.
Ship Value, not shiny.
This requires an entire org to understand this. You should set lofty specs, but also want things shipped.
1 Specs are rarely right
2 we learn as we build
3 we adjust as we learn
4 we ship when we can
5 we re-evaluate the spec
6 we listen to user feedback
7 we craft a new spec