966: A Look Back at Web Dev in 2025

Wes and Scott revisit their 2025 web development predictions, grading hits and misses across AI, browsers, frameworks, CSS, and tooling. From Temporal and AI coding agents to React, Vite, and vanilla CSS, they reflect on what actually changed, what stalled, and what it all means heading into 2026. Show Notes 00:00 Welcome to Syntax! 866: 2025 Web Development Predictions 01:26 Temporal API will ship in the browser 03:33 On-device AI becomes common 06:14 WebGPU unlocks fast local machine learning TypeGPU 07:10 Models will plateau 10:32 Is there an actual use case for video and photo gen AI? 13:27 Text to UI tools get really good 16:25 Framework choice will matter less 18:53 Web components in Standard Stack, Web Awesome takes off 21:37 AI browsers and Copilot Workspace-style tools will become normal 22:56 AI browsera will become inevitable, OpenAI will launch a browser 27:51 Relative color will feel fully “safe to use” 29:02 Vanilla CSS will make a comeback 30:33 Brought to you by Sentry.io 30:58 CSS mixins and functions spec solidifies CSS Custom Functions and Mixins Module Level 1 33:25 Container style queries will ship everywhere CSS if statements 35:40 Vertical centering jokes will stubbornly persist 36:20 VS Code will reach feature parity with Cursor 38:47 More VS Code forks will appear 39:46 React Compiler drops Babel 40:34 React server components will pop 42:17 Remix re-emerges as something new 43:17 React Native will have its time 44:21 TanStack Start and Tanstack will pop 45:46 SvelteKit gets more granular data loading 46:06 Local first apps will take off 46:43 Bun keeps doing “wild but loved” non-standard features, Bun will launch a platform-as-a-service 48:22 Vite stays king 51:07 Laravel will release a CMS 52:44 Sick Picks + Shameless Plugs Sick Picks Scott: DARKBEAM Flashlight UV Black Light Wes: WOOZOO Fan 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

Speaker names marked ? are inferred from speaking time and the show’s known hosts — they are not voice-verified.

• 0:00Wes Bos?

  Welcome to Syntax. We've got two episodes for you coming up in the next week. Today, we have our reviewing our 2025 predictions. So every single year, what we do is we look at where web development is and we say, these are our predictions for the next year. What's going to happen? What's going to flop? What's going to pop? And we are going to go through all of our predictions today and say, did we hit it or did we not? And then next Wednesday, we'll have another episode, which is our predictions for 2026 as to what's going to happen. So my name is Wes Boss. Happy holidays, Merry Christmas, everybody. Hopefully, you're enjoying it. This is going to be a really fun episode. I'm here with Scott Tolinski. How you doing today, Scott?

• 0:42Scott Tolinski?

  Hey, I'm doing good. Did you just come up with that? Did it flop or did it not on the fly just now?

• 0:47Wes Bos?

  I'm just genius. Yeah, I just have incredible intuition and all of that.

• 0:53Scott Tolinski?

  Oh, yeah. No, that's great. I like that a lot. Did it flop or did it not? That's a great metric. I think we can all live by here.

• 1:01Wes Bos?

  Did it pop?

• 1:02Scott Tolinski?

  I love these episodes because this is the thing I like doing the most. Just pontificating on like theoretical, who knows what? Is this going to happen or not? I feel like I'm always a little too optimistic on stuff. So very interesting.

• 1:17Wes Bos?

  Last year, last year, we had a lot of like, man, we were a little too optimistic on that. But I have to say that this year, we nailed quite a bit. So let's get on into the first one, which was the Temporal API will ship in the browser. So I said both Chrome and Safari will ship by end of year. And Scott said that it will be in at least one browser. So if you haven't heard of it, Temporal is this massive API that is set to replace the Date API. You might be saying, well, what's wrong with the Date API? Stop changing stuff.

• 1:52Scott Tolinski?

  I don't know if anybody's ever said, what's wrong with the Date API?

• 1:55Wes Bos?

  Yeah.

• 1:58Wes Bos?

  Fair, fair. So the Temporal API will allow you to encapsulate durations. So if you've ever wanted to say, I want to somehow make three days. How can you say that in a standardized way? Or if I want to do January 25th to January 26th, but regardless of time zones, or if you do want to include time zones in a start and an end. There's just time is, time is hard, time is complex. What is time? And the Temporal API is going to solve all of these. It's going to be a absolutely killer API. And where are we at right now? I think we nailed it. So here's where we're at. May 26th, it was added to Firefox. Good.

• 2:43Wes Bos?

  December 3rd, it entered into Chrome Beta, which means that a month later, January 7th, we're going to, January 7th, 2026, we're going to be, it's going to be landing in Chrome Stable. And then it's currently in Safari behind a flag. So like, we've been talking about Temporal for what? Like four years? And I feel like we're, we're pretty much there. I'm super excited for it.

• 3:11Scott Tolinski?

  I love Temporal and I've been using it with the Polyfill for like three years now. So, you know, I've been using it for a while and I, I've shipped stuff with that Polyfill. So yeah, I'm stoked about it, but I, this is the type of movement that it feels like I've been wanting to see for a long time. And here we're at. Yeah, you can start to learn Temporal, y'all. Our next one is that on-device AI becomes common. On-device small AI models, OCR detection becomes much more ubiquitous and developer-friendly, running either in the browser or on user devices. Well, we did see in browser AI stuff in Chrome. I feel like a lot of these types of features, they kind of.

• 3:54Scott Tolinski?

  Hmm. They go under the radar a little bit. We are seeing more OCR stuff. We are seeing more speech to text, text to speech. We are seeing all those things. As far as like small model AI, I think that's happening more often than we realize.

• 4:10Wes Bos?

  I don't think it's as common. I'm gonna say we missed this, and this is someone I love, Transformers JS. I've been playing with a lot of the built-in Chrome stuff where you can use a logo model in Chrome. I don't think we're there quite yet. I think people care much more about it's not that expensive to hit an API.

• 4:28Scott Tolinski?

  Right.

• 4:28Wes Bos?

  But I, I think as people start to say like, what, what does it mean when you don't have to pay anything for it? When it just runs on your user's device? What could you, you could run it constantly in a loop, you know? So I, I don't think we're quite there just yet. You are seeing more, a little bit more niche models. You know, toxicity detection is a really good one where if you need to detect if something is spam or something's, someone's saying something really off, Chrome is trying to figure out what the API looks like. What does it look like to have structured inputs and outputs? They're really just playing with a lot of that right now, same way Transformers JS. So I'm gonna punt that to next year.

• 5:09Scott Tolinski?

  You say miss.

• 5:10Wes Bos?

  Well, like, and I'm saying that as someone that's used them several times this year.

• 5:14Scott Tolinski?

  But if we're going by what the prediction actually was, it becomes more common. More common than what? It was before?

• 5:23Wes Bos?

  Yeah.

• 5:24Scott Tolinski?

  That's a win to me.

• 5:25Wes Bos?

  Yeah, you're right.

• 5:26Scott Tolinski?

  It's not, it's not, it's not that it is. I'm trying to, I'm trying to get us some points here, Wes. I think it became more common. Whether or not that became ubiquitous, I guess we did say much more ubiquitous, not it will become ubiquitous. So I think we saved ourselves with the wording here.

• 5:43Wes Bos?

  I was talking to some of the engineers that work on Chrome, and we're talking about this, like, like, what are the benefits to running on device? Like, there's obviously speed, there's privacy, and there's cost, right? And right now, I don't think that people necessarily care a ton about cost. It's way faster to use a hosted model than it is to use a Local model plus they're way better. And unfortunately, I don't think a lot of people necessarily care that much about the privacy aspect, which kind of pains me to say, but I think that's just the reality.

• 6:14Scott Tolinski?

  Yeah. Well, the next one is that WebGPU unlocks fast local machine learning. And I do not, I think it might be a little bit early, Ben, but type GPUs doing some cool stuff where they even have like an example of text prediction and stuff using WebGPU. I don't think enough people are doing this just yet. People are doing it, but I don't think enough people are doing it.

• 6:37Wes Bos?

  The WebGPU stuff just dropped in all the browsers and WebGPU is what's going to make it fast in browser. Like I have an example where I generated alt text for with Transformers JS. And the Wasm example versus the WebGPU example is six times faster. And like then it moves from a cool demo to like, oh, we could actually use this. So I think that's the one, that's the one that we're going to hopefully see more of in the next year. But that's, that's the next show. I'm not going to talk about that.

• 7:07Scott Tolinski?

  We're not making any predictions right now. Yes.

• 7:10Wes Bos?

  So let's talk about AI. So our big prediction was that the, the models will plateau in quality and we're going to see big improvements on how the products use the existing models. And I think we nailed that, but like, let's, let's dive into like the different aspects of like, where are we with AI versus 365 days ago, right? Because in some regards, the models didn't get that much better, right? Like we saw incremental improvements. You think they did? Okay.

• 7:43Scott Tolinski?

  I think they did.

• 7:45Wes Bos?

  So tell me about this.

• 7:47Scott Tolinski?

  I think if we're comparing how accurate the responses of a raw input versus output of something like, uh, what is the latest one from, from Anthropic?

• 8:01Wes Bos?

  Yeah.

• 8:03Wes Bos?

  It is. 4.7.

• 8:04Scott Tolinski?

  Or Opus 4.5 or Sonnet 4.5. I think Opus 4.5.

• 8:11Scott Tolinski?

  Is raw input versus raw output is light years better and more reliable than what we had last year. I just do. I trust the output of Opus 4.5. So much endlessly more with all kinds of tasks. It's still not great at CSS. It's still not great at some things using browser standards, but the end result I think is much better.

• 8:40Wes Bos?

  Okay.

• 8:41Scott Tolinski?

  Input, output.

• 8:42Wes Bos?

  The input, output. So I think that the actual tools that we use with these things got significantly better. So the agents, the like, the quality of code that agents are able to generate, even with if you're comparing them with the models that we had at the end of last year, the output of them are so much better because of the tooling built around it, you know, like the cursor, Copilot, all of these agentic tools that sort of go back and forth and reason with themselves. The quality of that has gotten significantly better. In fact, like, I was like halfway through this year, thinking about this prediction that I had. And I was like,

• 9:22Wes Bos?

  oh, boy, was I wrong about that. Because I was like, I think what's the incremental improvements? But like, I feel like the actual quality of the code that these things output, like you said, is significantly better. And I'm attributing that just to tools, but maybe I'm wrong about that. It's more model based.

• 9:40Scott Tolinski?

  I think it's both. I think there's a big increase in both because we did see a tremendous improvement in the tools themselves. But I do think if we're if I'm going to, you know, like I said, Opus 4.5, and I'm giving it the same question, I think I would like the answer enough that it makes me feel like it's a huge leap. Because we're like, last year, I wouldn't trust it at all. Last year was like, kind of a fun experiment. I would make fun of vibe coding. This year, I can vibe code personal software using these tools and actually feel like it's not total garbage. In fact, I've gone back with. Projects that I would have vibe coded last year using the latest model.

• 10:26Scott Tolinski?

  And it could clean up the code substantially better. And that is part tools, but I also think the models is a big part of that.

• 10:32Wes Bos?

  The models as well. Now let's talk about stuff that's not coding like video and photo gen has gotten unbelievably good. Right? Like we saw.

• 10:43Scott Tolinski?

  Unfortunately, shocking.

• 10:44Wes Bos?

  Unfortunately, Sora Nano Banana. It's a weird place because it's they're unbelievably good, yet a very not that useful. There obviously are some use cases for it. Like we're designing a jacket right now. And I've been going back and forth, doing some mockups with that and giving getting ideas. And I find that to be super useful. But like aside, like Sora was funny for like a week and a half and haha. And now it's just like, like boomers getting tricked on Facebook by videos that have the watermark removed. And like Nano Bananas, people just posting like, like fake stuff. Like, I think it's like, at least right now, this stuff is a massive net negative in terms of like, just trust.

• 11:24Wes Bos?

  And is there any good use for these like lifelike videos aside from it being absolutely hilarious?

• 11:31Scott Tolinski?

  I don't even think it's funny. I like, I was entertaining for like an hour and a half and I was like, oh, that's funny. Or it's creepy or it's weird. But like, man, I can't imagine more than that being like, haha, I made this now, haha. It's like, oh, it was really funny when I made Wes Buss in The Sopranos looking like Pikachu. Okay, that's, that's very funny to me.

• 11:52Wes Bos?

  But they're.

• 11:52Scott Tolinski?

  But.

• 11:53Wes Bos?

  Sora is freaking so funny though, like the one where the, the a pig comes through the window and the man's sitting on a toilet. Oh, man, I still laugh about that like months later.

• 12:05Scott Tolinski?

  There's something that it's like.

• 12:06Wes Bos?

  It's like meme funny, you know, like people are just like constantly creating new memes and pushing this thing to the limit. But like not all that useful.

• 12:15Scott Tolinski?

  Yeah.

• 12:16Wes Bos?

  Especially like all the energy and stuff that used to make me laugh. Yeah.

• 12:21Scott Tolinski?

  It's useful in creating really bad commercials. Man, I, when I see like an AI commercial or something.

• 12:27Wes Bos?

  Yeah.

• 12:28Scott Tolinski?

  The problem is, is that the people creating a lot of this stuff, the same reason why it sucks is the same reason why the people creating it were not creatives or commercial creators before. They're like the business people who are all like, oh, now I can make a commercial with AI, but they have no artistic vision at all. So that whatever they put into the AI is still going to come out sloppy, uh, because they don't have an artistic vision for it.

• 12:54Wes Bos?

  Yeah.

• 12:55Scott Tolinski?

  Uh, you don't have crafts people using this stuff. It's the marketers or the grifters doing it.

• 13:00Wes Bos?

  That was actually one thing about Sora is that Sora somehow figured out how to make the videos funny. But then like, like after a while, you kinda, you kinda understood all the hilariousness, you know? And it only knows how to, you, you find all the like tells, you know, like quick talking back and forth, like a cutoff at the end of something. Those are what makes it funny, but then, I don't know, after a couple of weeks, you realize, oh, that's just the, the recipe for making it funny.

• 13:27Scott Tolinski?

  Yeah. Next one. Text to UI tools get really good. Things like bolt dot new, V zero, et cetera, will get much better and faster. Uh, they get so good that some people stop using Figma, at least for early prototypes. Yeah. I don't use them still because I think that's like the part of the project that I personally want to have a hand in the most. Is the early stage parts of it. But I do feel like the tools got, I wouldn't say really good. They got better.

• 14:03Wes Bos?

  Yeah.

• 14:05Scott Tolinski?

  But that's my bias talking.

• 14:08Wes Bos?

  I think we nailed this prediction because Cursor, VS Code, Anti-Gravity, Chrome's MCP, Puppeteer, all of these agents now have the ability to take the UI into account. Both like screenshotting it, both taking videos as well as like clicking on things. And that whole loop, I feel like makes the debugging step and like prototyping step a lot better. I don't know that like, like tools like explicitly lovable Bolt and V0. I haven't seen that grow at all in the like dev space, but I know it has grown quite a bit in the like non-dev space, the tinkerer space, you know, and that's, that's a whole new

• 14:52Wes Bos?

  aspect of people who are just trying to like, oh, I'm, I'm fairly technical. Now I can build stuff. So I feel like they've gotten pretty good in that regard.

• 15:02Scott Tolinski?

  Yeah, like I said, it's definitely my bias talking and the fact that I like almost don't want them to be good. So yeah. I think I'm aware of that at least.

• 15:12Wes Bos?

  That's, that's actually a funny, a funny question that I've, I've asked myself a lot of times is that like, would you go back to a point where we didn't have any of this AI stuff for coding? And I would probably say, yeah. I would like, I was, I was very happy. Yeah, I was, I was skilled, very happy with where we were. I enjoy a lot of these new tools as well. And I know I love using them and I think it's great. And I'm not like pooing them at all, but I also would be totally happy if this stuff ever popped up either.

• 15:44Scott Tolinski?

  Yeah, I will say that I've, I think if you use the tools correctly, not that we need to go in on this, but like, yeah, I feel like I've learned a lot more this year than I have in years past because of these tools.

• 15:56Wes Bos?

  No kidding.

• 15:57Scott Tolinski?

  They can unstick you a lot.

• 15:59Wes Bos?

  Yeah, yeah, that's true. And they can put you in spots where you might not have been able to do things, you know, like I did software hardware, hardware projects this year where I probably would not have been able to to do that, right? You know, writing a little bit of C++ or just simply knowing where to go and what tools to use and to go next. I don't know that I would have been able to do that without an AI assistant sort of pointing me in the right direction. The next one we have here is framework choice matters less. So AI tools will get better at ingesting documentation, understanding which version of a library you're using, React versus Svelte or whatever. I don't know. I put a question mark behind this one because I'm not sure if framework matters less. What do you think?

• 16:43Scott Tolinski?

  I don't know if framework matters less. I do feel like the other parts of this got absolutely correct. The tools got so much better. Opus 4.5 can write perfect Svelte 5 code every single time. No back and forth whatsoever. And that's because of, one, the model got better. But two, also, there's even before the model got better, there was things like the MCP servers that can do auto. Like, there's so much better ways of interacting with the AI. I think that it did. But whether or not this one was lagging behind, funny enough, I did not look at our predictions review

• 17:25Scott Tolinski?

  before writing our predictions for next year. And I wrote word for word, framework choice will matter less because of AI. And now I'm looking at this, I'm like, oh, man. So I probably wrote this one in the first place because this is the something that I I hope. I hope that we can pick the tools that are best for the end result rather than the tools that are the most popular. This is me, you know? So I don't, I don't know. Maybe this one was a fail in terms of that. Framework choice probably does matter less, but I don't think people have caught up to that.

• 17:58Wes Bos?

  No, no, I don't like, I think it's gotten a bit better with contact seven MCP, but I still don't feel like it's there like I I've been trying to use this JavaScript framework called manifold for doing 3D renders. It's similar to like something called Open Scad in the 3D space where you can just like great things and merge them and extrude them like a 3D program you would for printing and whatever. And it just, I want it so much better, but it's just AI sucks at it and it's fully typed in all of this and I just cannot get it to to do better. So I should, it's probably been about six months since I've played with it. I should bring it back now and see.

• 18:36Scott Tolinski?

  Bring it back, Claude Code Opus 4.5. I think you might be surprised.

• 18:41Wes Bos?

  The docs have no examples. It's simply just, here are the interfaces, here are the methods, here are the values that are returned. And it just cannot fathom how to use it. It just keeps imagining things.

• 18:53Scott Tolinski?

  Next one, web components in standard stack, Web Awesome takes off. Man, this one did not happen. And let me say, I like Web Awesome, but it did not take off. It's not even out of alpha yet. I don't think it might be in beta now. I would be interested to know what's taking so long. Maybe it is our latest release as version 3.0 and it looks like it is stable.

• 19:17Wes Bos?

  November 6th, it was released.

• 19:19Scott Tolinski?

  Yeah, you know, I I use Web Awesome on, I will say on Sinhacks, I used Web Awesome. And for the most part, it was a really nice experience. So there was another really good one, Quiet UI from Corey Loviska, who was a part of or is a part of Web Awesome, but it is no more.

• 19:42Wes Bos?

  Oh, man.

• 19:44Scott Tolinski?

  Yes.

• 19:46Wes Bos?

  Quiet UI was from Corey, who built the Web Awesome as well.

• 19:51Scott Tolinski?

  Yes, and I know what happened here. I'm not at liberty to say on the podcast, but it's a shame because Qui UI did look fantastic. It does seem like somebody forked it, but I don't see any progress on that either. So ah, maybe you can still get the forked version of it or maybe not. I I'm I this is something that I was really excited to see and then really bummed out to see is currently unavailable due to some complications. But yeah, so I think developers are using web components more. I do think web components have gotten better. I think they have grown in popularity. I personally use them more. People won't offer their own, but will happily consume them.

• 20:35Scott Tolinski?

  I think all of those things happened, but Web Awesome did not take off.

• 20:39Wes Bos?

  Yeah, that was our prediction.

• 20:41Scott Tolinski?

  Yeah.

• 20:41Wes Bos?

  Here's my my take on all of this new and better stuff, because we see it in CSS as well. CSS has had all kinds of new stuff in the last year. A whole bunch of new stuff is coming up and you don't see a lot of people using it. You still see them using a whole bunch of JavaScript stuff. And I think the reason behind that is because people just want to use like a ShadCN or they want to npm install something and have it just work. And they want to be able to debug it easily and whatever. And they don't necessarily care that there's all this like standardization and beautiful fundamentals behind it. But I believe that is going to change because I think that a lot of these UI frameworks

• 21:25Wes Bos?

  are going to be using them, like obviously Web Awesome is already behind that. But I think that they will become more mainstream. And I'm going to stop predicting for the next year because I'm going to put this in the next episode. But I think that's why. Next one, AI browsers and search. Copilot-style workspace-style tools become more normal. So the way that we thought about this is like, what does coding actually look like? Right? You have Sitting in an editor, you have this like new agent UI that a lot of these tools are trying to push on you. Cursor just by default now goes to the agent tab instead of the code tab, which is kind of obnoxious. And all the other tools have something similar to this.

• 22:06Wes Bos?

  And GitHub is going absolutely ham on trying to shove all of this stuff into GitHub and down your throat. I don't know. Like, are these becoming as mainstream as we thought they would? Right? I certainly find them to be useful, where you can go on GitHub and say, hey, review this, or grab this, grab this thing. But I don't know that that's the UI that is the absolute killer UI. What do you think?

• 22:29Scott Tolinski?

  I think that they have become more reliable and more mainstream. I do think that has happened. And the latest stuff where you can assign different agents to different things, that they announced the GitHub Universe, all that stuff is great. So I personally think that, yes, these things did become normal and more mainstream. Yes, I will say that. Have they become great? I don't know. I've used them to fix some issues here and there. Am I using it to do most of my coding? No.

• 22:56Wes Bos?

  Next one we have is the AI browser will become inevitable. And I'll throw the next one in there as well, which is OpenAI will launch a browser. So OpenAI obviously shipped their own browser. It was absolutely awful, very slow. I don't know anybody that's using it. It's very slow, very limiting, very frustrating to use, but they're trying to cram you into the hole that they want the web to be. Plus, like, what, Scott changed browsers, what, six or seven times?

• 23:24Scott Tolinski?

  Maybe more than that, yeah.

• 23:25Wes Bos?

  What browsers did you use this year? Let's count them.

• 23:28Scott Tolinski?

  Like, for longer than a week?

• 23:30Wes Bos?

  No, just like, what did you dip into? There was obviously the OpenAI browser, which is, I don't even, what is it called? Comet?

• 23:37Scott Tolinski?

  I'm gonna, no, that's perplexities. I'm gonna be real with you. I did not ever download the OpenAI Browser, not even for half a second. But I did use Dia AI Browser. I did use perplexity's Comet for a good long time AI Browser. I used Arc for a long time. I used Chrome, Chrome Canary. I tried to use Firefox for just a little bit. And then I've been using Helium for the past month and a half or so. And really liking Helium is where I'm sticking for now. I will say with the Comet Browser is great. There's a lot of, I didn't want to use it for my daily browsing

• 24:19Scott Tolinski?

  because of privacy concerns. They're sending a lot of information to perplexity. And I just, I don't want them to have access to my bank account and all this information. But like when I wanted to do a little bit of things here and there, it was super useful. Like for instance, if I wanted it to put me on, like CJ was flying to New York. I wanted to be on CJ's flight. I copied his flight number. I pasted into perplexity and I said, put me on this flight. It got me all the way to the checkout screen. Now I did just go ahead and put myself on that flight and I clicked buy. And then later realized that CJ is, CJ likes early flights.

• 25:00Scott Tolinski?

  That flight was at six in the morning and I'll never forgive myself for just yellowing onto that flight. Cause that was, that was crazy. I've never flown that early, or at least I have, but not, I don't like to. Well, I'll tell you that.

• 25:13Wes Bos?

  But yeah. That's gonna be the new, oops, autofill did it. Like anytime I sell stickers or whatever, or the syntax swag store, you get all these like emails being like, oops, I got my address wrong because autofill did it. Now it's gonna be, oops, AI accidentally put me on a flight.

• 25:30Scott Tolinski?

  Oops, AI put me on a flight. Yeah. And if you want to know like the type of brain rot that you're getting from these AI systems. I didn't know that the flight was at 6:00 AM until the week before I was getting on the flight. And I was like, oh, let me see what time I fly. Oh no, what happened here?

• 25:47Wes Bos?

  You know what's one? One tool that I I think ChatGPT is starting to get this, but I just want like a an AI brain where I can just drop things in that I need to remember at some point, you know? Sometimes I'm putting something away and I say to myself, I have to remember that I put this here because I'm gonna be like in in six months, I'm gonna or like my wife couldn't find the stockings. And she's like, I put them away somewhere and I can't remember where and wouldn't it be so nice? Just to have a little like walkie talkie. I'm putting the stockings near the kids boots. You know, just I want that. No, just little reminders, you know, or on because I on my watch, you know, remind me X, Y, and Z. I use that a lot.

• 26:32Wes Bos?

  But couldn't I have like a brain where it's just like remind me and or here's what I'm doing or?

• 26:40Wes Bos?

  I use this type of screw, like the lug nuts on the tractor at the cottage. That's something I have written down somewhere and I needed it at one point. I couldn't find it and I'm like, I know I put this somewhere or blinds. I have every window in our house measured up. And I don't know where it is. Is it in a note? Is it in a Google sheet? Did I put it in a markdown file somewhere on my computer? I don't know and search sucks on my computer, so I can't find it.

• 27:11Scott Tolinski?

  The one I would like is my my electrical box. I have repeatedly toggled them all on and all off. And every single time when I'm doing it, I'm like, oh, when I figure this one out, I'm going to use the marker and write down what the circuit is. And then I find it and then I do my project and then I turn it all back on. I say, oh, but oh, okay, let's go do the next thing and I never write it down and oh.

• 27:38Wes Bos?

  Yeah, the next time I do that as well, half hours are wrong for some reason.

• 27:42Scott Tolinski?

  Yeah, yeah. And everybody does it in permanent marker on there. So it's not like you can, who knows what the last owner wrote on there or something.

• 27:51Wes Bos?

  All right, let's talk about CSS predictions. Relative color syntax, this is where you can take a color, whether it's an HSL, RGB, hex, whatever, and you can use from, and then you can split it out into RGB values, HSL values, and you can increment, decrement them, whatever. Beautiful syntax for being able to calculate a color. And Scott, you said you wanted at 94% usage. It has been in every browser. It actually reached baseline 2024, meaning that it's been in every browser for a full year now. And I think that it's very safe to use.

• 28:29Scott Tolinski?

  I love relative color syntax. This might be my MVP for the year. Stamp it. I love this API. I've built color systems that respond to light and dark mode, transparency, I built a crazy color contrast, automatic color contrast thing the other day with this syntax. Man, this syntax is underutilized and just all around fantastic. It has greatly improved my CSS in just ways that I cannot express on this podcast. Yeah, I love relative color. Our next one is vanilla CSS will make a comeback with all the CSS superpowers, scoping, anchors, relative color. More teams will just ship plain CSS.

• 29:12Scott Tolinski?

  I do think this is happening, whether or not it has become like a movement or what. I do think this is happening all the time. I do see more and more people shipping some of this latest stuff. I personally don't even add post CSS to anything. I don't add CSS to anything. I wrote my own utility framework. I wrote no utility framework. You can tell I wrote that because that's me. That's the type of thing I would say. Yeah, I think, man, CSS is just so capable now and is only getting more capable. So I do think it is making a comeback to just use this.

• 29:48Wes Bos?

  Vanilla CSS, huge. I think it, like, we're still early in a lot of these features, whether it's people still need to support. Older like iPads, you know, like that's probably the biggest. Talk about IE back in the day. The biggest pain in in supports butt is old iPads. People don't upgrade their iPads or they simply cannot, you know, like everybody has an iPad. That's nine years old and they use it every now and then. And they're just, they're simply add a browser where they cannot upgrade any further, which is really frustrating. But I feel like we're right on the precipice.

• 30:23Scott Tolinski?

  Yeah. If they were to install the latest Mac or iPad OS on that thing, it would literally melt their device because it's so bad.

• 30:33Scott Tolinski?

  And if you want to see all of the errors in your application, you'll want to check out Sentry. At Sentry.io forward slash syntax. You don't want a production application out there that, well, you have no visibility into in case something is blowing up and you might not even know it. So head on over to Sentry.io forward slash syntax. Again, we've been using this tool for a long time and it totally rules. All right.

• 30:58Wes Bos?

  CSS Mixins and Functions spec solidify. So there was rumblings at this time last year of adding both Mixins and Functions to CSS. So similar to if you've used SAS before, where you can apply a whole bunch of CSS to a selector, or you can make custom functions that will be able to take inputs and and return values. So the CSS Mixins is now a solidified spec. It's still in draft mode, but it's been updated as much as about a month ago as of recording. And the spec has has gone forward with only defining custom functions as part of one.

• 31:41Wes Bos?

  So then the idea of Mixins, which I'm pretty sure I believe, we did a whole show on it, but I'm pretty sure Mixins is being able to apply multiple functions to one. Is that right?

• 31:54Scott Tolinski?

  I I'll be real with you, even as far as going back as SAS goes. I never had a firm grasp on difference in usage between Mixins and Functions. Because at the end of the day, you're just looping in a bunch of complex logic. I guess. Functions are for defining values and mixes are defining chunks of CSS? Or am I, is that?

• 32:17Wes Bos?

  Yeah, I'm just reading through the spec really quickly and that's, that's what it is. Is functions are for calculating a single value and a mix in is for returning multiple

• 32:27Scott Tolinski?

  Okay.

• 32:28Wes Bos?

  Values from that. So if you, if you wanted to have like a mix in to make like a syntax button, you know, or it has, has a specific border radius and a drop shadow and a background and calculate the, that, that's where a mix in would work. So in order to have those things, first you need functions to be able to actually take inputs and then return values. And then you can get more complex with it. So it looks like the spec has been firmed up and it looks like in next year, we're going to start seeing this land in browsers. I'm pretty excited about that.

• 33:01Scott Tolinski?

  Yes. Yes. I am very stoked for this. I'm going to use this all the time. There's so many things I would encapsulate in a little function instead of having to write some mass amount of calc and who knows what inside of my CSS.

• 33:13Wes Bos?

  So true. Yeah. Just be able to put that, because those things are so hard to reason about and just being able to put that in a nice function, which is simple, is going to be key. But on the same regard, we also got, we also predicted that container queries are going to be shipping everywhere. Sorry, not container queries, container style queries. Container queries have been in the browser for a couple of years now. Style queries, which is you be able to essentially, and it, we essentially it was if statements against container properties. So you can say like, if this container has a flag of dark or if this container has a variable that's set to subtle, then do the following things. So we got that, that shipped in all of the browsers. However, we also now have if statements added

• 33:59Wes Bos?

  to the browser. It's only in Chrome right now. It's limited availability, but.

• 34:06Wes Bos?

  The idea of if statements are not just applied just to container queries, but you can also apply them to media queries and what else? Feature queries. So that's still a ways out, but I'm pretty excited about it.

• 34:20Scott Tolinski?

  Yeah, yeah, I'm stoked about it, too. There is a point, though, when you when you wonder like, what can be done just by adding classes or not or whatever? And the if statement part is very, very interesting. I did a little bit of a deep dive on it at some point. So, yeah, it is a cool, cool API. Container style queries. You said the style queries shipped in every major browser?

• 34:45Wes Bos?

  Yep, let's look at the can I use for that?

• 34:48Scott Tolinski?

  No, I'm seeing that they are partial support.

• 34:53Wes Bos?

  Yeah, partial support refers to only working on CSS custom properties in a style query. So it only works to say-

• 34:59Scott Tolinski?

  But not in Firefox at all.

• 35:01Wes Bos?

  Oh, you're right. Why did I see that? Okay, yeah, wrong about that. Yeah, well, not in Firefox, unfortunately. But honestly, I think that all of this stuff needs to land before we like fully see it. You know, so we need if statements, style queries, functions, mix-ins. All of this essentially CSS is becoming a programming language. And then we're going to be able to do some serious, serious stuff with this.

• 35:29Scott Tolinski?

  Yeah, yeah, I was gonna say that would be low key a groundbreaking or ground shifting API to have dropped in all major browsers. I'm stoked for style queries. Vertical centering jokes will stubbornly persist. Nailed it. Yes, people still make jokes about this stuff. Man, it's so easy to center anything vertically, horizontally, whatever. There's billion different one liners to do it. It's not hard, folks, so.

• 35:55Wes Bos?

  You can vertically align something on a block level element, which means a div. You don't use grid or flexbox or anything with the align content center. You don't have to- Say that joke anymore.

• 36:08Scott Tolinski?

  Yes.

• 36:09Wes Bos?

  Stop doing that joke.

• 36:10Scott Tolinski?

  Although it doesn't work in CSS battles because every single time I try to use it in a CSS battle, it fails because of however their renderer is doing it.

• 36:18Wes Bos?

  There's something weird, yeah.

• 36:20Scott Tolinski?

  Yeah.

• 36:20Wes Bos?

  Editors, IDEs and dev tools. So we predicted VS Code will reach feature parity with Cursor. I don't know that that happened. So the agent, agentic stuff in VS Code got very good. However, I feel like the, and I know that the tab completions, which is one of my favorite AI coding things is just not there. Like, and I've been, I've been DMing with a bunch of people that work on, on VS Code and being like, I've sent them videos. They turn those videos into like, I have, I have code and Cursor up. And I was like, these are the four things I want to do.

• 36:57Scott Tolinski?

  Yeah.

• 36:58Wes Bos?

  And I, I just, Cursor does it beautifully and tabs it, does exactly what I want. It jumps to where I want. And then VS Code like forgets a closing curly bracket, which is so frustrating. And it's, it just, it's not quite there. They're obviously working on it, but just Cursor is still miles ahead on the tab completion. So I, I don't think we got that one.

• 37:21Scott Tolinski?

  It's gotten a lot better though. I'll tell you that. VS Code's gotten a lot better. Yeah. I think the tab completion is not something I use that much.

• 37:29Wes Bos?

  No?

• 37:29Scott Tolinski?

  I'm gonna be honest with you. I don't. Yeah. I don't, I don't know if it's because Zed doesn't have as good of tab completion as Cursor. And I used VS Code primarily before moving to Zed. And so like, maybe I just haven't had the really good tab completion in a little while.

• 37:49Wes Bos?

  Yeah. That's the thing. It's like, I've got so used to having very good tab completion in Cursor. But then you, you talk to people about, that work on these things and they say, it's really hard because some people think it's too eager. Some people think it's not eager enough. Some people hate it. Some people can't live without it. And it's all of this, like, everybody's just kinda at a different spot with it. Like, even sometimes I have to turn it off when I'm doing some types of code. I have to turn it off because it's just way too aggressive as to what I want. It's like, ah, I maybe can predict everything you want to do here. And then it's like, no, no, I'm just trying to put a border on this thing.

• 38:28Scott Tolinski?

  One thing at a time, please. Yes. Chill out.

• 38:31Wes Bos?

  But then other times I'm like, well, yeah, keep going. I want you to do it. So I don't know. Like I need, I almost need like a knob where I can like.

• 38:40Scott Tolinski?

  Yeah, yeah. Yeah. How, how eager should this be?

• 38:44Wes Bos?

  How much? But like, yeah, that's, it's a tricky one. More VS code forks will appear. Of course, we had anti-gravity and Google had two forks of their own in 2025 pop up. They have one called Jewels and they have anti-gravity, which is kind of like windsurf.

• 38:59Scott Tolinski?

  Yes.

• 39:00Wes Bos?

  Which is windsurf, but also not. And like, yeah, it's kind of their launch kind of flopped though, because they, they launched it and then nobody could use it. It didn't work for like, like a week.

• 39:13Scott Tolinski?

  And it's still getting kind of, yeah, iffy reviews.

• 39:16Wes Bos?

  Yeah. So unfortunately, I think they pushed it out way too early because everybody tried it, sucked, and everyone went back to cursor, which is really frustrating for them.

• 39:26Scott Tolinski?

  And they got Jewels too. Like, what are they doing? It's classic Google stuff. But you'd think by now that they would, they would figure this out.

• 39:33Wes Bos?

  Yeah. And they have IDX, which is now Firebase Studio. So Google has at least three IDEs, identical IDEs.

• 39:43Scott Tolinski?

  The forks will continue until more morale improves. Next one here is for React ecosystem. React compiler drops Babel. We said that because Babel is ancient technology at this point, that the React compiler would drop it. No, that's not true. It did not happen.

• 40:01Wes Bos?

  That did not happen.

• 40:02Scott Tolinski?

  Is anybody using the React compiler? I'm not.

• 40:04Wes Bos?

  That's a good question. Yeah. As, as much as people talk about it and as much as people say, like rendering performance and whatever, and there are lots of situations you can point to where like this thing is slow, like GitHub pull request is a really good example. I think most like relatively simple React apps don't have that problem. Or people don't even know that they are re-rendering unnecessarily.

• 40:29Scott Tolinski?

  I think it's people don't know, not that they don't have that problem. Yeah.

• 40:32Wes Bos?

  They don't know what they know. But then we also had one here is React server components will pop. They'll hit their stride and we'll see. A lot of universal RSC components, meaning that like my, my prediction here was that you'll see a people ship React server components that include the client logic, the server logic, the styles, API calls, all of this stuff bundled into one component that you can do. And I will argue that that did not happen.

• 41:02Scott Tolinski?

  Yeah.

• 41:02Wes Bos?

  And in fact, we just had a massive security issue with React to Shell, which was basically every React website that used server components. So not every React website, but every, every React website that used server components. My own website was on Waku. Obviously all the next JS websites out there, anything that's built on Parcel with React server components. They were all effective and it was a pretty big, pretty big.

• 41:31Scott Tolinski?

  It allowed, yeah, remote execution, remote code execution with just a post request. So I mean, it was pretty, yeah. So.

• 41:39Wes Bos?

  Pretty rough, which is honestly, I don't, I think that will sour a lot of people on React for quite a while. And it sucks and it's, I don't want to like point fingers and I don't think anyone should be dancing on the grave. Because that this happened, I know a lot of people like it was very serious and I'm sure a lot of people had a very bad week. That sucks. And I think that that will be a, a bad bandaid. People are waiting for something like this to happen to React, you know, because of all the crazy APIs and React server components.

• 42:13Scott Tolinski?

  Yeah.

• 42:13Wes Bos?

  So a bit of a bummer.

• 42:15Scott Tolinski?

  Yeah, bit of a bummer there. Uh, next one, Remix emerges as something new. That happened. Remix is, emerged as something new, whether or not that's being used by anybody, I don't know.

• 42:30Wes Bos?

  It's not out yet.

• 42:31Scott Tolinski?

  It's not out yet. I was not at Remix conf. I don't know the timeline here.

• 42:35Wes Bos?

  Oh no, you should go back and listen to our episode on the Remix.

• 42:40Scott Tolinski?

  I forgot, Wes, stuff enters my brain and just exits. If I'm like, I'm not, I guess I'm not picking up remix. I don't have room for it.

• 42:48Wes Bos?

  Remix announced what it is going to be and it has nothing to do with React anymore. And it is a sort of a full stack entirely JavaScript. It still uses JSX. It's all based on web standards. We guessed it might be a Shopify related product. That is not the case. Uh, we guessed that it might be a Rack server components based headless commerce thing. It's not the case at all. Uh, there's nothing to do with React anymore. And yeah. Next one is React Native will have its time. I, I, React Native is kind of its own thing. Like it gets used a ton where it's needed. But where people don't need to build native apps, they're obviously not going to be using it. So I don't know if we nailed that one either.

• 43:33Scott Tolinski?

  Yeah, I, I think it has. I think React Native continues to get better. Expo continues to get better. Uh, the more I see from React, and one thing React Native, I think just added CSS, better CSS support for a CSS grid or something. They have been, been crushing. Yeah, I think they also felt the hype around links. I follow a number of React Native folks on Twitter and I do see kind of constant hype around various things in the React Native ecosystem.

• 44:00Wes Bos?

  So links, for anyone listening, people are probably trying to Google this. It's L Y N X. This is a React Native competitor from ByteDance, which is the owner of TikTok. Um, and they, and they launched their own version of React Native, which powers a lot of the big, uh, big apps that they have in China.

• 44:17Scott Tolinski?

  Yeah, links is really cool. Interesting. I'll tell you that. Keep your eye on links. Um, next one, Tanstack start and Tanstack will pop. Yes, we nailed this one. Tanstack has got hype around it nonstop. All the Tanstack stuff, I've been seeing major things move to Tanstack. And I, I think that they have a lot of, it, it's funny. I mean, the Tanstack ecosystem overall has, in my mind, legitimized quite a bit, but also

• 44:45Wes Bos?

  Yeah.

• 44:45Scott Tolinski?

  grown quite a bit and then.

• 44:47Wes Bos?

  They just launched Tanstack AI, which I think is gonna be huge.

• 44:51Scott Tolinski?

  Which we knew about early, by the way.

• 44:53Wes Bos?

  Yes, that's what Tanner told us after the episode we did with him. He told us what it was gonna be. That's pretty cool. So just like a standardized AI SDK that can be used in.

• 45:07Wes Bos?

  JavaScript, PHP, and what else is it? I think Python, which is really interesting. They're going with like every language you can use this SDK in, not just like, Tanzac is known for like, yeah, it works with React, but it also works with Svelte and it also works with Vanilla. But now he's going outside of that and just working with every single language, which I think is the move because then you can, if we standardize on these ideas of like responses and requests and the whole thing is going to be beautifully typed. I'm pretty excited about that.

• 45:41Scott Tolinski?

  Yeah, I'm going to do some tutorial content on this Tanzac AI stuff. Really stoked about it. I had some SvelteKit stuff, so SvelteKit gets more granular data loading. They did.

• 45:52Wes Bos?

  That happened.

• 45:53Scott Tolinski?

  They did not get islands or they did get some kind of hydration control. They didn't get, they didn't get the island stuff, but they did get more granular data loading with remote functions and they're dope. So that is component level data loading, yes. I also wrote local first apps will take off and I do think they have had quite a bit more hype behind them. I don't think it's reached critical mass where people really understand the capabilities of local data caching and how, how great that is. And then, you know, when that happens, everyone's just going to act like it's some brand new thing. But I, I, I think that is still to happen. But um, man, local data has definitely taken off. I think more people know what the word local first is, even if they're using the term incorrectly.

• 46:36Scott Tolinski?

  But I do think most people do understand that local data is a viable strategy. Yeah.

• 46:43Wes Bos?

  For Bun, we had two predictions. We say Bun will keep doing wild but loved non-standard features and they certainly continued that. They, they doubled down on their node compat this year, but they also did a lot of non-standard features, which was they essentially became a VEET competitor and they also implemented their own router. So Bun is an awesome tool, but probably the big one we said here is Bun will launch a platform as a service. So we're like, well, Bun is VC funded. They have to make money at some point. What are they going to do? You know, the, the clear path forward is just like, they're going to release a hosting environment. That did not happen. They got acquired by Claude because Bun is powering like Claude code. Yeah, I got it.

• 47:26Wes Bos?

  Sorry, they got acquired by Anthropic and that's a pretty interesting move because.

• 47:33Wes Bos?

  JavaScript as a, almost like a compiled executable. I know it's not actually that and it's much bigger. Last time I said compiled JavaScript, people like lost their minds on me. But being able to take a fast and easy to code core, which is Bun, and put it into products like Claude Code is, is why they've, they've acquired them and done it. So I don't know why they did just use Claude Code to spin up a Bun themselves, you know, it's gonna take all the coding jobs, but I guess they had to pay a whole bunch of money for some of the smartest people in JavaScript to do that.

• 48:11Scott Tolinski?

  I don't think, I don't think AI is able to write Zig, cuz Zig just moved off of GitHub. So now their code isn't getting flirped up automatically, right? Next one, Veet will stay king. Veet remains the dominant bundler server choice. Yes, it is. I still firmly believe that, man, Veet rules, Veet powers so much, and anything that's not next JS is Veet. That's really where it's at. Or I guess Bun, but yeah. Rolldown. Rolldown is a, man, Rolldown was released, but it's not the default yet in Veet.

• 48:47Wes Bos?

  It is. It was the default in seven.

• 48:50Scott Tolinski?

  What?

• 48:50Wes Bos?

  Was it not?

• 48:52Scott Tolinski?

  I don't know. I'm so, there's too many things, Wes.

• 48:56Wes Bos?

  Yeah, I'm pretty sure. I was upgrading something the other day and I went through the breaking changes.

• 49:02Scott Tolinski?

  Rolldown. How to try Rolldown. You have to use Veet npm Rolldown Veet latest to use Rolldown. The current docs say that Veet is planning to integrate Rolldown. To use Rolldown, you have to use Rolldown Veet. It is still considered experimental.

• 49:25Wes Bos?

  Yeah, you're right. 7.0, they rolled it out and you have to opt in. It's 8.0, which is in beta 1 as of today, where it will default to Rolldown Veet. So probably in a couple of months, we'll see that be the default. I've been using it on all of my projects and it's been absolutely awesome. Yeah, it's great.

• 49:46Scott Tolinski?

  Yeah. There's also one thing that we missed on this is Veet Plus.

• 49:51Wes Bos?

  So V plus was, what is it? Give me the rundown.

• 49:54Scott Tolinski?

  Oh, man, I'm gonna be honest. I don't have a good answer to that question.

• 49:59Wes Bos?

  The whole idea behind V+ is not V just not being like the dev tool and bundler and builder that it is right now, but it also is your Linter, your formater, your test runner, UI testing, all of basically absolutely everything. And that's their way to make money, right? They raised a whole bunch of money. Whether that will be the case or not, we will see. But I don't know, part of me is just like, yes, please just give me something that does everything in one. And then the other part of me is just like, no, I want to be able to pick my tools and maintain this sharded JavaScript landscape that I've grown to love. So.

• 50:40Scott Tolinski?

  I want to use V for everything. And I already have only been using V for everything.

• 50:44Wes Bos?

  And as long as it stays amazing, you know, and doesn't and they've proven that to me over, what, eight versions where I've upgraded happily every single time without issue. And as long as it just keeps getting better and I'm not bogged down by anything, then yes, I think that's the move.

• 51:02Scott Tolinski?

  And the V team has always delivered consistently. So, yeah.

• 51:07Wes Bos?

  We said Laravel is going to release a CMS. That did not happen. They said they're going to acquire a or tightly partner with Statomic because at the time, this was during all of the WordPress drama. And everybody was like, well, I'm going to go on a new CMS. All of that WordPress drama and whatever, like not to downplay it, but like, I don't think that a lot of people moved off of it. The people that use WordPress love it and they're still not a very good replacement for what WordPress is, which is a huge ecosystem with lots of plugins and lots of stuff in it. And it is just this whole monster of its own that I don't know will

• 51:48Wes Bos?

  ever be entirely replaced. There's been bytes taken out of it, you know, you've got like, I think the biggest bytes are like things like Squarespace and Webflow and whatever. They've taken bytes out of that, but it's still so huge.

• 52:02Scott Tolinski?

  I don't think that the majority of WordPress users even know what.

• 52:08Wes Bos?

  Yeah.

• 52:09Scott Tolinski?

  Anything regards to any of the drama even happened or was. So developers, sure, but like the users, no.

• 52:17Wes Bos?

  Yeah, yeah, I agree. That's our predictions tallying it up. I think we got a healthy 87% accuracy. I think we did pretty good on that. What do you think, Scott?

• 52:28Scott Tolinski?

  I think we got 100% accuracy because that's what I choose to believe. That's my reality. Yes.

• 52:33Wes Bos?

  Let us know down in the comments what you think we hit and what we didn't. And of course, we will see you one week from today on our episode talking about our 2026 predictions.

• 52:44Scott Tolinski?

  Yeah. Do you want to do a sick pick before we get out of here?

• 52:47Wes Bos?

  Ah, yes. I have a sick pick that I just remembered the other day. And this is not a very good winter pick, but I don't care. It's, this is something I went to your house and I slept in your guest room and you had a woo-woo fan.

• 53:00Scott Tolinski?

  Yeah, the woo.

• 53:01Wes Bos?

  And it's this fan that goes doo, doo, doo, doo. It's a fan that goes on two axes. And it's tiny and it's nice and quiet and it has my favorite feature error, which is you can turn the freaking blue LEDs off while you're sleeping. So we got one of the little ones and then we got another one that's on like a pedestal and they're so compact. But they still, they put out, man. They put out and it's like the best fan I've ever had and I've been so happy with it. So next year, once you're getting a little toasty and you're like, we need a new fan, go to Costco or whatever and grab the woo-woo fan. They're unbelievable.

• 53:39Scott Tolinski?

  And I'm a, I'm a fan noise kind of guy, so I like a little fan on at all times in the, when I'm, especially when I'm going to sleep.

• 53:46Wes Bos?

  Yeah, me too. Yeah. I, I have like a little USB sound machine that I travel with because I just, I don't like when it's dead quiet. I like a little bit of

• 53:57Scott Tolinski?

  Yes.

• 53:58Wes Bos?

  On there.

• 53:59Scott Tolinski?

  Yeah, same. I'm going to stick pick a little UV black light. It's like a little, almost like a little flashlight, black light. I got it. I got it from

• 54:07Wes Bos?

  Why do you hold it? Like you're a cop.

• 54:09Scott Tolinski?

  Yeah, that's actually a good question.

• 54:12Scott Tolinski?

  That is how I hold it when I use it though. Yeah.

• 54:14Wes Bos?

  Yeah.

• 54:15Scott Tolinski?

  No, I, I've been using it actually, uh, well, I've been using it to clean, clean like in the kitchen or something like that. I'm, I'm like, oh man, you see everything with this. I actually got it for my skin, uh, believe it or not, but like.

• 54:27Wes Bos?

  So wait, what does it do?

• 54:29Scott Tolinski?

  It's basically a really high powered black light.

• 54:32Wes Bos?

  And you see what?

• 54:34Scott Tolinski?

  You see every little crumb ever. You can find all kinds of stuff. I lost a pill last night and I was like, I know it was here. And then I was like, oh, let me bust out the black light. I turned it on and that pill just blew, blew like bright white. It was like, I found it instantly and it's so good for finding little stuff like that. Or like our daughter had drawn on the carpet with like some kind of highlighter or something and we could barely see it. I turn on that, that black light and all of a sudden it's like right there. Now we can clean it better. Like it is, I've been finding so many little use cases for this thing. And it's nine bucks, this little like black light flashlight. I've been using it to all, do all kinds of just like cleaning around the house or whatever.

• 55:15Scott Tolinski?

  Uh, or like when I'm, you know, cleaning the kitchen at night, I'm like, I'm not like a germaphobe or a clean freak or something, but I turned on, I was just like, oh, there's all these crumbs here that I missed or whatever, that you're just not, not seeing otherwise. So, uh, it, it, it's funny. I got it for a completely unrelated use case and now I'm just using it for all kinds of stuff. So.

• 55:34Wes Bos?

  Wow. Terrifying.

• 55:37Scott Tolinski?

  Terrifying. It's not terrifying. Also, uh, when you pointed at the, the glow in the dark syntax sticker.

• 55:44Wes Bos?

  Oh, yeah.

• 55:45Scott Tolinski?

  Instantly turns neon green. It's pretty sick. So.

• 55:50Wes Bos?

  Awesome.

• 55:51Scott Tolinski?

  Yeah. So that's it for our predictions. Let us know how you did on your predictions for this year, whatever you thought was going to happen. Let us know what's something that you thought was going to happen this year and didn't happen. Uh, because that's what we're interested in and leave your predictions for the next year as well, because we're about to hit you up next week with what we think is going to happen in 2026.

• 56:13Wes Bos?

  Be ready.

• 56:14Scott Tolinski?

  Peace.