967: What’s Going to Happen in Web Dev During 2026

Welcome to Syntax. We have our 2026 predictions for you today. What's going to happen 2026? Last year, we had an incredible hit rate. I mean, we were well into the 80, 800 percent, I would say. 87.5 percent accuracy, yeah. We guessed things that we didn't even know that were going to happen. And today, Wes and I are standing up. In fact, Wes was like, I'm standing up. And you know what I said? Me too. I'm standing up too. Let's do it. New year, new me. I'm a stander now. I can't wait to try stand for a week and a half and then sit down for the rest of the year. Yeah, maybe I should do an episode on the treadmill. Get walking. Let's get into it though. Let's get our predictions cooking here. What do we predict for the year 2026 in the world of web development? So number one here is web GPU and 3D experiences pop. Man, let me tell you, that Lando Norris website made some waves. Yeah. And that made some waves that won't be felt until 2026. But I think we're going to really feel them with new experiences. Now, we saw a lot of really cool GPU enhanced websites or websites that had a lot more shaders and graphical elements and things like that. I think it's only going to get crazier for 2026 for sure. I think so too. Man, the cool landing page. And this kind of – I'm going to loop this in with another one of my predictions. It's design making a comeback because everybody's cranking out the same decent-looking website with AI. Raycast-ass homepage. Yeah. In order for – and that's not a slant at Raycast at all. No. I think Genericast invented that whole UI. And it kind of sucks that your entire aesthetic has become like a meme because it's so good and everybody copies it. But websites where you land on it and you feel like, wow, somebody has actually put some work into this. It makes you stop and look at it and experience and feel good about the product. because there's so many generic ass websites where I can't even tell if I'm on like what website I'm on. Sometimes I'm on threads and Twitter and I don't even know what website I'm on because they all look exactly the same. And part of that is good because it's like you just know what to expect and you just want to use the application. But also like there's some joy that's been lost in the website. And I think 3D, all these web GPU experiences are going to improve that. People are able to make new things. So Simon Le Marchand is working on shaders.com. And it's just like really sick. It's a web app and like an NPM package that you can just like use shaders together and you can mask things and blend them. And there's a whole bunch of like defaults that you can pick out. And I think it's the year. It's the year for 3Ds. It's the year that people are going to learn what shaders are and make cool ass looking websites let's we're gonna see dithering all over the place people are gonna find out about dithering and they're gonna dither and noise yes and i'm not just gonna stop job yeah i'm gonna stop drop uh shut him down roll him up shop open up the shop stop shop drop shut him down open up shop sorry yes i agree with you on that uh shaders man shaders are a crazy thing but i also think ai will improve the burden on learning shaders i think that's why is that like in order to like write shaders right now or without ai like you have to be a mathematician you know you have to be an artist and a mathematician and basically people want to be able to like not be a mathematician and still make cool looking stuff and i think the tools for that are coming this year yeah Yeah, light mode makes a comeback. I got to say, I've been using light mode. Yeah, I told you. There's evidence here. I joined the Syntax team meeting the other day, and I had light mode on. I had to turn it off because it was making my glasses look crazy. But yeah, that's the hard part about glasses, where it was on camera. It gives you this look here. But, you know, for me personally, I have been liking light mode during the day and dark mode in the evening. And I have the automatic thing set up. And I have found light mode themes that I really like in my text editor for the first time in my entire life. I think the last time I used it. Your entire life? Not even like Dreamweaver notepad days? I was going to say, the last time I used a light mode theme for more than enough time to change it to a dark mode theme was Dreamweaver. Because the moment I went into TextMate, I did a dark theme. And then in Sublime Text, dark theme. And then dark theme ever since. I'm just so sick of crappy dark mode. It's like brown or washed out gray. Notion is the poster child for that. Doesn't work well. I love dark mode. I still dark mode when I'm coding. But most of my other apps default to light. And I like it. I use a system setting for everything. And I was actually asking this on Twitter the other day. It was like, do people really want the little sun toggle in some personal person's website? Or do you just want it to be the system setting? Because I opt in on a per site basis. Like I use Twitter in dark mode. Yeah, it looks way better. And it's just about how it feels for that website. And like I said, there's so many crappy dark modes that have been half-assed. So I want that little sun toggle. don't you think give me that all day google docs will ever get to dark mode like come on question like what are they doing no who's writing google docs in dark mode i no chance every time i go to the google docs i'm like come on no no don't no never never doing that well maybe we'll see i don't think it will ever come that's such a huge under yeah to do all the icons you know but then they they also have to you also have to count for people have made documents and slideshows assuming the background is white i'm not talking about slideshows i'm talking about like the canvas areas yeah like that like but like a doc somebody made a doc or somebody made a spreadsheet and the colors that they've chosen on that spreadsheet are based on it being a white background so what do you what do you do can you calculate a color that is similar yeah you actually can so maybe they can figure that out yeah that's what please beep that out we don't swear on this podcast i i know that i thought it'd be funny with a beep i thought that yeah that it would be funny okay next one we have here is css modern css standards are going to kick Man, there is so much that has happened in the last, I don't know, maybe 14 and a half months. So much that is coming. Go to chrome.dev forward slash CSS wrap 2025. And you will feel like almost stressed out about how much stuff has been added to CSS. It's unbelievable, right? we've got customizable select css anchor starting style if statements popover scroll animations and related to popover there's like eight different things you know like hover intents and uh hinting and style queries and we've got css functions that are currently being added to the spec so i think that css is going to have a year this year and i'm here for it i think a year from now people are going to be like wow we can actually use this stuff i think shad cn all these ui frameworks are going to have major iterations or we're going to see some new version of these ui frameworks that are entirely built on these modern standards you don't need to use some floating ui or a whole bunch of like external javascript libraries i'm just going to take a minute to plug my my thing graffiti is kind of built on that idea is that like i'm not this is not a slam but that utility classes should have more utility right like they shouldn't be just a dsl for css it should do more stuff so like uh you should be able to have a swiper or a um like i have an instagram style reel that's just dot real or you know their header is applies a lot of styles so it's almost like components based out of uh actual actual out of css without using any things other than these CSS modern features. And let me tell you, there's some cool stuff in this thing from the color system that's like alpha-based rather than like shades-based using relative color, easy to configure, but also a whole text-based system that does like fluid text based on its container query or automatic contrast color with really, really cool relative color syntax. So I whether or not it's graffiti, which I don't think it will be, but I think things like graffiti will like you mentioned will become more ubiquitous or systems that are already ubiquitous will lean less on JavaScript, which man people in the comments of this YouTube channel when I or even my personal channel. I did like a thing on invokers about, oh, you can you don't have to use JavaScript for this now. People are like, stop trying to kill JavaScript. Like JavaScript can do it fine. And it's like, brother, this is less code. It's easier and it's more performant. Like, what do you want? You want to do it yourself? You want to have it be worse just for the sake of using JavaScript? Like, that's crazy. I love JavaScript. And I agree with this. Yeah, like these things are primitives. The only reason we added JavaScript in the first place was because we couldn't use those things. Now we can. So, yeah, let's do it. I think you got to make this thing look like sick because like there's like this like functionality point of view to it, you know. But then there's also the reason people pick up ShadCN or Tailwind UI or any of that is because it just looks good by default. And those defaults are becoming so ubiquitous. if there were something that looks different. Not to say that you can't make Shadzian look like anything. Literally, you can make it look like anything you want. That's the whole point of it. Just people stick with the default. But if there's something that comes out with whatever that looks like next level, looks really cool. Yeah. I think that will pop. Yeah, man, there's so much cool CSS stuff. One thing I think that is underrated in the potential modern CSS landscape is scroll animations. I think because they aren't available in Firefox yet, or just that we haven't seen enough with scroll animations, or I think there's a misconception that the thing that you can do with them is just scroll on the page, animate stuff in, or parallax or whatever. I think scroll animations have the most potential for like a major shakeup in terms of like interesting things that we can do in CSS. Like interactions, you mean, right? Yeah, all kinds of stuff. I just saw an example using them in form inputs or something. So, I mean, there's a lot of really interesting opportunities. But as this stuff gets better and better I think we going to see not just these features hit We going to see UI patterns like the swiper thing that I built all of a sudden being like oh wait we can do this Oh, no, wait, we can do this. Like this always happens in CSS. A new feature comes in and then people find out, OK, that's great. And then like three years later, they find out, oh, there's so much bigger possibilities with this now that we've really gotten comfortable with this API. And now we can really explore some interesting concepts and ideas with it. You know what is another cool thing I just saw on this Chrome CSS wrapped is scroll markers. So if you're doing a carousel, one of the things you still need JavaScript for is you got to like put all the buttons and then you got to like listen for like the scroll. What's the event in JavaScript when the scroll snap snaps? I don't even know. There's an event for scroll snap snap. And you listen for that. And then when that happens, you update your dots as to which one is currently active. There's a new thing being added to CSS called scroll markers and scroll marker target current, which will allow you to make buttons that click next and whatever. CSS is so good. speaking of css let's talk about javascript yeah speaking of css yes javascript we said temporal will ship in every browser because every year it seems like that is what is this how many years have we predicted i think we've predicted it for probably four years now and last year it hit what it hit chrome kind of it hit it's going to hit chrome in 2026 january so maybe not but it's it's not in safari yet and it isn't it is this is a tap-in west this is a tap-in because it is teed up on everything i feel like i feel like this will have to happen just a little but yeah but will there be like a gotcha you know it works but safari doesn't do seconds or something weird like that you know yeah safari thinks that there's a security reason so we're going to completely limit the API so that way it doesn't hurt our precious native app. Safari does this one weird thing that just renders the whole thing unusable. But Temporal will ship. This will be our year of Temporal, and I'm so stoked for it. Also, Standard Stack will gain popularity by framework authors. So this is something I did a talk about this probably about a year ago. I've been talking about it a lot. There is a lot of new features in JavaScript. Navigation API, URL pattern. There's a new sanitizer API, which we always have to reach for DOM purify. You're taking user input, you want to put it in the DOM, and you've got to strip out an image on load, something like that. There's a new sanitizer API that's coming out. All of these new standard primitives are going to primitive in 2026. So you're already seeing this with Hano and Eliza and a lot of these standard server frameworks. But now, like Remix as well, now that they have become standards in JavaScript, I think a lot of these frameworks are going to pick them on up. So the standard stack is going to gain popularity, and that makes sharing code between multiple frameworks. It means moving code from one framework to another. It makes all of that stuff super easy. I think in general, frameworks will continue their push to RPC territory. Where we've seen this with SvelteKit. We've seen it with everything. TanStack query. People are moving to RPC, which feels like it's about time. Man, I use this kind of API in Meteor land. And when I moved to have a separate API, I was always just like, come on. This feels so much worse than how I was doing it in 2015. So I do think this is going to just continue to grow. And there's all kinds of things, whether that is like convex or super base or these things that kind of obfuscate some of that. And you're just calling functions and it handles it all pocket base, those types of things. Yeah. Yeah. I think this is just going to continue to become more of the commonplace. Do you think that we will see a push for standardized RPC? because we have like you have like the spell version and then like cloudflare has their own called that they rolled out called captain web and and then there's obviously rack server components no i don't think we'll see a standardized version of this you don't i don't see that there are some there's like json rpc there are some specs out there for it but i think as we move a lot of this stuff to rpc probably not this year but i think at some point there will be some sort of call of like let's let's standardize these things and maybe we don't necessarily need to because of the fetch api like we have web request and web response and we have get put post we have the body you know like those things are are fairly standard already so maybe that's that's good enough i will say that But I do think that standard schema will become way more ubiquitous in regards to RPC. Even zero sync in their new mutations has moved to having a standard schema base the same way that Svelte remote functions are. So that way you can use archetypes, Zod, whatever you want, and to validate your data between. Because that is really, as we talked about in the remote functions episode, that is really such a killer way to validate your data between the client and server. So I would hope that that aspect of it might be standardized. I think so. For those who don't know, standard schema is this idea that you take your library, like Zod or ValleyBot, or there's several others, there's like 20 of them out there, and that all of the tools that both ingest data, validate data, but also return data, they all speak this thing called standard schema, and you can convert between them. And it's been so nice to be able to use whatever library I want, but just know that all of these tools work together. Whereas previously, a tool would be like, we only use Zod version 3. And that's it. The OpenAI API is like that right now. You can only use Zod version 3. But then you're starting to see a lot of these AI APIs being like, just pass us standard schema. And it will work between all of them. Even like, what did I use the other day? Chrome's local AI API uses JSON schema. If you want to be able to specify the return value as like a structured content rather than just text, you have to use JSON schema. And I was like, come on. Let me use Zod or whatever I want and then just pass you the standard schema version of that. Don't pigeonhole me into using your weird version of this. I feel like these libraries, whether that is archetype or whatever, are all just going to move to support both. And it's like you can just use whatever you want, right? But that's the whole point of standard schema. I know. You can use whatever you want. You can specify it in whatever way you want. And then when you pass it to the tool, it doesn't matter. Doesn't matter. You can convert Zod or archetype or whatever to standard schema. And then the thing will just ingest the standard version. Yeah. What do you think is going to happen in React Land this year? Oh, that's a good question. I don't think much. I think the pace at which we move with a lot of these frameworks, especially that so much more of the attention has been off of features and onto how do you do this with AI. I don't know. Like there's obviously we had the huge React security hole. that's certainly going to leave a bad taste in a lot of react users mouth but i don't know i don't think much i think it's still going to be the number one but i'm rooting for a lot of these other other players in the space as well you know whether that's felt or remix or whatever yeah i think there will be another security issue and i only think this because i was talking to cj And he kind of opened my mind up to the idea that when you're inventing such a unique transport, that the possibility for something like this is opened up. So I do think there probably might be something else based on nothing. Around server components initially. React server components invented the whole transport end-to-end, right? And a lot of people were vocal. Even Rich Harris, a creator of Svelte, was like, we will regret reinventing RPC. And here we are with a major security hole in it. Well, maybe we'll parlay that into one of my other ones. We will see a lot more security mishaps in web development in general. I think that is because of several things. AI code slop, obviously. That's a big one. Understaff tech teams. I think that's been a lot of the reason we've seen so much downtime lately. And as well as like so many of these companies are just shipping at insane speeds right now because everybody's trying. It's a race to to be the winner of all of this AI stack. And because of the insane speeds that they're shipping at, things obviously get missed and whatnot. So that's a bit of a trade off or a huge trade off right there. And I think a lot of that stuff is starting to catch up with us. You know, we've seen major downtimes in a lot of the cloud providers. And I think that is going to continue through the web development industry, unfortunately. I think we will find at least one, at least one, I think there's going to be more, at least one major story that comes out about an app that people are really using that's maybe not mainstream but taken off. that once the security issue is found, the entire Apple have found to be vibe-coded garbage, like held together with duct tape, and then we'll all laugh about it and et cetera. It'll be all over online. Like, I can't believe they did this. They called this database query from the client for some reason, you know. I think Svelte for Svelte, we didn't talk about that. I think Svelte Kit 3 will be released. I don't think that's a difficult prediction to make and will include all of their async and remote data stuff all buttoned up and fully launched in a stable. Let's talk about tooling as well. Yeah. Like around all these web development tools. A couple of years ago, we predicted people will fall out of love with ESLint. That's happened a lot slower than I imagine. And that just says something about the ecosystem that things are built around. It's the same thing with WordPress is that as much as you don't like some of these tools based on like the UX and the DX of working with them, they're just so big that it is very hard to move forward with. But we're starting to see some pickup in people. I've moved a couple of projects to Biome, which I've been really enjoying. Oxlin is another one that's built into Veep Plus. We'll see. So Vite Plus is their Vite's like paid initiative, I guess, where it's like an all in one tool that handles all of your linting and formatting and it's supposed to replace everything. I'm curious to see if that gets pickup or not. I think bold prediction. I think by this time next year, Biome is going to get snowpacked by Oxlant. Interesting What do you mean And what is snowpack Explain what that is Snowpack was kind of like the first ESM bundler that came out and then Veet came out and was better And Veet kind of instantly took over and people stopped talking about Snowpack. I think Biome and their approach does not allow for what I have heard. I'm not an expert on this. Does not allow for plugins to be compatible in the same way that they were with Prettier. This is me speaking completely uneducatedly on this. And I should probably do some research. But I think because of how Oxlant is built and the people behind it, I think Oxlant will become the default non-prettier formatter and the default non-prettier linter. Yes. And I think the reason you're saying that is because biome plugins are written in something called GritQL, which is essentially like you have to write some language that you are probably not familiar with in order to make these plugins. And that makes the ecosystem by default not as strong. And that's why ESLint is so big is like any idiot can go and make myself included can go write a JavaScript plugin for this. whereas Oxlint is written in Rust but allows you to write plugins in JavaScript and they are working towards implementing the entire spec of ESLint so that you will be able to just take your like I have some weird ESLint plugins in some of my projects where it's just like I'm not I don't want to fuss with it I hate my most hated thing is working on the tooling and trying to get it to work and when I hit save in my editor and it just formats and lints properly. I'm not touching it until the next time that it breaks. And then I'm like, oh, damn it. I got to spend some time figuring out why this isn't working. Yeah. Yeah. Do we think that anything will replace StyleLint or are people just going to continue to ignore StyleLint? Because StyleLint is fantastic. I don't know. StyleLint has such a big ecosystem, plugins. And even if these things say that they can lint CSS, I feel like that would be tough to replace everything that StyleLint is doing. I would love to see that, though. I would love to have everything linted in one tool. But I do think that Oxlint is going to be it and not Biome. Interesting. Yes. All right. We'll put money on that. Planting the flag. I'll see you in a new year. Yes. Yeah. The next one is we saw Anthropic Purchase Bun. I think we will see more acquisitions like that happen. I don't know who or what, but I do think more web technology properties, whether that is things like Bun or otherwise, will get scooped up by who knows who. Yeah. Like who needs Dino right now? You're thinking about looking at all this. Does anybody need Dino? Who needs Tailwind? Someone might buy Tailwind. Like, OpenAI or Anthropic has to buy Tailwind simply as a thank you for all of the hype coding they crapped out in the last two years, you know? Yeah, it is interesting, and I do wonder about some of these. I feel like Cloudflare is poised to buy some stuff, you know? Cloudflare bought—they didn't buy Hano, or they— Well, no, they employ the author behind it. They Aqua hired a couple people from Vercel. Yeah, yeah. Yeah. There will definitely be some party kit aggressive moves. As much as these AI things are good at writing code, people that know what's up and how to write code are still in heavy demand. Here's one of my thoughts is 2026 is going to be the year of durable compute. And what I mean by that is this whole idea of pausable, waitable workflows that you can pause and resume. So probably the big ones are like temporal and ingest, where you could simply have a function and you can await inside of it. Or you have like a step and you can wait for like four days. And then four days later, you can pick up and keep going. Or you can try something every hour and then loop over five times. A lot of the stuff that we previously would use queues for, it makes a lot more sense to just use a function that reads top to bottom and can sort of go to sleep. And then you can wake it back up and you have all of your state and all your variables and everything that you were used to in the past. So Ingest and Temporal were two of the sort of forefront in this area. Cloudflare Workers has their workflows. Vercel launched their own workflow.dev, which I previously said was Next.js only. That is not the case. It literally works with anything. In fact, they're working on a Cloudflare adapter, which I think is the move if you want people to trust it. Armin, he used to work at Sentry. He's writing one called Absurd, which is based on Postgres. What else is there? Trigger.dev. There's so many people going to this, and partially that's because of agents, and partially because like this is just a nice way to write code you know you have to send an email you want to wait for that email to send and come back or you want to try it several times over the durable function is the is going to be big in this the year of 2026 yeah i think that's interesting i am curious and by the way just to be clear you're talking about temporal the company. Temporal.io, which has nothing to do with the temporal API we just talked about. Yeah, this is a company that provides the ability to pause code. Yes, the ability to pause code. Yeah, I think you're right on this. I have not used any of these tools before. So maybe I'll pick them up. Maybe they'll hit the mainstream. Yeah. I even think about our transcription service right now. You know, if you have a function that runs for, sometimes you have a function that runs for like 60 seconds because you're waiting for some heavy thing and you don't want it to time out. Anytime you have like what would normally be a long running function or a function that needs to retry every so often or a function that needs to, that could possibly throw and you want to retry in a couple of minutes, a durable workflow is probably the move there. I look forward to hearing more about this in the future, Wes. Yes. Possibly from you. Yes. I'm working on a show on it right now. I have a card. That's why I was able to rattle off all of the names of those because I've been trying them all out. I love it. Let's talk about AI stuff. I think the AI – here's what I think. I think the framework will matter less because the AI tools get better. She said this last year. And that the AI tools will simply just pick whatever is going to work the best. Now, I do think that, and I think I've personally seen it where I'm not having to write a framework all the time or I'm not having to worry about the quality of the code based on which framework I'm picking. Now, there's a lot of alpha libraries and stuff I'm picking up that obviously I still do, but I think the tools will just continue, as we saw over the past year, to get better to the point where I can say, write me a whatever app with this version, and it's just going to get it right instead of making up as much syntax. Because the amount of improvement I saw over the course of this year was massive in that territory. So I think it will continue that path. I'm curious. So I am pretty bullish on not like Remix itself, but the idea of Remix where it is so much based on standard APIs that it just knows about fetch, web request, web response, URL search params, routing parameter matching. It knows about all of these things because they're primitives built into the language. and then if you can build your framework on top of that it needs to know a lot less about the framework and it needs to know a lot less about like the oddities of how things work so I'm hoping that that means that you're able to just give it these brand new frameworks and it can do a good job at writing that code I don't know we said this last year and it's still kicking out react in Tailwind 3 for me unless you explicitly go and do a whole bunch of work. And it's not good at writing Svelte 5, you know? Yeah. It's good at Svelte 5. I'll tell you that now. Opus 4.5. Good at Svelte 5. It's good at Svelte 5. So you provided the docs with it, and it knows how to reason about that? It's just good at it even without the docs now. The Svelte team made an API benchmarks that was determining what percentage of Svelte features that it got correct yeah and it reached 100 with oh that's amazing okay yeah that's what we need because it's so much of this is just like i feel like it's worse or i feel like oh yeah no the team has benchmarks and they've been updating at any time anything new came out benchmarks we will see more benchmarks we will be continuing to benchmark uh ai stuff i think end to end will become much more popular i called this tip to tail on a previous episode meaning that having AI involved at every step, not just like you just boop, boop, boop, and then it goes off and rips the whole website for you, but having AI involved in your planning, your writing code, your iterating, testing, it's getting really good with PlayWrite and integrated browsers into these agents where it can actually scroll the page, take screenshots, click things, drag and drop. I think having AI in the loop for every single part rather than just writing the code and you having to copy paste an error from your terminal into the chat, I think that those improvements will get much better. And I think that will significantly improve the speed at which we write this software and quality. I totally agree. I think there's even going to be new tools and new ways of working with AI that we haven't seen before. I feel like all the time stuff comes out that improves the tooling around the AI and therefore the output of the AI ends up becoming better. Have you heard of Beads? No. Yeah, Beads is something that I just found out about. A memory upgrade for your coding agent? Is that it? Yeah, so what it does, if I'm understanding this correctly, because I've only just started to use it, is it is basically taking that to-do list that many of these agents are keeping in context and moving it into JSON and SQLite, and you're able to commit it to your repo and stuff. So therefore, that to-do list of what the agent is using at any given point in time is less ethereal and more concrete and shareable across your team. And it is kind of like these systems that many of us are just kind of haphazardly doing in Markdown right now. Yeah. You know, like this status of this, open, close, whatever, blocked by, it basically allows you to have a Git-structured version of that type of workflow. Your whole process through something. Yes, I've just installed this on a project of mine, so I'm yet to see if this thing will really solve my problems. But I heard a lot of really good things about it and it got 4 thousand stars on GitHub seems to be a rising star in this space But I think things like that as well as tools like uh sentry uh at s dot i sentry yeah sentry has some really great ai tools and they fit perfectly into your normal workflow where like even in development you can use the spotlight mcp to be like i what is this issue that's going on and how can i how can i solve this but in your your production code too Like, I found that their Seer platform, the ability to take any given issue and find the root cause of it has been really nice. I think we're going to see, like, a lot more things like this. Because when you use these tools in practice, they, even if it's just a little button in your sentry that says, what's the root cause of this? Like, I was on Netlify today. And I had a deploy that failed. and you know with deploys that fail sometimes it's who knows why the hell this deploy failed there you have an ai button that says why did this deploy fail and you click it and it gives you an ai summary of why it failed i didn't have to go palling through the logs and make a guess and i think we're going to see little things like that just pop up and continue to get better next one you have here is regular people will realize that they can make personalized software and i know people hate i don't know if regular people will but but developers will developers already know this that like i have made so many little apps my christmas lights i needed to do the spacing of the window frames for my christmas lights and i just had to input the width and height and it told me exactly how far along and it kicked out a 3d printed jig that i could then print and and used to drill holes exactly spaced correctly in it. And like that piece of software, I would never find anywhere. And it was so helpful to myself. And I think regular people also have the need for that. And regular people already do this with spreadsheets. You know, like you should see some of the crazy stuff people do in spreadsheets to simply and spreadsheets are an awful way to do stuff, right? You have to nest all these things in one single line. imagine the people that have the smarts of making complex spreadsheets can now just move that over to like vibe coding and actually build software that's useful for them i don't know what the avenue for that will be right like you have like bolt and v0 which is kind of something like that already but there's got to be one more step where like i'm still not talking to parents at school pickup or or whatever you know they're maybe using chat gpt for these things but no they're not making software yet yeah they're not making software maybe that will happen yeah i feel like i feel like that's too soon but who knows you know maybe we'll have the one thing that makes it really easy you do see a number of these apps pop up it's got to roll out in like like microsoft whatever you know microsoft app maker it's got to come with like microsoft teams and like oh i just make a quick little app you know it's got to be integrated with that well i don't know what that will be but I do know that MCP and MCP UI will pop this year. You know, we've seen major improvements in MCP and we're starting to see quite a bit of work on the MCP UI front, meaning that like we saw OpenAI released their half-assed version of being able to integrate custom UIs into ChatGPT, but that spec is severely limited. And if we want to be able to just embed our own custom UIs into any chat or any AI agent, MCPUI is the move for that. And I think that we're going to see a standard. I think the MCPUI standard is going to be accepted by the MCP spec. And I think that we'll start to see it implement in a lot of these chat agents. I'm curious to see what OpenAI does around this because I know that they want to have the upper hand of control. They they might have like an apple moment where they're like no we're gonna implement it but in our own crazy way and unfortunately they can do that because they are the big one the big dog in this space i'm woefully under uh researched on mcp ui not something i have really looked at at all yet awesome see like imagine imagine you are in chat and you ask it to like i don't know uh show me the latest pizza places or display the latest syntax episode and imagine that we could just return instead of just returning data from our mcp you could just return like an iframe with html and css inside of it i don't know that this is the end a lot of people are saying like this is the replacement for the web and for the browser you know this isn't the browser is dead and we're simply just returning widgets from from that and partially i think like wechat in china a lot of commerce a lot of ordering is all done on wechat widgets and it it works over there so i think there will be a lot in which i don't think it's gonna replace the entire web i think it's a crappy experience for a lot of stuff but i think for some commerce ordering food doing research simply just returning uis from uh from a chat instead of just text is is going to be great yeah there are so there is a lot of times when like even just wanting to know a quick answer i mean ai has gotten good to the point where many times you're not searching the web for things you know yeah asking quick questions stuff that's easily verifiable or and like they're yeah they're already kind of doing that like they're returning graphs sometimes you know and but like imagine that you could just open that up to the entire web and say you can return if you install your xpedia or your airbnb or you install the syntax mcp server it should also be able to return like a custom ui whether that's just nicely formatted data or whether that's actual like buttons that you can click and edit your data inside of that. Yeah, that's reasonable. Yes, next one. Devs will fall off. I think this is something that anybody who, as a developer, who gets deep down the AI rabbit hole doesn't realize it's happening until they're like, oh, I'm not using really my brain. I'm feeling productive. Things are coming out. Sometimes the code is really bad. If I look at the code for too long, it hurts my eyes. Uh, but you're not really, you're not realizing that you're not gaining the same types of skills if you're just having it spit out. It is so funny. We talked about this a number of times on the show, but when you, when you talk or when you read comments in YouTube from people who are using a lot of AI, you can tell exactly where they are as a developer or in their AI journey, but based on like the types of things they're saying, and you always want to, oh, you'll figure it out eventually. You'll get to why we're saying this. And people just assume that you're either a hater or you're a maximalist or whatever on all of these things based on what you're saying. People are obnoxious on the entire arc of I hate AI to it's going to replace absolutely everything. And if you're an absolutist anywhere on that arc, you're obnoxious because we haven't figured it all out yet. It's very bad at some things. It's also very good at some things. And it's a lot of it. It depends. but you're getting stupid by being an absolutist along that arc yeah you are there's a comment uh on one of our videos about i was saying to only use ai to help you learn rather than to have it do it all for you when you're trying to learn a new topic that seems reasonable right if you have the ai do it for you you're not going to learn it that's if the goal is to learn the thing and uh somebody responded with this is a boomer take uh ai is a revolution boil frog boil as in i'm a frog boiling in a pot of water because uh the heat is turning up slowly that's hilarious because you're like the most anti-ai guy i know uh it's just like it's it's crazy town out there but i do think that where you are in your journey will dictate and you'll eventually be like oh shoot i'm maybe not picking up the same stuff and maybe we'll have to learn less and we'll just be kind of dumber because of it but we'll still be effective who knows some of the stuff will literally not matter that we don't know how to do it anymore i i agree with those those comments as well some of the stuff is like oh nobody can can write a nested selector or nobody can do x y and z anymore and like maybe that doesn't matter anymore however i i do know that you have to continue your skill set and ai is very good at helping you push into new skill sets and and learning them because if you just say well it does all i want now i'm just gonna push the button that end of thing you're gonna be the one that's gonna fall off with this um because you're not going to continue that arc into becoming smarter and learning new things yeah so we're keep learning things folks learn you know what i learned the other day scott what did you learn rfid and and and why am i why am i so stupid rfid and nfc um this is like a little prox mark three and like i spent a day diving deep into how nfc works the different types of it how um how these different cards work which which ones are writable how bits and bytes are stored on an nfc card you know i've got i've got like a whole bunch of them got one right here and these little tags and like i feel a lot smarter after having known all that works and i've got a lot more lower level than i do with a lot a lot of my skills and uh you just got to keep doing stuff like that yeah keep doing stuff yeah yeah i think the inshidification will continue uh as we've seen all kinds of avenues here software feels like it's falling apart products feel like they're falling apart in general and unless something big happens like i think we're we're due for another year of things feeling like they're getting worse for some reason as everybody's just trying to get that bag baby uh but that's that's yeah everyone's trying to get that bag right now yeah it's tough it's tough i i i do see and this is kind of crazy i do see a world where ai eventually helps with the incentivification yeah i mean there's like you mean like like makes things better you know because like we're talking about all of these security things and and whatnot um and all these bad things but like the hilarious thing is that that these tools can also significantly help you find totally slow code and help you find security issues and vulnerable so that's what you're talking about yeah help you fix problems help you write more uh more defensive code from the start instead of just something that works yeah yeah i agree yeah yeah beautiful let us know that's our 2026 predictions let us know down below what your predictions are what you think we are wrong or right about something as well as if we didn't hit any of these things because maybe what we'll do next year is we'll come back to the comments of this video and say what did what did the folks in the comments what is mr paperclip who wrote something about it what is it where are we at right now with this type of thing yeah mr paperclip yes yeah cool all right thanks everybody for tuning in we will catch you later peace