meta_pixel
Tapesearch Logo
Log in
Syntax - Tasty Web Development Treats

988: Cloudflare’s Next.js Slop Fork

Syntax - Tasty Web Development Treats

Wes Bos

Tech News, Technology, News

4.91.2K Ratings

🗓️ 18 March 2026

⏱️ 47 minutes

🧾️ Download transcript

Summary

Wes and Scott talk with Steve Faulkner about vinext, a Vite-powered Next.js fork. They dive into AI coding workflows, agent browsers, code quality, and what modern dev tooling looks like in an AI-first world. Show Notes 00:00 Welcome to Syntax! 02:01 Knowing how to use AI 02:31 The idea behind “slop fork” vinext How we rebuilt Next.js with AI in one week 06:27 How to approach a project like this Super Whisper 07:53 Using markdown as a planning and thinking tool 12:35 Steve’s OpenCode setup 14:31 What agent browsers are and how they work agent-browser 15:34 Where agent browsers fall short 19:02 Why agents work best with tight feedback loops 21:23 Dealing with poor code quality from AI 23:54 Brought to you by Sentry.io 24:19 Searching for a reliable AI workflow 25:54 What about security? 28:46 When it makes sense to port a framework vs switch 32:03 What an AI-first programming language might look like 33:16 TypeScript in an AI-driven workflow 35:36 Cloudflare and improving developer experience 38:10 Being excited and uneasy about where AI is heading 39:06 Which industries AI disrupts next 41:29 Sick picks + shameless plugs Sick Picks Steve: IWC Pilot’s Watch Mark XX Shameless Plugs Steve: vinext Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

Transcript

Click on a timestamp to play from that location

0:00.0

Welcome to Syntax. Today we have Steve Faulkner on, and he is the creator of V-Nex. If you didn't hear about it,

0:07.6

basically Cloudflare took NextJS, and they created what is lovingly called a slop fork,

0:14.2

which is they ported the entire NextJS framework to Vite. And then they posted it and it was this big thing. And

0:23.0

we're not here too much to talk about like the drama of all of this and whatnot and

0:28.4

whether NextJS is hard to run on Cloudflare and whatnot. But I think we're more interested

0:33.5

here of like, how did you do this? You know? Like, like, how was this created? What's your

0:39.1

process for tackling something that is not like, oh, cool, you made like a little app or you

0:44.4

can like drag and drop stuff around or you made a photo booth app, but like you literally took like

0:48.8

an existing, I'm not going to say spec, but like like test suite and replicated most of the software behind it. So super interesting one. I'm super happy to have them on. Welcome, Steve. Thanks so much for coming on. Yeah, happy to be here. Like I said, I'm excited to tell the world more about this. I think it's a cool story. It's a cool story about AI and just the world we're living in right now and how rapidly it's changing. I think this is going to be a wild year, maybe wild five or ten years for software. Yeah. Yeah, buckle up. So give us a quick rundown of who you are and what you do. My name is Steve Faulkner. I am the director of engineering here for workers. So pretty much own kind of the whole workers org at Cloudflare. It includes other things like our agents product, containers, some of the stuff around Wrangler, CLI. So I didn't list all the teams. Apologies to who I missed, but it's roughly like 80 people. I've been here for a couple years. And yeah, that's my role. I'm not writing code every day. That's not what I do.

1:44.8

I've seen a lot of people have said a lot of stuff about what I did and about the blog.

1:48.1

And I think the only real correction that I want to make is a lot of people have been calling me a 100x engineer or something like that.

1:54.3

I would use a title 100X engineering manager is how I would.

1:58.5

I think that would be the correct.

2:02.7

Yeah, given the state of AI, isn't that like kind of where we're landing though? Those are the people with the the superpowers

2:08.9

are the 100X engineer manager. And we'll jump right into that. Like I think AI is an application

2:15.0

factor, right? If you know what you need to do, I think you can use AI to do it faster and better. But it works in both directions, right?

2:21.2

I mean, I've seen it negatively amplify things when you don't know what you need to do or

2:25.2

you have the wrong kind of direction, right? It just helps you go, but the human still needs to set the

2:30.6

direction. I was curious about the term slop fork that has been thrown around, given the nature

2:36.9

of AI writing it.

2:38.8

How does that term, like, hit you?

2:40.9

How do you feel about the term slop fork being used here?

...

Please login to see the full transcript.

Disclaimer: The podcast and artwork embedded on this page are from Wes Bos, and are the property of its owner and not affiliated with or endorsed by Tapesearch.

Generated transcripts are the property of Wes Bos and are distributed freely under the Fair Use doctrine. Transcripts generated by Tapesearch are not guaranteed to be accurate.

Copyright © Tapesearch 2026.