🦋 Ben (@bhws) profile picture

🦋 https://teapawt.net/t.co/dI4ktaZTuJ

🦋
Joined July 2008
Photo by 🦋 Ben (@bhws)Photo by 🦋 Ben (@bhws)Photo by 🦋 Ben (@bhws)Photo by 🦋 Ben (@bhws)Photo by 🦋 Ben (@bhws)Photo by 🦋 Ben (@bhws)Photo by 🦋 Ben (@bhws)Photo by 🦋 Ben (@bhws)Photo by 🦋 Ben (@bhws)Photo by 🦋 Ben (@bhws)
I've been slopping together a poor man's orbs with pi durable @pidotdev and @Cloudflare durable object. So far the experience is amazing...
2
75
Try to get outside and switch offline for a bit, but everything reminds me of @vuejs
1
64
Hell froze over: announcing FormKit for React. Secretly framework-agnostic since inception, today we’re open sourcing the most popular Vue form library…for React. Why is this a big deal? 1. Forms are still hard. We (the creators of FormKit) thought form libraries were no longer necessary, given the trajectory of coding agents. It turns out we were wrong, and we learned this the hard way. Need repeating conditional fields nested 3 layers deep inside a dynamic component, with accessibility, validation, internationalization, and backend error placement? Turns out coding agents aren’t great at that. It’s table stakes for FormKit. 2. Single component. This matters more than you would think, but FormKit doesn’t ship lots of different components each with its own props. Instead, it has a single one: <FormKit type="any-input-type-here"> and unified props. This was done to provide a better DX to human engineers. It makes it easy to spot when a given component was part of the form’s data structure vs a presentational component. It turns out this matters even more to coding agents than humans. No matter where your coding agent is, whenever it sees “FormKit” it immediately knows “oh, that’s part of the form’s data”. 3. No plumbing. FormKit doesn’t require any manual data collection, event listening, or state tracking. It does all this for you on a heavily tested, framework agnostic, self-assembling graph. The only code your agent needs to write is declarative templates and submission handlers that respond to the state. 4. Dense colocation. FormKit’s syntax happens to be ideal for coding agents; nearly everything you need to know about a given input is *on* the input: <FormKit type="text" name="email" label="Email address" help="How should we get ahold of you?" validation="required|email" /> Colocation dramatically improves the efficacy of coding agents. 5. DOM. FormKit, unlike most form frameworks in React, renders the actual DOM. This also increases colocation and best practices, meaning your coding agent is far more likely to produce consistent and high-quality output that looks and acts the way its supposed to. 6. Schema. FormKit’s own inputs are not written using Vue or React — instead, FormKit has its own render schema — think of it like an AST for the DOM — and you can modify it on the fly. It’s not very human-friendly to write, but it turns out most models are already pretty well trained on FormKit’s schema. Want your inputs to look a bit different on one form than another? No problem, your coding agent can easily make those changes *without* modifying the JSX structure at all. Oh, and any inputs you create for Vue work with React and vice versa. 7. Plugins. FormKit leans into the unstructured tree graph hard. The graph doesn’t just collect data, it also passes down configuration and plugins. Want one form to work a bit differently than another one? No problem — just add a plugin to the top of that form or group and its children will all receive that feature. You can even mass assign props and configuration this way. Of course, FormKit has been solving these exact issues for a long time, but it wasn’t until we started using it on our own projects with coding agents that we realized what a huge advantage it is. With so many people using coding agents with React, it made sense to unveil FormKit for what it has always been — a completely framework-agnostic form framework that happens to unlock your coding agents. ➡️ formkit.com
7
6
5
112
11,729
📣 Announcing: KickStart! A next-generation form builder from the @FormKit team. Going live...now 👀 Generate a form, edit it with manual controls or AI prompts, then copy and paste @vuejs components or schema into your project. 🔗👇
9
29
9
225
41,021
🤔In addition to inline composables (see @TheAlexLichter video) folding `region` comments can further tame large script setup files. Say, regions: > imports > top level concerns > inline composables Devs can hide the imports and inline composables. play.vuejs.org/#eNrNGGtv00jw…
Replying to @TheAlexLichter
@TheAlexLichter introduces the idea of inline composables as a way to organize your Vue 3 code while preserving Single File Components. youtu.be/iKaDFAxzJyw?si=xA0l…
2
1
691
The playground link will show lots of errors, but the demo works to show how to fold/hide the regions, such as imports
83
🦋 Ben retweeted
PSA: If you see two verified "Vue - Official" extensions in VSCode, pick the one with the more recent version. This is a bug in VSCode marketplace that we have no control over until it is fixed. More context github.com/vuejs/language-to…
Replying to @evanyou
This seems to lead many users to install the 2.0.10 version because it shows more downloads - but the latest is already 2.0.14.
5
24
1
186
60,196
It feels like CSS has come such a long way. Nearly all of the major pain points that developers have faced for decades are either resolved or well on their way. This is a good thing! Of course the web is never done, but it does feel like we've hit an infection point.
20
23
6
346
31,190
Has this since changed as the implicit aria role of a select (non multiple) element is `combobox`. HeadlessUI's listbox are a select-only combobox: w3.org/WAI/ARIA/apg/patterns…
We try to stick with the design pattens outlined in the "WAI-ARIA Authoring Practices", which you can find here: w3.org/TR/wai-aria-practices… Note how a Listbox and Combobox are two different components.
155
🦋 Ben retweeted
Big release for @firefox and an exciting day for web developers! 🎉🎉🎉 :has() is here!!! 🎉🪩🥳
:has, text-indent: hanging, text-wrap: balance, iframe lazy loading, … @Firefox 121 is released today with lots of presents for web developers 🥳 mozilla.org/en-US/firefox/12…
1
41
5
306
22,137
🦋 Ben retweeted
Welcome 💿 to the ⚡️party!
Today we are excited to share our new Vite plugin available in Remix v2.2.0! Vite’s lightning fast DX ⚡️ means 10x faster HMR 5x faster HDR We are also happy to announce that Remix is officially sponsoring Vite! Read more about our announcement here remix.run/blog/remix-heart-v…
5
13
531
82,084
Is this a new twitter feature to make the ads more prominent?
159
Said it before, @vite_js has been an amazing bridge to bring so many shifting communities together again. 🚀 @remix_run now on board 👏 kudos @evanyou for creating such a brilliant thing 🥕 @nextjs ? you know you want it teapawt.net/pcattori/status/171287…
Now that @astrodotbuild is on @vite_js it's looking like `script setup` in @vuejs SFC's is working! 😍 Loving the reach @vite_js is having. It's becoming a bridge for the different communites to be able to work together.
196
🦋 Ben retweeted
Nuxt Studio is out of beta and open to everyone ✨ nuxt.studio
16
141
27
706
121,001
In the latest Safari technology preview you can now add a name attribute to the <details> element and make it work as an accordion. A first look into the work around accordions by @openuicg #openui #Safari #HTML
5
31
4
107
29,139
Like @vuejs? Happy to share @lydiahallie and I are teaming up with @djirdehh (author of Fullstack Vue) to bring a free Vue design patterns guide to Patterns.dev 🥳 Excited to share more updates soon. Stay tuned!
21
235
20
1,260
196,802
🦋 Ben retweeted
If you're wondering what's the deal with Signals and how they are related to Vue refs, I wrote something up in the Vue docs: vuejs.org/guide/extras/react…
19
66
14
583
126,943
Hmmm how's the Twitter QA process holding up these days?
1
148