71–74 of 74 posts
This is insanely verbose just for a button with a tooltip: import { Button } from "@/components/ui/button" import { Tooltip, TooltipContent, TooltipProvider, TooltipTrigger, } from "@/components/ui/tooltip" export default function TooltipDemo() { return ( }> Hover Add to library ) } Contrast with plain old HTML form button where the title attribute gives the tooltip text: Hover
Earlier quoted context omitted.
Neo doesn't mean it can just be a completely different thing, it means its a modern take on the same thing from before but slightly evolved. Neo-Classicism still looks like Classicism. Neo Nazis are still Nazis. If I create something called Neo-Cuisine, you'd expect the result to be edible. If I see something calling itself "Neo-Brutalist Architecture", I'd expect it to look like Brutalism, or have some hallmark of t…
It's a visual style, yet all your criticisms are about under-the-hood technicalities. The style I use for my personal projects ( https://frost-e.com/design-system/ ) is a single css file, but looks similar. Nothing is stopping you from applying this visual style to plain HTML components.
This is insanely verbose just for a button with a tooltip: import { Button } from "@/components/ui/button" import { Tooltip, TooltipContent, TooltipProvider, TooltipTrigger, } from "@/components/ui/tooltip" export default function TooltipDemo() { return ( }> Hover Add to library ) } Contrast with plain old HTML form button where the title attribute gives the tooltip text: Hover
Haven’t you heard that you’re not supposed to type code anymore?
Mainly, looking at it is the problem. Decades old copy-paste editing techniques get around the typing.
Earlier quoted context omitted.
Not sure; it may be doable remotely with some CSS, in which case it would be a few lines of code for any number of buttons.
Joking aside, I don’t believe you can and I’m fine with that. It’s still so much simpler and predictable.