Yes simplicity and fast feedback loops. The Remix 3 folks explain it well (attached). This is for small and medium websites (mostly internal tools or small apps) so we don't need fancy bundlers (though I am hopeful this approach will scale eventually!)
Most AI builders give you a prototype.
Netlify gives you something you can ship.
Watch: prompt, agent, live URL -- functions, auth, AI Gateway, storage all included from the first prompt.
youtu.be/uALtHWEGigA
ntl.fyi/40XC1X0 Feedback appreciated! Or: would be fun to see you make some Mastro demos on Val Town! You could create an @Mastro account on Val Town and publish some "starters" or "demos" there for folks to remix
I'm hopeful that Mastro or Remix 3 could be what I want, but I do love react, so I made something that's fullstack react-router that I am pretty proud of, but it's very experimental
www.val.town/x/stevekrous... 
I desperately want a full-stack framework that works without a bundler for val town. The two patterns I recommend now: - hono + ssr jsx (100% ssr) - react spa + hono for api routes (100% client) I want something that's the best of both worlds...
AI building goes fast, until it doesn't.
The stall at 70% isn't the idea failing. It's the platform running out of runway.
Auth, functions, storage, forms, AI access: on Netlify these are there from the first prompt, not a setup step you hit after.
ntl.fyi/40XC1X0 This is very cool
netlify.new is on Product Hunt today!
Upvote, leave a review, or see what builders are saying about prompt-first development on Netlify.
www.producthunt.com/products/net... 
from a vc point of view, sure but every company is a unique butterfly
We're vite.dev/live! Come watch and chat.vite.dev with us 💜
And join the live panel after the movie at Vite Land's #stage 'getting acquired by openai or anthropic' is becoming the monogoal of devtools companies maybe
Firecrawl is joining Leap Week.
On March 25, we're showing how to pull structured data from anywhere on the web and push it directly into your backend.
Firecrawl handles the extraction. Directus handles the rest. 
1 HOUR from now!! :)
we've updated the Stripe Sync Engine on @supabase.com
continuously sync your Stripe data to Postgres. updates:
◆ added support for Coupons
◆ you can use it on Branches
◆ admin controls: restricted to Admins/Owners
◆ ux refresh: A smoother, faster interface 
Junie CLI from @jetbrains.com recently shipped with ACP support — install it right from Zed.
Command palette > `zed: acp registry` > Junie > Install
$50 free Gemini 3 Flash usage included.
junie.jetbrains.com 
Netlify co-founder @biilmann.blog on what's different today:
You can now start a project from inside Netlify. Prompt, pick your agent, get a production-ready app without leaving the platform.
Still deploy from anywhere. Now also build from here. 
if you're doing code review, try /review and /pr-comments. pay attention to how much mental energy you save by not switching contexts. that's the real value.
here's a quick video demo
$ npm i -g command-code command code gets this. it's built around the terminal because that's where developers actually work. not as a gimmick GUI, but as a fundamental design principle. tools should minimize context switching. every context switch is a tax on your productivity and your ability to think deeply. the best tools keep you in flow. we built Command Code to provide you with the best agentic developer experience. this is the kind of feature that seems small until you use it. then you realize how much friction it removes from your daily workflow. - learning (see patterns in how your code is reviewed)
- taste aware (Command continuously learns your coding/reviewing taste, and compounds in value after every session) by keeping you in the terminal, command code preserves your cognitive state. you stay in the problem. you stay in flow.
this is especially valuable for:
- async review workflows
(get feedback immediately without waiting for humans)
- rapid iteration (fix feedback in the same session) 4. commit and push without ever leaving the terminal
why does this matter?
context switching is a form of cognitive load. code reviews are the biggest bottle neck today. every switch degrades your working memory. you lose the mental model you've built. you lose momentum. you lose flow. this is subtle but powerful. you're not just seeing the comments, you're immediately positioned to act on them. the friction is gone.
the workflow becomes:
1. /review → get structured feedback/score
2. /pr-comments → see all comments
3. continue in the same session to fix issues