967: What’s Going to Happen in Web Dev During 2026 ![rw-book-cover](https://wsrv.nl/?url=https%3A%2F%2Fmegaphone.imgix.net%2Fpodcasts%2F5197fe5a-42f7-11f0-affd-87d9985a1760%2Fimage%2Fc86a54acd72683732c4773e25bf0ae14.png%3Fixlib%3Drails-4.3.1%26max-w%3D3000%26max-h%3D3000%26fit%3Dcrop%26auto%3Dformat%2Ccompress&w=512&h=512) ## Document Notes ## Highlights - **WebGPU And Shaders Spark Design Revival** - WebGPU and shaders will enable a new wave of visually distinct websites that break the current homogeneity. - Wes Bos and Scott Tolinski expect designers to embrace 3D and shader-driven effects for more expressive landing pages. Transcript: Scott Tolinski So number one here is web GPU and 3D experiences pop. Man, let me tell you, that Lando Norris website made some waves. That made some waves that won't be felt until 2026 but when i think we're gonna 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 uh elements and things like that i think it's only going to get crazier, uh, for 2026, for sure. Wes Bos I think so too, man. The cool landing page and this, this kind of, I'm going to loop this in with, with another one of my predictions is design making a comeback because everybody's cranking out the same Decent looking website with AI. Scott Tolinski Raycast ass homepage. Wes Bos Yeah. In order for, and that's not a, that's not a slant at Raycast at all. No. Because Raycast like invented that whole UI. And it, it kind of sucks that like your entire like 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 what website I'm on. Sometimes I'm on threads and Twitter. 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. ([Time 0:00:49](https://share.snipd.com/snip/58387fdd-8399-4a41-ac4f-b885672692aa)) - **Light Mode Makes A Comeback** - Light mode is resurging for daytime use while dark mode stays for night and coding sessions. - Both hosts say per-site toggles or automatic system settings improve the experience. Transcript: Wes Bos 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 gotta say Scott Tolinski I've been using light mode i joined yeah i told you there's evidence here i i uh i joined the 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 uh that's the hard part about glasses, where it was on camera. You know, 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... Your entire life? Wes Bos Not even Dreamweaver notepad days? Scott Tolinski 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 so i'm ([Time 0:03:42](https://share.snipd.com/snip/c5a7664b-99a3-42ac-a9ad-f18eb3a83d10)) - **Modern CSS Will Reduce JS Reliance** - Modern CSS features (container queries, scroll animations, relative color, popover, etc.) will let developers replace JS with CSS primitives. - Wes predicts UI libraries will evolve to rely on these standards, reducing JS overhead and improving performance. Transcript: Wes Bos One we have here is css modern css standards are going to kick ass 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 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 the 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. Scott Tolinski I'm just going to take a minute to plug 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, you should be able to have a swiper or a, like I have an Instagram style reel that's just dot reel or, you know, their header is, applies a lot of styles. So it's almost like components based out of actual, actual, out of CSS without using any things other than, you know, 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 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. They're 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? Wes Bos 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 there's this functionality point of view to it. But then there's also the reason people pick up ShadCN or Tailwind UI or any of this 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 ShadZN 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. Scott Tolinski 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 parallel on the page animate stuff in or parallax or whatever i think scroll animations have the most potential for like a major shake-up in terms of like interesting things That we can do in css like like interactions you mean right Yeah, all kinds of stuff. I was I just saw an example using them in like form inputs or something. So I mean, there's like a lot of like really interesting opportunities. But as this stuff gets better and better, I think we're going to see not just these features hit, we're going to see UI patterns, 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 we like this always happens in CS that's a new feature comes in and then people find out okay 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. Wes Bos 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 what's The event in JavaScript when the scroll snap snaps I don't even know well there's a there's an event for scroll snap snap and you listen for that and then when that happens you you update Your like 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. ([Time 0:07:08](https://share.snipd.com/snip/a6dd3fa8-1a9b-48ae-abf1-5d0ee1f9baa3)) - **Use Standard Browser Primitives** - Embrace new standard browser APIs (Navigation, URLPattern, Temporal API) to build more portable, framework-agnostic code. - Scott Tolinski suggests framework authors will adopt these primitives to enable a 'standard stack'. Transcript: Scott Tolinski Yeah, 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 that it will ship in every browser? I think we've predicted it for probably four years now. Wes Bos And last year it hit, what, it hit Chrome, kind of? It's going to hit Chrome in 2026 January. So maybe not. But it's not in Safari yet. And it is in Safari. Scott Tolinski This is a tap-in, Wes. This is a tap-in because it is teed up on everything. I feel like this will have to happen. Just a little tap-in. Wes Bos It's gotta, but will there be like a gotcha? You know, it works, but Safari doesn't do seconds or something weird like that, you know? Scott Tolinski 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 does this one weird thing that just renders the whole thing Wes Bos 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. The navigation API, URL pattern, there's a new sanitizer API, which will, like, you know, we always have to reach for like DOM purify to like, you're taking user input, you want to put It in the DOM, you got to strip out like a image on load something like that there's a new sanheiser api that's coming out all of these new standard primitives are going to primitive in 2026 so you're already seeing this with like 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. ([Time 0:13:20](https://share.snipd.com/snip/eefbc110-fbdc-4b82-85ef-a6805000a6ea)) - **RPC And Standard Schema Gain Traction** - RPC-style remote functions and a common schema for validation are becoming mainstream across frameworks. - Scott highlights standard schema adoption (convertible from Zod/archetype) as key for client-server validation. Transcript: Scott Tolinski 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 10 stack query, people are moving to RPC, Which feels like it's about time, man, I use this kind of API in meteor land. And like, when I moved to have a separate API or like, like, 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. I think this is just gonna continue to become more of the commonplace. Wes Bos Do you think that we will see a push for standardized RPC? Because we have, like you have the Svelte version and then like Cloudflare has their own called that they rolled out called Cap'n 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 Scott Tolinski Enough i will say that i do think that standard schema yes will become way more uh ubiquitous in regards to our pc 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. ([Time 0:15:27](https://share.snipd.com/snip/1635745e-986c-4a50-9064-ef7dfb1b1722)) - **React Holds Ground Amid Security Concerns** - React will remain dominant but may see slower visible change; security incidents could temper confidence. - Wes and Scott expect more attention on framework security after recent React transport issues. Transcript: Scott Tolinski Yeah. What do you think is going to happen in React Land this year? Wes Bos 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 on to 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. ([Time 0:19:41](https://share.snipd.com/snip/d85d5f68-705d-4aa9-8fbc-4f4ac183e0bf)) - **Prioritize Security Over Speed** - Take security seriously: shipping fast with AI-generated code raises the risk of major vulnerabilities and downtime. - Scott warns understaffed teams and rushed releases are driving more security failures in 2026. Transcript: Wes Bos 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. Understaffed 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 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. We've seen major downtimes in a lot of the cloud providers. ([Time 0:21:09](https://share.snipd.com/snip/bd424d6c-e378-45a8-b048-ad0006d02c88)) - **SvelteKit 3 Will Land** - Scott expects SvelteKit 3 to ship with solid async and remote data features and a stable release. - He frames this as a likely, non-surprising milestone for the Svelte ecosystem. Transcript: Scott Tolinski I think Svelte kit three 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. ([Time 0:22:38](https://share.snipd.com/snip/a52c2e45-5bd5-4d88-9601-55081617b71e)) - **Tooling Shakeup Around Linters And Formatters** - New tooling (Biome, Oxide/Oxlint) is challenging long-standing defaults like ESLint and Prettier. - Wes and Scott think Oxlint may overtake Biome and become the integrated linter/formatter standard. Transcript: Wes Bos Let's talk about tooling as well. 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 Vite Plus. We'll see. So Vite Plus is their, Vite's like paid initiative, I guess, where it's like an all-in 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. Scott Tolinski I think, bold prediction, I think by this time next year, Biome is going to get snowpacked by Oxlant. Wes Bos Interesting. Scott Tolinski 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. 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 oxalant is built and the people behind it i think oxalant will become Wes Bos The default non-prettier formatter and the default non-prettier linter yes and the reason i think the reason you're saying that is because my own plugins are written in something Called grit ql 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 like myself 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 I 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 not touching it until until the next time that it breaks and then I'm like oh damn it I gotta spend some time figuring out why this isn't working. Scott Tolinski Yeah. Yeah. ([Time 0:22:53](https://share.snipd.com/snip/28735e0a-0e30-4e86-82d3-5090a24e63ec)) - **More Strategic Acquisitions Incoming** - Expect more acquisitions of web tech firms (like Anthropic buying Bun) as larger players consolidate infrastructure and tooling. - The hosts foresee Cloudflare, Vercel, or AI firms scooping up promising projects. Transcript: Scott Tolinski 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, get scooped up by who knows who yeah like a who needs dino right now Wes Bos You're thinking about yeah looking at all this does anybody need dino yeah i don't know when someone should buy might buy tailwind like open ai or anthropic has to buy tailwind simply As a thank you for all of the vibe coding they crapped out in the last two years you know oh yeah I did it is interesting and I do wonder about about some of these I feel like Cloudflare is poised Scott Tolinski To buy some stuff you know Cloudflare bought did they they didn't buy Hano or they they they well ([Time 0:26:45](https://share.snipd.com/snip/a0cf9c52-1994-48cf-b4db-9f4c21eaeada)) - **Durable Compute Becomes Mainstream** - Durable compute and workflow platforms (Temporal, Ingest, Vercel/workflow.dev) will rise for pause/resume and long-running logic. - Wes calls 2026 the 'year of durable compute' as developers move away from brittle queue hacks. Transcript: Wes Bos 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 possible waitable workflows that you can 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. You know, a lot of the stuff that we previously would use cues 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. ([Time 0:27:58](https://share.snipd.com/snip/51e0d22e-0935-4466-984e-1c6b1a39dec4)) - **AI Makes Framework Choice Less Critical** - As AI tooling improves, framework choice matters less because generators can adapt to standard APIs and produce usable code. - Both hosts expect AI to write across frameworks better as models and standard primitives improve. Transcript: Scott Tolinski I think the AI, here's what I think. I think the framework will matter less because the AI tools get better. 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, 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 can 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. Wes Bos So I'm 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. ([Time 0:30:59](https://share.snipd.com/snip/3ae3db4a-a73b-47e4-8696-b26d6351584e)) - **Put AI In The Full Development Loop** - Include AI throughout the development lifecycle: planning, coding, testing, and iteration to boost speed and quality. - Wes urges integrating Playwright-like checks into agents so AI can interact with UIs end-to-end. Transcript: Wes Bos I think end to end will become much more popular. 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 Playwright 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. ([Time 0:33:34](https://share.snipd.com/snip/699ce990-934f-42ea-96cc-74cc0ffdbcff)) - **Beads Adds Persistent Agent Memory** - New tools like Beads persist agent state in JSON/SQLite so agents share memory and to-do lists across teams and commits. - Scott has installed Beads and notes it formalizes ephemeral agent context into a versioned, shareable artifact. Transcript: Scott Tolinski Have you heard of Beads? No. Yeah. Beads is something that I just found out about. Wes Bos A memory upgrade for your coding agent. Is that it? Yeah. Scott Tolinski 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- 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 product, this status of this open, close, whatever blocked by, it basically allows you to have a Git structured version of that type of workflow. Wes Bos Your whole process through something. Scott Tolinski 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've heard a lot of really good things about it. And it's got 4.3 thousand stars on GitHub. Seems to be a rising star in this space. ([Time 0:34:41](https://share.snipd.com/snip/c2dc9aa1-4d3b-4661-a714-5e7d7cd19ea3)) - **AI Improves Observability And Debugging** - AI-assisted observability (Sentry, Netlify) provides quick root-cause summaries that save time digging logs. - Scott highlights AI buttons that explain deploy failures and pinpoint likely causes. Transcript: Scott Tolinski 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, I what is this issue that's Going on? And how can I how can I solve this, but in your your production code to like, I found that their, 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 century that says what's the root cause of this. Like I was on Netlify today, and I had a deploy that failed. ([Time 0:36:11](https://share.snipd.com/snip/0a532fb4-1c31-4395-8a7c-15cab0b908c5)) - **MCPUI Enables Rich Chat UIs** - MCP and MCP UI standards will let chat agents return rich, interactive UIs instead of plain text responses. - Wes expects MCPUI adoption to enable embedded, clickable interfaces from AI agents for tasks like bookings or edits. Transcript: Wes Bos 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 use 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 should see some of the crazy stuff people do in spreadsheets. 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 Scott Tolinski 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, Wes Bos Microsoft App Maker. It's got to come with like Microsoft Teams and like, oh, I'll 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 MCPUI 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 wanna have the upper hand of control. 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. Scott Tolinski I'm woefully under-researched on MCPUI, not something I have really looked at at all yet. Wes Bos That's awesome. So like, imagine, imagine you are in chat and you ask it to like, I don't know, 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. ([Time 0:37:21](https://share.snipd.com/snip/e62be474-046a-4ed2-b052-33c36a947b03)) - **Keep Learning Despite AI Convenience** - Don’t let AI make you complacent: continue learning low-level skills to stay sharp and adaptable. - Scott warns developers who over-rely on AI will 'fall off' and stop gaining deeper expertise. Transcript: Scott Tolinski 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. 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 you'll you'll get to why we're saying this and people like just assume that you're either a hater or you're maximalist or whatever on all of these things based on what you're saying. Wes Bos People are obnoxious on the entire arc of I hate AI. Oh, bro. 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. Scott Tolinski Yeah, you are. There's a comment 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 somebody responded with, this is a boomer take. AI is a revolution. Boil, frog, boil. As in I'm a frog boiling in a pot of water because the heat is turning up slowly. Wes Bos That's hilarious because you're like the most anti-AI guy I know. Scott Tolinski It's just like 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 Who knows? Wes Bos Some of the stuff will literally not matter that we don't know how to do it anymore. I agree with those comments as well. Some of the stuff is like, oh, nobody can write a nested selector or nobody can do X, Y, and Z anymore. And like, maybe that doesn't matter anymore. However, 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 learning them. Because if you just say, well, it does all I want now. I'm just going to push the button. ([Time 0:42:25](https://share.snipd.com/snip/d4ca85bd-f7d9-475d-82b5-5131ab373482)) - **Hands-On Learning With RFID/NFC** - Wes spent a day learning RFID/NFC details and used hands-on gear to understand tags, formats, and writable cards. - He uses this as an example of actively learning technical, lower-level skills beyond high-level tooling. Transcript: Wes Bos This is like a little Proxmark 3. And I spent a day diving deep into how NFC works, the different types of it, how these different cards work, which ones are writable, how bits and bytes are stored on an NFC card. You know, I've got a whole bunch of them. I've 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 of my skills. ([Time 0:45:46](https://share.snipd.com/snip/93fa6793-6c68-4c05-a192-acd99f30f9b9)) - **Fast Shipping Still Produces Fragile Software** - Despite tooling advances, many products feel brittle because teams ship fast to chase AI-driven opportunities. - The hosts expect 'crappy software' and incentivization issues to persist through 2026 unless priorities shift. Transcript: Scott Tolinski Keep doing stuff. Yeah. Yeah, I think the inshidification will continue. As we've seen in 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. But that's that's yeah. Trying to get that bag right now yeah it's tough it's tough 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 Wes Bos You mean like like make things better you know because like we're talking about all 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 Scott Tolinski 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 Wes Bos Down below what your predictions are when 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 Scott Tolinski Of thing yeah mr paperclip yes yeah cool ([Time 0:46:19](https://share.snipd.com/snip/a693d9e0-9291-401e-a5f5-c955e3d5f457))