Wanting the government to help people is free. You don't have to preemptively circumscribe your demands to appease the reasonableness referee in your mind or to placate a hypothetical political opponent. You are just some guy you can ask for whatever. www.welcometohellworld.com/wanting-the-...
Yeah, nothing against you, Matt.
Personally, it's not an uninteresting idea and I think it could help the broader community; I think that would be a great outcome.
There's just an uneasiness and sensitivity around the parties involved. On top of the already strong feelings about AI!
Sure, but that's the one that was specifically mentioned in the article.
It's not the one I'd have chosen to highlight, myself.
Having left Vercel for Cloudflare, this has my spidey sense tingling
Yeah. The mention/partnership of NDS leaves a pretty sour taste, especially considering the broader associations of Vercel and Nextjs leadership.
NDS notoriously firing the most innovative govt staff and benefitting from a $1000 human replacement is an uncomfortable juxtaposition.
Hm, but why Vite Next.js when TanStack Start and Astro?
github.com/open-governm...
Hey, thanks for asking!
I've been focused on another project for a little while, so I havent had a chance to put a ton of time into it. Still in the back of my mind though!
Might have a project coming up I can use to look into a little more. And is leveraging the design token standard
Hello, world.
Sugarcube is now available for use.
sugarcube.sh
Check it out on GitHub
github.com/sugarcube-sh...
Or on @npmx.dev
npmx.dev/org/sugarcub...
Thanks for following along :)
Looks great! Really looking forward to trying it out!
Unbarrelify got me thinking... I know of a library that uses multiple chained imports, not unlike barrel files.
Turns out, my importing directly from the source, I was able to cut USWDS SCSS compile time in half!
All that, and more:
github.com/uswds/uswds/...
🙏 looking forward to it!
Potential to be open source or source available at some point?
I always wanted to take a poke around at Nord Health components, but it's closed source 😭
Nonetheless, it's cool to see a peek under the hood!
This is really cool. How is extraneous information on the page handled? Things like menus, heading, footers, etc..
Hey, there's me!
Codex, I guess. Same thing.
@aaronfrancis.com in the chatgpt spot?? 👀
this is how design works
@uswds/uswds package on npmx.dev. 1 like
First to like @uswds on @npmx.dev
Oh, you mean, if210you?
Lol, I'm not trying to argue with anyone 😂
I don't have much experience with Web Components so I'm just trying to learn what preferences folks have
<DatePicker.Root> <DatePicker.Label /> <DatePicker.Control> <DatePicker.Input /> <DatePicker.Trigger /> <DatePicker.ClearTrigger /> </DatePicker.Control> <DatePicker.Positioner> <DatePicker.Content> <DatePicker.View> <DatePicker.ViewControl> <DatePicker.PrevTrigger /> <DatePicker.ViewTrigger> <DatePicker.RangeText /> </DatePicker.ViewTrigger> <DatePicker.NextTrigger /> </DatePicker.ViewControl> <DatePicker.Table> <DatePicker.TableHead> <DatePicker.TableRow> <DatePicker.TableHeader /> </DatePicker.TableRow> </DatePicker.TableHead> <DatePicker.TableBody> <DatePicker.TableRow> <DatePicker.TableCell> <DatePicker.TableCellTrigger /> </DatePicker.TableCell> </DatePicker.TableRow> </DatePicker.TableBody> </DatePicker.Table> </DatePicker.View> </DatePicker.Content> </DatePicker.Positioner> </DatePicker.Root>
You might hide complexity of a date picker (attached) behind <DatePickerInput />. If you're already using a framework this is easy, you just create a new component.
Exposing this as a WC feels like it defeats the purpose of what many expect from WC's.
As a WC user, which would you prefer?
this is why i find tests to be unethical and simply don't write them
That's true. Though, my thinking was that it's easier to hide the composition if you're already using a framework than if you're using web components.
In other words if you're already using React, making <MyComponent /> is easier than creating <my-component /> if you're not using a framework
I ask because I'm curious if there's an appetite, in general for both, but if folks who prefer web components tend to also prefer the abstracted version
And wondering if there's a way to make both camps happy with web components 🤔
Curious you're take on component composition vs abstraction.
From Radix UI, shadcn
<Component.Root>
<Component.Thing>
...
</Component.Thing>
</Component.Root>
to fully abstracted and encapsulated
<my-component />
What/where do you feel is most comfortable?
This was an initial PoC stackblitz.com/edit/unocss-...
And some vibecoding trying to generate classes leveraging a cva.style style syntax
stackblitz.com/edit/unocss-...
I'm super into this. I've been thinking about something similar for a while, tho it goes beyond tokens specifically.
Kind of picturing something like: .component-attribute-modifier or .btn-size-sm
Very inspired by tools like CVA. Trying to find the right balance between utility and too abstract
