This is another reason bsky sucks

Congrats!

I'm disappointed by influencers on both platforms. I don't care where devs have conversations, but as a small fish it seems to be working there better than here, at least for me.

I always post my open source efforts here. It gets effectively no views, no attention, no distribution. I do the same on X and people actually get excited and start using it.

Bums me out honestly. bsky seems to work great if you already have gobs of followers.

Small Image Processor Logo

Announcing: sip — a small image processor for the orange cloud 🟠

An open source ultra low memory WASM image processing for Cloudflare Workers.

It resizes via DTC stream rather than a buffer, meaning even large jpgs can be processed directly on your Durable Object w/o OOM.

sip.standardagents.ai

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

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.

...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.

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?...

...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.

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...

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.

<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.

...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:

...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...

...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....

...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...

...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...

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...

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?...

Congrats!!!

That’s right, nothing to see here

Absolutely

Hmm, I dont think we're talking about the same issue at all. I think if you read the docs, especially the sandbox section it would become quite clear the problem this is solving.

All our own, most similar to Vue though

It matters a lot actually. Running agent-produced code live in the browser the way we are wouldn’t be possible, or at least would be much more complex, with build steps.

Thanks! It’s much improved since alpha 9.

Also the sandbox is very cool and unique

We’re open sourcing ArrowJS 1.0: the first UI framework for coding agents.

Imagine React/Vue, but with no compiler, build process, or JSX transformer. It’s just TS/JS so LLMs are already *great* at it.

AND run generated code securely w/ sandbox pkg.

➡️ arrow-js.com