989: State of JS 2025

Scott and Wes dig into the latest State of JS survey results, breaking down which JavaScript libraries, frameworks, and tools are rising, falling, or holding steady in the ever-shifting JS ecosystem. From front-end frameworks and meta-framework pain points to JavaScript runtimes, hosting services, and the growing role of AI tools in developer workflows, this one’s packed with takes, tier lists, and plenty of opinions. Show Notes 00:00 Welcome to Syntax! 01:06 JavaScript Features, not overly interesting. 02:15 JavaScript Libraries popularity and usage over time. 07:52 Library Tier List. 10:55 Library Ratios Over Time. 13:09 Other Front-End Frameworks. 15:24 Meta-framework Ratios Over Time. 19:34 Meta-Framework Pain Points. 21:57 Backend Frameworks. npm Trends express-vs-hono. 25:14 LLM Stack Suggestions. 27:54 Brought to you by Sentry.io. 30:37 Testing Frameworks. 33:15 Libraries Other Tools. 37:20 Utilities. npm Trends biome-vs-oxlint 40:53 JavaScript Runtimes. 45:04 Hosting Services. 51:39 AI Tools. 54:16 AI Code Generation. 55:04 Awards. 01:00:19 Sick Picks & Shameless Plugs. Sick Picks Scott: Anker MagSafe Charger Stand Wes: Battery-powered Heat Gun Shameless Plugs Scott: Syntax on YouTube 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:00Scott Tolinski?

  The State of JS survey just dropped in February of 2026 and there's some interesting stuff about libraries and tools and all of the things that we're using every single day in our code. And today, we're going to be breaking down what's interesting about the State of JS 2025. My name is Scott. I'm a developer from Denver. With me as always is Wes Boss. What's up Wes?

• 0:24Wes Bos?

  Man, I love doing these because it's such a good read on like where devs are at, you know, what tools are they using, what frameworks are they using, what's popping? Because it's, it's, it's one thing to like, listen to like the hype circles of web development that you and I perpetuate, but it's another thing to actually like, look at the raw data of like, like what are people actually using and what are people enjoying? What are people not like using? What, what has popped in the last year or so of, and there's so much good stuff here. So I'm excited to get in.

• 0:57Scott Tolinski?

  Yeah, me too.

• 1:06Scott Tolinski?

  Where do you want to kick this off? Do we want to start on the libraries? There's the, the whole section on here for JavaScript features. As you mentioned, when we were talking about this pre-show, it's gotten kind of less interesting. Like, okay, we're still talking about knowledge coalescing. Like, okay, we've been talking about that for years. It's been, it's been in JavaScript forever, you know?

• 1:27Wes Bos?

  JavaScript had like, I don't know, probably six or seven years of like major API improvements. And, and the actual like, the language itself is starting to get pretty good. And like, we certainly have had lots, lots of new things, you know, lots of new methods added to it. There's all these like immutable methods added to arrays. But simply just like looking at the stats of these features, it seems like People are not as, as like dialed in on them as I think people are a bit more distracted by all the AI stuff going on right now. But that said, the, the libraries, the tooling, the bundlers, um, resources, all of those things that people are using, those have quite a bit.

• 2:09Wes Bos?

  They're not as stagnant as, as the actual language features. And I think there's a lot more interesting stuff in that. So we're going to start into, just go straight into the library stuff and then we'll get into all the build and bundling tools.

• 2:21Scott Tolinski?

  Yeah. And, and so this is the change in, the changed popularity over time where there's a graph here. For people who are listening on audio, we will describe everything, but it's either way, it's whether you have used it or have not used it. Whether you have negative opinions or positive opinions on it. Right? And the most interesting thing about this chart is that so many of these libraries share this same backwards C shape. It looks like it is a backwards C where they start in, you know, people, less people have used them. More people have used them. So it goes up a little bit and people like it. And then over time, more people have used it, or just over time, people hate it more and more and more.

• 3:06Scott Tolinski?

  So it goes further and further to the left, forming this backward C. And if you look, just about everything kind of follows that same shape, whether that's express, uh, react. And some of them to a much different degree, like web packs is crazy. Web packs is like way far to the, uh, negative opinions and have used territory. But what I think is interesting is the ones that don't follow the same shape. Uh, particularly down here, solid. Now solid is still pretty low in terms of the have used. But solids makes like, kind of like an S, whereas people are using it. And I think the sentiment I've reached is that people are coming back to it.

• 3:49Scott Tolinski?

  And generally, like we, we had that episode about Svelte recently and one of the comments was like, so it's getting close to being like solid. It's like trying to catch up to solid now. And I think solid does have a general sentiment of being a solid choice, right? Like a, a.

• 4:08Wes Bos?

  Yeah.

• 4:08Scott Tolinski?

  And I, I, I don't mean to be a dad joke about that, but I do think that it is an interesting use case for where like, I think people are seeing that it is definitely a good choice and solve some of their React issues without being a completely different beast like something

• 4:24Wes Bos?

  Yeah, you can move to it pretty quickly. Um, I feel like the people that use Solid are generally a little bit, a little bit more advanced.

• 4:32Scott Tolinski?

  Yes.

• 4:32Wes Bos?

  And care about the, the nitty gritty, you know, right?

• 4:36Scott Tolinski?

  They have taste.

• 4:37Wes Bos?

  Most people will just kind of like default to writing React. Um, and then once you, you either get really good at React or you, you kind of look for something else. And that's kind of where you start dipping into, to View and Svelte and whatnot. But like, I feel like the, the folks that pick up Solid are, are pretty dialed in on this type of thing and they get it.

• 4:56Scott Tolinski?

  Yeah. Other ones that share a similar kind of S shape, but more higher use territories. Vtest for one. I think Vtest is still on the way up. People are realizing it's so fast and wonderful. And if you're using Veet, Vtest just makes sense. Playwright is one of these things that I think people were paying attention to, and then maybe over swung on it a little bit. And then now with AI, people are back to using and enjoying Playwright because it's doing a lot of nice automation for them. Another one I noticed in here is Veet in general has a much larger version of this massive S shape. So what's so interesting about this is that this does typically follow a number of standard shapes. It's like the backward C where something gets popular

• 5:40Scott Tolinski?

  and then everybody hates it. Uh, but then what I don't understand is why so many of them have the same S shape where they're, they're really, uh, have positive opinions, slightly negative the previous year, and then positive the, the year before that. And then like the long tail of what would be the boomerang. It's almost like the boomerang is starting to happen and then it corrected itself back to an S. This like backward C is happening and it pulls it back. But Veet, oh my gosh, Veet is the most popular, most used tool on the planet. And I don't feel like that should be any surprise, folks. That is. My personal experience, that's the way it goes.

• 6:22Wes Bos?

  The one interesting one that popped out to me here is the angular. What it does is it, it kind of had like a, this survey has been around so long that they're, they're almost at 10 years now, right? At 2016, the data goes back and it started at, I haven't used, but not a lot of people had used it, but they're very positive about it. And then it kind of slowly moved towards being more used and negative opinions. But then 2023 got positive again, you know, swiped right back.

• 6:54Scott Tolinski?

  And then 2024 got more positive and then 2025 got less. I, I don't know what to make. I'd be curious about this angular chart if it went all the way back to 2013, where you could see like the true angular boom, because people who started after like post react, don't really understand that like everything, everyone was picking up was either

• 7:14Wes Bos?

  Everything.

• 7:14Scott Tolinski?

  Angular or backbone, but it was like almost angular. Like I remember so many jobs. That was like the big thing. And then there's something like Mocha here, which is just like inconsistent. It's like a straight line to the left from positive to negative, doesn't even get higher or lower. It's just gets worse reviews over time. So I thought this was interesting, specifically just because of the, the patterns you see in the shapes of things, that they do form this backwards C shape, and then some of them form an S shape. And the only ones that really buck that trend, it's like the angular and Gatsby is kind of crazy.

• 7:50Wes Bos?

  Yeah.

• 7:50Scott Tolinski?

  Very interesting stuff.

• 7:52Wes Bos?

  Really quickly, the library tier list, if you scroll down to that, they have the S, A, B and C tier. And I don't know if there's a whole lot surprising me here, right? Like V, Hono, playwright, Astro, Bun in the S tier.

• 8:07Scott Tolinski?

  I'm surprised about Astro being in S tier, not because Astro is bad, but because I often hear people say, I tried to use Astro and maybe it like didn't fit my use case. But in my experience, I really like Astro. So, but I am surprised that general sentiment is that it's so high.

• 8:24Wes Bos?

  I think it's the people that use Astro absolutely love it. Um, and then I just think not enough people are using Astro for, for the rest of the stuff. Cause if you're looking at what all of your possible options are out there, especially now that a lot of the frameworks have, have this whole idea of like islands and whatnot.

• 8:44Scott Tolinski?

  Yeah.

• 8:46Scott Tolinski?

  I think tier list, tier list that's interesting here is that next JS is in the C tier, which is the lowest tier. That's where I would personally put it, but like, I'm also a hater. So like, I'm surprised to see this is so low when you look at like what it's next to. It's next to Gatsby, like who's using Gatsby still? Selenium, who's using Selenium? Webpack, like Mocha, Cypress? I'm surprised Cypress is that low. It is kind of like a unique thing, but I guess most people have like jumped to Playwright as being the thing.

• 9:22Wes Bos?

  Yeah. Well, if you just think about, like, if you look at this list and you ask people like, what was the most painful part of your career? And they're probably are gonna go back to like flaky Mocha tests, these annoying Cypress tests, you know, like oh Angular 1, Angular is in the C tier as well, you know, Webpack config's just constantly like breaking and not working. Gatsby, it Gatsby has a crazy like fall from grace story. And I think it's just as people's sites got too big. That's what happened to mine, right? It just came from this beautiful static site build to like a huge pain to actually deploy. But

• 10:03Wes Bos?

  Next as well is just is such a divisive framework. And, and also I think a lot of people who don't like React are like, they just like point at Next JS and say, wrecked bad, you know, like Scott over here.

• 10:16Scott Tolinski?

  React, React has 72% in the favorability score where Next JS has 55%. So it's not just React bad. Also like-

• 10:27Wes Bos?

  I would put myself in that category as well. So that makes sense.

• 10:31Scott Tolinski?

  I actually wrote my own bespoke React framework instead of picking up Next just because I found it to perform better using React Router and all kinds of stuff. So I had to deal with custom doing hydration stuff. That was a lot of fun. I picked that. I was like, oh, I'd rather hit myself in the foot with a hammer instead of picking this other tool up.

• 10:55Wes Bos?

  All right. Next one we have here is ratios over time. The prize for the largest relative usage increase goes to Vtest and Playwright. So that means like so many people are moving their testing setups over, away from, what was the one before Playwright? Why am I even forgetting this?

• 11:14Scott Tolinski?

  Cyber writes.

• 11:15Wes Bos?

  No, Playwright was a fork of Puppeteer. That's what it was.

• 11:20Scott Tolinski?

  Oh Puppeteer, yes.

• 11:21Wes Bos?

  Yeah. And then in Vtest was like, it's like Mocha compatible, right? But the biggest increases that we have here, if you look at the largest increases and the largest decreases is obviously V went up, what, 6%? ES Build, a 6% increase as well. Vtest, huge increase. Playwright, big increase. NestJS coming in this one. I, I don't know anybody that uses NestJS and probably all the comments are gonna get mad at me. Not to say that they, they don't, people don't use it, but that's a surprising one.

• 11:58Scott Tolinski?

  It's an Angular thing. I think Angular folks use.

• 12:01Wes Bos?

  Oh, you're right. Yeah, you're right. NestJS is very popular Angular community. That's, that's also the thing is that sometimes you just aren't in the, the same circles as these types of thing. And that's why I love the survey. You realize, oh, wow, that's a lot more popular.

• 12:15Scott Tolinski?

  Oh, yeah. I'm in a bubble for sure. And this is in usage, mind you, because this is just largest increase or decrease in usage. If we look at like awareness or interest, these things like really changed substantially. So as far as usage goes, the largest decrease in these, it's, it's mostly just ones that haven't increased. It's like, there's not like a huge downturn.

• 12:39Wes Bos?

  Nothing has like tanked here. So I don't think there's anything all that interesting there.

• 12:44Scott Tolinski?

  Yeah. Positivity, I think, is an interesting one. Especially if we looked at that, that previous chart where it shows over time, there's that, that C-shaped curve. You kind of see that exact same shape in some of these where it's like, instead of being, it looks more like a rainbow where, you know, over time, they, these things just get less and less popular or less and less positive sentiment there.

• 13:09Scott Tolinski?

  One thing I think is interesting here is always diving into the other front-end frameworks, because you know, there's the big boys, there's the ones that everybody knows about. Interestingly enough, 163 people put Astro and other front-end frameworks. I don't think that really counts. To me, that's like more of a meta framework. But we do have 49 respondents who voted for Ember here. Though the one I think is the most interesting on this list is Ripple. Ripple being a new one that is not quite really out yet. You can use this thing and I've been kind of keeping up with this.

• 13:45Wes Bos?

  Oh. I thought Ripple was, you know what Ripple was? And I've been ignoring it all this time. Ripple was like a BlackBerry tool to test like BlackBerry apps locally. That's why I've been ignoring it all the time. This is ripple dot dash ts.com. What is this? A TypeScript UI framework?

• 14:05Scott Tolinski?

  Yeah, Ripple is, it's inspired by, it's entirely unique thing. It is inspired by Svelte, Solid and React. They have an interesting syntax. You'll, you'll recognize some of this as being like, it does feel like Svelte mixed with React. If somebody was like, let me take some of this stuff, like the way that state is being done. It's not being done through, you know, runes, but there is a track function. And that's, you're saying, all right, we're tracking this value. And then there's derived values. There's like some symbols because this is a compiled language. But then in terms of like how you're authoring components, you're exporting a component function kind of. So it functions, it's like, it's its own syntax.

• 14:49Scott Tolinski?

  And, and so therefore it solves some of the issues of Svelte, like defining multiple components per file and using them like functions. And then it also solves some of the things of React, like it has by default, scoped styling. It's interesting syntax. It's an interesting language. It's still very fresh, but I'm in their Discord. I've been checking this out. I haven't gotten to use it just yet, but it does feel like there's a number of things that are nice about it. So coming in on the chart for probably the very first time with 34 respondents. And I think that the people behind it are bright. So interesting to see that show up.

• 15:24Wes Bos?

  Um, next one is meta framework ratios over time. So this one is. Pretty clear that NextJS is is still top dog here. In fact, their usage percentage went up 4%. And if you look at their interest or satisfaction, they all went down, which is is kind of interesting. Maybe it's a lot of people just vibe coding stuff and it uses NextJS by default.

• 15:48Scott Tolinski?

  So if we look at usage, Astro's usage has shot up from 2021, started at number seven, has gotten all the way up to number two, number two, number two. You remember Austin Powers, Astro number two. And then if you look at awareness, Astro's still pretty low. So for usage being at number two and awareness is number four, people are like, as they're becoming aware of Astro, are really liking it. Interest is number one. Satisfaction for Astro is number one. Knocking off top dog Svelte Kit, my, my boy, look at how they massacred my boy here. Astro has taken down Svelte Kit. Svelte Kit's now number two.

• 16:28Scott Tolinski?

  And then appreciation, this is interesting. I don't, what is appreciation is the gap between interest and satisfaction. So Astro's appreciation has gone down, which is interesting. It's down to number nine. So people aren't appreciating Astro, the gap between interest. So positive sentiment among people who have heard of it and satisfaction, positive sentiment amongst people who've used it.

• 16:57Wes Bos?

  Interesting.

• 16:58Scott Tolinski?

  And then positivity Astro, number one, all the way down from number four in 2021 up to number one.

• 17:07Wes Bos?

  What's really interesting to me here is that Tanzact Start is not on this list at all. Now granted, they, they took this survey probably as Tanzact Start was just in in beta. But if you scroll down to other meta frameworks, like what else are people using? 50% of the people that wrote something in were, were using Tanzact Start, which is what 235 respondents? And that's, that's quite a bit out of, I think 11,000 people took, took it. So Tanzact Start popping, absolutely popping. And then right below that is Tanzact Router as well. Like a lot of people are simply just, the core of Tanzact Start is it's, it's a router, right?

• 17:49Wes Bos?

  So that most people are simply just using the Tanzact Router as their own framework.

• 17:55Scott Tolinski?

  Can I give a shout out to my 13 respondents who put in meteor here? Shout out to those folks.

• 18:00Wes Bos?

  Oh, man.

• 18:02Scott Tolinski?

  Vike, V I K E. Never heard of this. Vike?

• 18:07Wes Bos?

  I'm pretty sure we had this conversation last year when we did this, this episode. Composable framework to build advanced applications with blazing fast, quick start, next generation.

• 18:19Wes Bos?

  Your stack, your choice.

• 18:21Scott Tolinski?

  They nailed all the words, blazing fast, next generation, DX, unprecedented flexibility. It looks like you, you bring your own stuff. You, you can choose your front end framework or your backend framework, it looks like.

• 18:37Wes Bos?

  Oh, it's a next gen, next alternative. Vike, getting in there. What else? Expo 11D, 11D, 4% lower. I think the, we've said this for a couple of years now, but the, the static site, like the entire website being a static site generator seems to have, have like fully gone away. And then that's not to say that like your, your site should not have static pages. I, I cache most of my stuff and, or pre-render it out as static pages. But just like buying into something where the entire thing is static. And then you realize I see a little bit of something that's not static.

• 19:18Wes Bos?

  You know, I need it to be a little bit more flexible. And then you realize, ah, I probably shouldn't have done this whole thing as static.

• 19:25Scott Tolinski?

  I just need a little bit of dynamic.

• 19:27Wes Bos?

  A little bit of dynamicism, yes.

• 19:29Scott Tolinski?

  Dynamicism, yes. A little bit of that. Let's talk, I just want to hit real quick, the meta framework pain point. And the highest pain point for people is excessive complexity, which like, yeah, excessive complexity. You know, the things that we're doing, I think. There's too many times where we're having to do the same exact thing over and over again. Things feel boilerplatey when like, man, I, I, I think that simplicity is a, a thing we'll continue to see with. With new frameworks, either frameworks doing more for you or because what like right now, these meta frameworks,

• 20:11Scott Tolinski?

  they, you still need to bring so much stuff to have them be like fully usable.

• 20:16Wes Bos?

  Yeah.

• 20:17Scott Tolinski?

  And then you have to wire that up together and it all feels like complex. So I'm sure we'll. Yeah, we'll see something there.

• 20:24Wes Bos?

  I, I think a lot of the complaints over excessive complexity have to do with individual component, like caching and in updating individual things. Because like, in my opinion, one of the best things about React server components in, in NextJS is the ability to fetch data in the component, be able to use React suspense. Um, now you can use the same thing in, in Svelte land as well, asynchronous Svelte. I think that those are fantastic because if you have one thing on your site where it might take a little bit longer or you want to like not cache the entire page, um, but you want to just cache like one piece of it.

• 21:08Wes Bos?

  For, for example, like I have a footer on my website where the, the, the data in the footer is live. And I want that to continually be updated, maybe every so often. But like the blog post itself doesn't need to be re-rendered every single time. And there's, there's other parts, right? It doesn't make sense to cache at a page level. And the, all of this stuff around React suspense and caching and being able to stream from the server to the client. That stuff is both fantastic, but also really hard to wrap your head around and, and figure out how to do it right. So I bet a lot of that complexity is, I bet a lot of that 14% is, is those people.

• 21:51Scott Tolinski?

  Yeah, yeah. Very interesting stuff in here. Do people have pain points? Yeah, for sure. Okay, so let's look at, you wanted to look at backend frameworks next. Backend frameworks are interesting because, well, a lot of us are using full stack or meta frameworks now. So the folks who are running just straight up backend frameworks, it does seem like, well, not that it does seem like. It seems like by this chart, Express is still the top dog.

• 22:19Wes Bos?

  By far, like.

• 22:21Scott Tolinski?

  By far.

• 22:22Wes Bos?

  Eighty percent, Nest thirty-two percent. Yeah. Express is such a weird one where, and like I have, I had this myself as well, where it like, it's just not worth. You have such a huge app, not necessarily worth, but it's such a big job to move off of the like connect handlers. And especially when you have your auth and everything just wound into the, that is middleware. It's such a big job to move that into the next generation, which is like, like web request, web response, which everything else uses now, right? Thankfully, I just moved mine off of Express and it's, it's, it's not like, oh, that's so much better.

• 23:06Wes Bos?

  You know, that's the other thing as well. It's like, oh, that's, that's nice that it's all on like a standard web, web request, web response.

• 23:13Scott Tolinski?

  Yeah.

• 23:14Wes Bos?

  And I think that's why Express is just so big, you know, like there's, it's not worth people's time to, to move off of it.

• 23:21Scott Tolinski?

  But I do have, I have noticed personally, um, some AI defaulting to Express.

• 23:29Wes Bos?

  Oh, yeah.

• 23:31Scott Tolinski?

  And it like drives me nuts. I, I was doing something and then I see it's like setting up an Express endpoint. And we're, I'm, I'm in the middle of a Svelte kit site. I have my agents tuned. It knows it's a Svelte kit site. And it's, I'm like, why the F are you doing an Express route? It's like, well, we needed a route for the web, the, the API. It's like. Brother, you have the whole API system baked into the app like, why you setting up a separate express server? I would never ask you to do that. Hanno showing up for the first time in 15%. I would love to see next year Hanno shooting up and express shooting down personally.

• 24:09Wes Bos?

  Yeah, I, yeah, I, so I linked up this express versus Hanno and you can kind of see every single NPM package right now is seeing like double numbers going up right now. Everything is just increasing an insane amount and that's simply just because there's a lot more people coding right now and there's a lot more agents just spinning stuff up and people are just making projects left and right. So like the, the fact that both numbers are going up, I think is, is kind of a moot point because, but you can see that, I don't know, Hanno's, Hanno's is biting the heels of that. And also Hanno is used in a lot of, of the meta frameworks. Even if you don't know that you're using Hanno, it's often, it's either Nitro or Hanno. Those are the two

• 24:54Wes Bos?

  like little web servers that are sitting behind a lot of these frameworks that are being built.

• 25:00Scott Tolinski?

  Yeah. Yeah, it's interesting. Um, yeah, it, there, there is that weird thing now we're experiencing where it's like whatever AI is suggesting is just getting shoehorned into apps.

• 25:15Wes Bos?

  Did you see the amplifying.ai? They had this, um, they had this like stats on what Claude code picks. So what they did is they took a whole bunch of different code examples, right? They had like a React spa, they had a backend app, they had, I think they had a Python app and they had a next JS app. And then they asked it several questions of like, um, what should I use for styling? What should I use for components? Where should I host this? What should I use for error monitoring? And they tracked what Claude code gave them, um, from the different models. And it's significantly different between the latest Opus update and, and the ones that were,

• 26:00Wes Bos?

  what, Sonnet 4.5 versus Opus 4.5? Like express just wiped off the map.

• 26:07Scott Tolinski?

  Really?

• 26:08Wes Bos?

  In the latest one, um, Prisma to drizzle was nuts. Like it was recommending Prisma. Let's see.

• 26:15Wes Bos?

  If you scroll down to where it says where models disagree.

• 26:19Scott Tolinski?

  Hold on one second. Sorry for the interruption, folks. I had a salad delivery.

• 26:23Wes Bos?

  Ooh.

• 26:25Scott Tolinski?

  Homemade non-brand. Got some, I got all kinds of stuff in here. My life is the best. Shout out to Courtney.

• 26:32Wes Bos?

  Yeah. So, cool. Look at this. They asked, like, what ORM should I be using? Sonnet 4.5 was Prisma 79% of the time. Opus 4.5 was Drizzle 60% of the time. And then Opus 4.6, Drizzle 100% of the time. So like, it's clear that they are training these things. E- either they're, they're taking the like, the feedback as to like, when they suggested something and then they, they trained the model on it. Be like, oh, people didn't want this. Or they're simply just like, I often wonder if they're just writing these things in.

• 27:06Scott Tolinski?

  I know. Yeah.

• 27:07Wes Bos?

  Straight into it. Cause they're, they certainly did that for getting rid of the purple, you know? In these models, they had to beat the purple out of, out of these models and it's, the purple is almost entirely gone. It's been replaced with like, uh, model space fonts and, and putting circles around it or border, borders around everything. But that was unreal that this is like, there's like a Claude code stack now where it just chooses all of the, the entire stack for you.

• 27:34Scott Tolinski?

  This is fascinating. We'll link this up so people can check this thing out. Uh, like authentication, custom DIY. Like we're better off on this because I always do, I, I use better off for everything.

• 27:45Wes Bos?

  Yeah.

• 27:46Scott Tolinski?

  I, I do wonder, yeah, how much of this is just from the training verse? Like, uh, how are they steering this if at all?

• 27:52Wes Bos?

  Uh, yeah.

• 27:53Scott Tolinski?

  Really fascinating stuff, but I gotta say, shout out to, uh, Sentry, number one in observability. It's picked the most amount of times and I gotta say for good reason because it's excellent. So check it out, sentry.io forward slash syntax. Sign up to use the coupon code TASTY TREAT, all lowercase, all one, get two months for free. I gotta say, man, Wes, speaking of observability, I've been observing my agents. So I put in Sentry has AI monitoring and I've rigged up my agents here. And so like, let me show you my, my open code. I wrote an open code extension to track my agent usage in Sentry. And so it like tells you which session specifically it is working with.

• 28:37Scott Tolinski?

  It tells you the models, it talks about tool calls, it shows you your tool calls, the average speed and time of the different models. You can filter everything by all this, your requests of different types. You can get the errors coming in from the LLMs and everything in here too. So if you're doing any kind of agent work, whether that is in within your app or in your process, you can actually use Sentry's AI monitoring to do that for you.

• 29:05Wes Bos?

  That absolutely rips. So cool.

• 29:08Scott Tolinski?

  Yeah, I'm currently working on.

• 29:11Wes Bos?

  What's your most common tool call?

• 29:15Scott Tolinski?

  My most common tool call, let's see, in the, we'll do in the last 90 days. My most common tool call is read.

• 29:26Wes Bos?

  Read.

• 29:29Wes Bos?

  And bash, can you, does it, does it break out bash any, any further than that?

• 29:36Scott Tolinski?

  Oh, it does. Yes.

• 29:39Wes Bos?

  Man.

• 29:39Scott Tolinski?

  I need to get more into this data because there's so much data in here. Like yes, Svelte auto fixer called 248 times, task, skill, web fetch, edit. Yeah, it's, it's interesting stuff. And again, I'm, I'm just really, you can see only like a week or two into getting this data. And then now I'm wiring up Pi because man, I'm building a whole dang Pi orchestration setup, Wes. Like of course, and. I gotta have some observability into that. What's it doing?

• 30:10Wes Bos?

  Yeah.

• 30:11Scott Tolinski?

  Yeah.

• 30:11Wes Bos?

  That's good. Yeah, also, like, you know where your money's going, right? If your tokens are being wasted on specific tool calls, you might not necessarily know, oh, man, I spent 300 bucks on like, the React docs being sent with every call.

• 30:29Scott Tolinski?

  Exactly. I think that's the thing I'm most excited about with this is like, really having a handle on optimizing process. You know me.

• 30:37Wes Bos?

  All right, back to state of JS. Let's talk about testing frameworks and kind of what's being used right now. So if we go down to, we go to testing tools over time, and then filter for the rank, just to see what's being popped up. Jest, again, still number one. These tools that are so big, sometimes you think, oh, everybody's using Vtest or whatever, but these big tools take a long time to dethrone. But Vtest coming in at number three. Storybook still coming in at number two as well, which is impressive. And playwright coming up. So that, the whole story of the state of JS is Vtest and playwright are just absolutely climbing. Everybody's using that lately.

• 31:23Scott Tolinski?

  Yeah. Yeah, wow, those are just the big climbs for playwright. Big climbs for Vtest. I think Vtest is still going to keep climbing because you still have a lot of folks who aren't even on V, which, like, I'm sorry, because it's just so wonderful. Yeah, I find this to be really interesting. Bun Test showing up in here as well. Yeah, really interesting stuff.

• 31:45Wes Bos?

  I don't even think you, you don't even need to be on V to make Vtest work.

• 31:50Scott Tolinski?

  Is that true?

• 31:51Wes Bos?

  Yeah, because like, like, most people have like some expect or like Mocha, like, you have some sort of unit tests and...

• 32:01Wes Bos?

  In many cases, you can simply just swap these things over, right? You're using Jest or whatever. You can just swap over the packages and they will simply just work. And I think a lot of the pain people have with Jest and whatever is that it still needs common JS and you're compiling your code so that it will run. And now you're testing it against like this weird compiled stage, which is not the code that's running in production. And that's a bit of a pain. So seeing people move to Vtest, which is it's testing it as your code is running.

• 32:37Wes Bos?

  Not as it's running, but it's testing it as if it were bundled for production. And then also playwright, whereas you're literally just testing it in the browser. Your integration testing, I think people's tests are getting in a much better shape. And honestly, I feel that as well. The between those two tools and using AI to help you write tests. I feel like the pain of testing is like a thousand times less.

• 33:02Scott Tolinski?

  Yeah. And if we look at the pain points, number one being blocking, but performance being number three, which I think those folks who have listed performance could give Vtest a try. So other tools here, these are just general libraries. We have ZOD up top here. A shocking amount of people still listing LowDash, bro. 4,000 people, LowDash. LowDash, I'm surprised underscore isn't on here.

• 33:33Wes Bos?

  Hold on. If we, it is, it's number 12. Still 7% of people using underscore. And I wonder if this is just like, yeah, I've heard of that. I used that at one point and then I'm going to put a check on there. But like, what's more interesting is which ones have gone up or down, right? Like ZOD, massive 12% spike in the last, in the last year. Everybody is realizing, man, I need. Validation and schema for absolutely everything. I think like, once everybody sort of got in, like, or was TypeScript pilled for a couple of years,

• 34:13Wes Bos?

  they're realizing, mm, okay, I understand that everything is fully typed and validated. And what else can be fully typed and validated? And that's when you get Zod pilled. Loadash, mindless.

• 34:26Scott Tolinski?

  Yeah. You know what I find interesting here is that in a bubble, bubble moment here, effect, only 48 respondents responded with effect. And all you hear about is effect, effect, effect on Twitter. And like, nobody's putting effect down here. Also, archetype, folks, 48 on archetype. Type is sick. Y'all have to get on archetype. If you like Zod, you'll like archetype and Valibot. Yeah.

• 34:52Wes Bos?

  Yeah, before, that's the other thing about these things is people don't necessarily know what they don't know. That's why, like, Moment JS has not been a good choice for what, five years?

• 35:06Scott Tolinski?

  Yeah, no kidding.

• 35:07Wes Bos?

  And it's number four. And then like, date functions, number three, it's, that's still a good choice. But soon, Temporal will, um, will probably replace most of that. Loadash, there's some use cases for Loadash here and there, right? Like little utility functions and you're doing, especially you work with a lot of data. I think that there's still use case for Loadash there, but not

• 35:29Scott Tolinski?

  Yeah.

• 35:30Wes Bos?

  this many people, right?

• 35:32Scott Tolinski?

  No.

• 35:32Wes Bos?

  People don't necessarily know the alternatives.

• 35:35Scott Tolinski?

  Yeah, I pick up like just or, but I have JavaScript now. Modern JavaScript has really added.

• 35:40Wes Bos?

  Just writing a function. Yeah, there's, yeah. Modern JavaScript has most of the stuff you need.

• 35:45Scott Tolinski?

  Yeah. Animations and stuff, so Chart JS has a 11-point increase. So Chart JS went from like, not being on here at all. How does that make any sense?

• 35:58Wes Bos?

  I often wonder if some of these libraries are pushing people to vote, because yeah, Chart JS has been around for a long time.

• 36:07Scott Tolinski?

  I made was one of the first tutorial courses I did on Level Up tutorials back in like 2012, 13 was ChartJS. So 3JS, shocking that it's decreased considering 3JS continues to get more impressive every single day. GSAP on here at number five, D3 as number three. Yeah, Motion, formerly Framer Motion on here is number four. Motion's a great library. Surprising that React Spring is still on this list because man, React Spring wasn't even fun to use when it came out. It's been a long time since then.

• 36:44Wes Bos?

  Yeah, I'm glad to see Motion nice and high up here. I wonder if we'll ever see anything different than 3JS, you know, like it just seems like such a powerhouse of a library. There's, is there any alternatives to 3JS?

• 37:00Scott Tolinski?

  It's mostly things built on top of 3JS.

• 37:03Wes Bos?

  Yeah, everything is like built on, like, isn't D3 built on top of 3JS?

• 37:07Scott Tolinski?

  Ah, I don't want to say.

• 37:09Wes Bos?

  Did I get that wrong? Oh, no, I'm, I'm, I'm, I was thinking about something different.

• 37:14Scott Tolinski?

  Yeah, I would say.

• 37:15Wes Bos?

  D3 is a charting library. It's like an SVG library.

• 37:19Scott Tolinski?

  Yeah.

• 37:20Wes Bos?

  All right, if we scroll down and look at utilities, like what people are using, you know, ESLint prettier, looks like 90% people still using ESLint, 86% as prettier. We've seen a lot of like disruption in this space in the last little bit, namely Biome and Oxlent, Oxlent format sort of coming out and providing compatible APIs or, or, or simple, just like, like better APIs that are way faster. But most people still on old faithful ESLint and prettier. But Biome, 16% and then Oxlent, 1%.

• 38:02Wes Bos?

  I would, if you were to tell me like which one is way more popular right now, based on just my like ears on talking to people, I would say Oxlent, but it's Biome is 16 times bigger.

• 38:14Scott Tolinski?

  Yeah, Biome, I think for being first to market in that regard is being the nice alternative there.

• 38:19Wes Bos?

  I like.

• 38:20Scott Tolinski?

  But Biome, yeah, Biome's fine for me. I occasionally see the Biome process on my computer going absolutely ape shit. So I don't know what's going on there. So I personally been looking forward to Oxalent because I do feel like their approach is possibly a bit more, hmm, a bit more possible for consistency amongst moving into different frameworks or HTML or CSS. I see it as being a better long-term option. I would have to imagine by the time that this says JS 2026 here, Oxalent will be way higher than it is in this one because I think people are gonna, I think it's gonna be a thing that people are gonna discover this year.

• 39:04Wes Bos?

  If you're, if you've never heard of it, like OXC is like, it's from the folks at Veet, or I think the like creator of it has joined Void Zero. And that OXC tool is like, it parses and transforms, I was gonna say JavaScript, but it parses and transforms languages, you know, like JavaScript, JSX, JSON, HTML, CSS, view templates, all of that stuff, right? And then when you have a parser and transformer, then you can build things like a linter, like ES Lint, or a formatter, like Pretty or, and those are the two things. And I, I'm kind of glad to see this as well because like, I feel like now that most of

• 39:46Wes Bos?

  the industry has standardized on using Veet, and now everybody's moving to using Veet Test, and then the next thing is that people are going to be using the linter and formatter from that ecosystem. And then what, what's next? A JavaScript framework?

• 40:02Scott Tolinski?

  Yeah. Yeah. And I think the reason why I prefer the OXC is, is like what they exactly say here is Oxalent leverages the native Go port of the TypeScript compiler, providing full TypeScript compatibility. As by contrast, Biome is to implement its own type inference instead of relying on the TypeScript compiler. To me, using the Go port of TypeScript and actually using TypeScript instead of writing your own is like.

• 40:33Scott Tolinski?

  That to me seems a more scalable approach. Also, you can have plugins that are compatible with ES Lint with Ox Lint. So therefore, you know, your ecosystem is is going to be larger. So Ox Lint, to me, very exciting option, something that I'd be definitely poised to see increase in usage. JS runtimes, number one is obviously Node JS. For people out there, I think there's like a weird kind of like Twitter subset of like people who think that like Bun is it for everything. But Node, clearly top dog, top banana still, browser, obviously. But then Bun being number three with a huge increase.

• 41:14Scott Tolinski?

  I have noticed like a lot of AI bros, a lot of like non-developer types, like to talk about Bun as being the thing.

• 41:24Wes Bos?

  I I feel the same way as well, and I love Bun. I've got many videos on Bun. I use it on a lot of my projects. And how obnoxious the Bun guys on Twitter are, when you post anything about Node, it's always just use Bun. Just use Bun. And it seems really big in the like, like student area, you know, vibe code, student area. And it's being, obviously Bun was purchased by Anthropic. Will Bun become like a runtime that, like, obviously it is right now. But like, it seems like the place for Bun is people are sticking it in, obviously Claude Code, right? That's what powers Claude Code.

• 42:08Wes Bos?

  I know Open Code used to use Bun and they swapped it out for Node just because they were having issues with with Windows. But like, maybe that's the the move is that people are, Bun is just going to be this like nucleus engine that they can stick into products that get shipped.

• 42:24Scott Tolinski?

  Yeah, in my experience, I found Bun to be.

• 42:29Scott Tolinski?

  buggy or have issues and like that's just my personal experience but like using the bun adapter for svelte kit like occasionally there's issues there but using bun for open clot won't work so you have to use PNPM or NPM and node like there I have hit a number of like times when bun just doesn't work and I don't know if that's like I'm just hitting weird edges because I'm on you know weird stacks or different things here and there but I don't know if that's that's common but me personally I that's one I don't have any problems with node node to me just works like

• 43:08Wes Bos?

  that that was the other thing and I think that if you if you take a look at Dino Dino's at 11% went down 1% and I don't I think that Dino didn't go down because bun got more popular I think Dino went down simply because people were fine with node node added a lot of the stuff that we wanted right you can yeah you can run typescript in node without a plugin now you can you can load your environmental variables in without a plugin now you know like a lot of the just like little paper cuts of node are solved and a lot of people were saying it's fine it's fast enough it works great for me and I'm happy with it but what else cloufler

• 43:46Wes Bos?

  workers went up 12% that cloufler has had a hell of a year just seeing how many people like almost nobody was using cloufler workers a year ago yeah according to the survey I when was my first cloufler workers video because I feel like I was early six years ago I posted a video here's what cloufler workers do but obviously as cloufler has pushed their workers platform more into like oh this this can be used much more than just like a little middleware now like you could build entire apps on it you got databases and images and they've email now like they're they're almost like the full stack now so a lot more people are opting to just build

• 44:30Wes Bos?

  straight on that and they sorted out their Like running it locally, they have this thing called the, the engine behind Cloudflare Workers is not Node, right? It's Node compatible. It's their own runtime. It's called WorkerD. And for the longest time, still, still have pain points where like it doesn't, it doesn't work exactly how you'd expect it to do locally versus when you deploy it, but they've sorted out a lot of that by allowing you to run WorkerD locally and you can, you hit those issues before you spend three minutes waiting for your build to go through.

• 45:03Scott Tolinski?

  Yeah. Yeah. Interesting stuff. Hosting, I think is interesting. AWS is top dog for cell number two. GitHub Pages is number three. Okay. Netlify number four. Cloudflare number five, but a massive increase. I could imagine Cloudflare becoming an easy

• 45:23Scott Tolinski?

  number three on this by next year with the, I don't know. I'm surprised that Cloudflare is number five, if we're being honest. But

• 45:31Wes Bos?

  Man, I think like the, the people that are using GitHub Pages are doing it because they want somewhere to host their stuff for free, right? And they're, maybe they're sticking it, they're building it every single pull request. You can do that on Cloudflare now for either free or they're like $5 plan will cover a lot of it. If you're like, I want to put this somewhere, but I don't feel like paying for it.

• 45:55Scott Tolinski?

  Yeah.

• 45:56Wes Bos?

  That's a good spot to throw all of your like little one-off projects.

• 46:01Scott Tolinski?

  Totally.

• 46:02Wes Bos?

  Netlify still a huge one. Firebase, this is, this is odd to me. Firebase was 1%, now is 21%?

• 46:11Scott Tolinski?

  Okay. That seems like a weird, something weird in the data, not, not like, I don't even, yeah, I don't know. I don't necessarily understand.

• 46:19Wes Bos?

  I do know that like the AI does pick Firebase quite often for building apps, right? And, and especially if you want to build like some quick little real-time app, Firebase is huge for that. But, and then also you can host it on Firebase. That seems crazy though.

• 46:36Scott Tolinski?

  Interesting. Coolify, number 15 on the list with 6%.

• 46:41Wes Bos?

  Oh, yeah.

• 46:42Scott Tolinski?

  I, I like Coolify. I host a lot of stuff on there.

• 46:45Wes Bos?

  Text editors, 84% on VS Code, 26% on Cursor. Man, that's another one that surprises me. If you were to ask me, You'd ask anybody and they say, "I was on Cursor until January and now I'm, don't even use an editor at all. I just Claude Code prompts in my brains and ship it. Who cares?" But that does not seem to be the case here. It seems like VS Code still massive, massive lead over Cursor.

• 47:15Scott Tolinski?

  And that's my experience. I don't, I've never really found Cursor to be that much beyond VS Code. I know you like it and I know you have good arguments for that. But VS Code has always done the trick for me. The editor I use most these days is Zed, though, and Zed being number five on the list. Zed is not without its issues. You know, there's, it's still very fresh, but if we're talking like performant text editors that are like a GUI-based text editor, it's nice, very nice.

• 47:48Wes Bos?

  I was thinking about using Zed the other day and I thought like, now, now's the time to switch your editor because so much is changing, right? Like, a lot of people don't want to switch their editor because their ESLint and prettier finally works when they hit save and formats and they don't want to fuss with it anymore. They're not going to switch, right? But now, oh, you're gonna, you're switching to Oxlint or Biome? Oh, and you're using Claude Code instead of like GitHub Copilot? Like, there's a lot of like change happening right now in the tools that you use. And when that happens, when you're using a new framework, you're using new formatters, new linters, all that

• 48:28Wes Bos?

  type of stuff, it's not that big of a jump to also switch the editor, right? You gotta get your keyboard shortcuts in place, but it's a good, good use case. Sublime Text, who's still using Sublime Text? 889. 8% of people still using Sublime Text. More people using Sublime Text than WinSurf. That is unreal.

• 48:51Scott Tolinski?

  That's, I mean, I don't, I don't know anybody that uses WinSurf, but... You know, sublime text, sure. I do see people on Reddit being like, it just works for me. It's, you know, it's fine. It's performing, but still, that's like still using text wrangler in 2026.

• 49:06Wes Bos?

  You know, I actually have some insights into the sublime texts. I have a book on sublime text, or I did have a book and a course on sublime text.

• 49:15Scott Tolinski?

  You do?

• 49:16Wes Bos?

  I deprecated it three years ago, put a huge banner. You load the page, there's like a huge overlay. This is out of date, totally deprecated, and people still close that and buy it and don't ask for a refund. And I think it is a lot of Python developers who are in the like education data science space. We're like, that whole like Python data science is like a totally different world than like a web development. So I think that's who's still using this type of stuff. But then what are they doing taking data JS?

• 49:56Scott Tolinski?

  Yeah.

• 49:57Wes Bos?

  I don't know what they're doing.

• 49:58Scott Tolinski?

  I would kill to see, kill to see what's in these other answers down here. Cause there's 179 people who've answered something that's not on here and I'm, I'm just dying to know if anybody put Coda.

• 50:08Wes Bos?

  Well, you can look at the data query builder. I just went through the GraphQL API for state of JS, which is sick that they give you an API. You can pull the data yourself. What have we got here? Quite a few people, eight people using Adam, three people using Android Studio.

• 50:26Scott Tolinski?

  Kev.

• 50:27Wes Bos?

  Lots of like online code sandbox, code spaces, notepad plus plus, come on. Text, who's still using TextMate?

• 50:36Scott Tolinski?

  That's what I'm saying.

• 50:37Wes Bos?

  Three people using TextMate?

• 50:38Scott Tolinski?

  TextMate. Is there anybody put Coda? I gotta know.

• 50:42Wes Bos?

  Trey, nobody put Coda.

• 50:45Scott Tolinski?

  Okay.

• 50:46Wes Bos?

  Quite a few people are saying Trey, Visual Studio, Visual Studio Enterprise, VS Codium. That's like the open source fork of VS Code or the distributed version.

• 50:57Scott Tolinski?

  I'm gonna respond next year to the survey saying I'm using Dreamweaver just to throw off the data.

• 51:01Wes Bos?

  Oh, remember Fleet? We were in the beta test for that.

• 51:05Scott Tolinski?

  Oh, yeah.

• 51:06Wes Bos?

  Fleet was like the VS Code competitor from

• 51:09Scott Tolinski?

  Intelij.

• 51:10Wes Bos?

  WebStorm or Intelij?

• 51:11Scott Tolinski?

  WebStorm, yeah.

• 51:12Wes Bos?

  Yeah, whatever happened to that? Is it people still doing that?

• 51:16Scott Tolinski?

  I asked the folks, uh, cause um, someone that works at on WebStorm was at our syntax meetup in San Francisco.

• 51:23Wes Bos?

  Yeah.

• 51:23Scott Tolinski?

  And I was asking them about that. And the answer was, uh, I think, uh, I think there's some internal confusion over, uh, what was what there, so.

• 51:34Wes Bos?

  It's a nice looking editor, but I ain't got time for that.

• 51:39Scott Tolinski?

  We also have AI tools in here where, uh, a large amount of people, 6,000 people, but ChatGPT is number one. And, uh, and those people just plug it into ChatGPT, I guess. I would, I would recommend that, like, I get, that's a, you know, something that I'll pick up every now and again, but yeah, interesting that it's like the number one.

• 52:01Wes Bos?

  That one is probably number one because like if you're asking what AI tools to use, people are gonna be like ChatGPT and then they insert their like Copilot 51% Claude at 44%. And then it's interesting, this is a huge amount for Claude versus Cursor. It's almost double what Cursor usage is.

• 52:23Scott Tolinski?

  Yeah.

• 52:24Wes Bos?

  And this was before the, the January clodification of everybody.

• 52:30Scott Tolinski?

  The clodification, yes.

• 52:31Wes Bos?

  You know?

• 52:32Scott Tolinski?

  The clodification, the clot, yes.

• 52:37Wes Bos?

  But I would have thought Cursor, Cursor 26%. Again, you asked me, what is the entire world using? Three months ago, I would have said Cursor, yeah.

• 52:47Scott Tolinski?

  No, I wouldn't have, no. I would, I wouldn't have said Cursor. I would have said Copilot, yeah.

• 52:53Wes Bos?

  Yeah, yeah, you're right. That's what, everybody's bagging on Copilot, but they don't realize how much of a. Like the fact that everybody was already using VS Code and GitHub, how much of an advantage they have there?

• 53:07Scott Tolinski?

  Yeah. Meanwhile, Open Code had only 58 respondents at number 14, doesn't even get a point as a point or 0.5, 0.5 percentage points here. Okay, I gotta know. Nearly 1% of the people here put Grok. You're coding with Grok?

• 53:26Wes Bos?

  We did, I, we did our vibe coding video and I used Grok.

• 53:29Scott Tolinski?

  What are you doing?

• 53:30Wes Bos?

  For like three or four months. That's probably why.

• 53:33Scott Tolinski?

  My God, dude. Oh, my God. That's crazy. Um, that's shocking to me.

• 53:42Wes Bos?

  Give me the Grok coding model. I, like, they have it, I guess, but like, where's a Grok CLI?

• 53:48Scott Tolinski?

  But if there's all these other things out there that are so much better, what's possessing you to pick that?

• 53:53Wes Bos?

  It's free. It's because it was free. That's a guarantee. That's why. If you, if you download, install Open Code, it like, for the longest time, it defaulted to Grok because Grok was free.

• 54:03Scott Tolinski?

  Yeah.

• 54:03Wes Bos?

  And then people were, were just using that for everything. And it's, it's no longer free. So we'll see what it is next year. I, we almost need this, like, what AI tools are using? We need this, like, every three weeks.

• 54:14Scott Tolinski?

  Every three weeks, yes, for sure.

• 54:15Wes Bos?

  Yeah. Um, also in like AI code generation, real quick, 0% of people said they are generating 100% of their code with AI, which is, a- and just the spread in general was much more comforting than I would have thought.

• 54:31Scott Tolinski?

  Yes. Yeah. Yeah. The average is 26%. Or no, the average is 29%.

• 54:38Wes Bos?

  29%.

• 54:39Scott Tolinski?

  Yeah, 29%. 10% of folks are not using any AI. So we do get a lot of comments about people who are like, I'll never touch AI for anything.

• 54:47Wes Bos?

  Yeah.

• 54:48Scott Tolinski?

  All right. Well, that is, it's now 10% and it was

• 54:51Wes Bos?

  It was.

• 54:52Scott Tolinski?

  19% last year. Yeah, 20%. So it's gone down by half. So I wouldn't be surprised to see this get cut in half again by next year, folks.

• 55:00Wes Bos?

  Buckle up, folks. Cool.

• 55:02Scott Tolinski?

  Buckle up. Awards. We like to vote on these. Um, the most adopted technology over the past year.

• 55:13Scott Tolinski?

  The most adopted. So like Veet has been like the answer to all of these like every year. So you can't be continually the most adopted, right? I mean, that that I can't continue that. I'm gonna say Vtest.

• 55:26Wes Bos?

  Yeah, I'm gonna say it's probably Vtest and then number two is gonna be Playwright. And then it usually tells you number three as well. Like those, it's so clearly V and Playwright, but like, what would number three be?

• 55:40Scott Tolinski?

  Veet?

• 55:42Wes Bos?

  Probably. Honestly, I think it probably is. All right. Three, two, one. Vtest, number two, Playwright.

• 55:51Scott Tolinski?

  Playwright.

• 55:52Wes Bos?

  Number three, TurboPak.

• 55:54Scott Tolinski?

  Yeah.

• 55:54Wes Bos?

  That actually makes sense, given the dominance that NextJS has and now TurboPak is stable. So that actually makes sense. Nine percent increase. Highest satisfaction.

• 56:06Scott Tolinski?

  Veet.

• 56:07Wes Bos?

  Yeah, probably Veet. This is just the awards go to Veet. All right. Three. Oh, no. Should we guess second and third place? So it's a kind of interesting.

• 56:14Scott Tolinski?

  I already clicked it. Sorry.

• 56:15Wes Bos?

  Okay. Um, well, I haven't looked. I'm gonna, I'm gonna look. Um, Playwright and View.

• 56:23Scott Tolinski?

  Okay, you were wrong on both. Number two, Vtest. Number three, Hano or Hono, whatever, however you say it.

• 56:31Wes Bos?

  I say every Japanese word wrong, so don't trust me.

• 56:34Scott Tolinski?

  But Veet, 98% of its users having a positive opinion about it. Uh, this is the equivalent of, uh, what did Drake say? He said something about, uh, Kendrick just did something. Let's give him a Grammy. Um, I don't like Drake and Kendrick deserves those Grammys. Uh, so Veet, you deserve these Grammys. Uh, I'll just say that.

• 56:53Wes Bos?

  Hano deserves those Grammys. Finally, you know, Hano getting some love over here. I feel like we've been talking about Hano for years and now it's, it's getting some love here. Highest interest, orders of the technology developers are most interested in learning once they are aware of it.

• 57:10Scott Tolinski?

  This is tough. Vtest.

• 57:13Wes Bos?

  Just because.

• 57:16Scott Tolinski?

  I'm gonna say Vtest then Astro then uh Hono.

• 57:21Wes Bos?

  I'm gonna say playwright. It because those were the two big ones, right? I'm gonna say playwright, three, two, one. Vtest. Number two, roll down, makes sense, that's the um engine behind V and then playwright 76%. People are interested in most write-ins.

• 57:40Scott Tolinski?

  Tanstack start.

• 57:43Wes Bos?

  FNM?

• 57:46Wes Bos?

  Tanstack start coming in at number two. Number one is FNM, what's that?

• 57:51Scott Tolinski?

  I know about HNM.

• 57:52Wes Bos?

  Fast node manager, what?

• 57:55Scott Tolinski?

  Yeah, what?

• 57:57Wes Bos?

  Ooh, what do you, what do you use to switch your node versions?

• 58:00Scott Tolinski?

  I use NVM and I hate it.

• 58:02Wes Bos?

  I use N and I love it, except I always forget what the commands are.

• 58:06Scott Tolinski?

  Yeah, my AI is always like, this is a wrong node version. I'm like, you're using Node Verge manager, take care of it. Brother, you can handle it.

• 58:13Wes Bos?

  You gotta do some work, Scott.

• 58:15Scott Tolinski?

  No.

• 58:18Wes Bos?

  Oh, this is cool. I have never had an issue with how fast my switching of node is.

• 58:27Wes Bos?

  But I maybe people who are like, like running tests against multiple versions of node, I could see that.

• 58:33Scott Tolinski?

  That's enough to put it number one in write-ins above Tanstack start?

• 58:37Wes Bos?

  FNM.

• 58:40Wes Bos?

  Interesting.

• 58:40Scott Tolinski?

  FML.

• 58:41Wes Bos?

  Although I do have, every now and then, because I have like weird issues with my node where you switch the NPM version. And it's like, something got wrong, you gotta run this shmod 749 and fix it.

• 58:57Scott Tolinski?

  I don't know why node version managing is horrible for me. So FNM, you're on my radar, starting right now. And the most commented library, which library received the most comments?

• 59:09Wes Bos?

  Library.

• 59:10Scott Tolinski?

  Next JS.

• 59:12Wes Bos?

  Yeah, definitely next jazz and Tanstack start second and Astro third.

• 59:18Scott Tolinski?

  Astro second and then it doesn't matter.

• 59:22Wes Bos?

  Three, two, one. Next year, 69 comments.

• 59:26Scott Tolinski?

  Web pack and react.

• 59:27Wes Bos?

  Uh, web pack and react. Oh, that's true. People love bitching about those things. So that makes sense.

• 59:35Scott Tolinski?

  That's, yeah, this is the most bitched about category here. I will say, Wes, can we just give me an award? I got four of these five correct and the only one I didn't get right was F and M and I got Tanstack start as number two. So.

• 59:51Wes Bos?

  I've got your finger on the pulse there, Scott. I congratulate you.

• 59:56Scott Tolinski?

  Oh, thank you so much. I think I've, yeah, I know. I've done these too many times to just know that the answers to most of them are V and V test. So.

• 1:00:05Wes Bos?

  Well, um, that is stated jazz. Props to Sasha for putting that out again. That's always super fun to go through every single year. I am going to go install F and M.

• 1:00:16Scott Tolinski?

  Yeah. Hey, I'm going to go install F and M too. Do you have any sick picks you'd like to, to get through?

• 1:00:22Wes Bos?

  I got this for Christmas and it's something that I've been wanting forever. And this is a battery powered heat gun. So heat gun I use quite a bit. You know, you got shrink wrap or if you need to heat something up to take like a component off of a board or surprisingly, one thing I use a lot for is my wife comes home shopping and there's stickers on it, absolutely everything. And those stickers always come off brutally, right? You gotta peel it and you gotta get the goo gone. If you just heat them up a little bit, they come off way easier. And I always get annoyed with my heat gun because it's the same thing with the glue gun.

• 1:01:01Wes Bos?

  I got a battery powered glue gun as well. I was like, I'm not near an outlet and I'm doing something where I need to put heat on something. And I was like, you know what? It's, it's not as like, like powerful as like a plugin one and it doesn't run as, as, as long. But I often don't need it to be super hot. I just need to be like good enough and I need to be wireless. So, um, I got this one. It takes the wall batteries. Um, I'll link up the one I actually ended up getting and it works awesome. It surprisingly heats up pretty quickly and it gets. Hotter than I like, probably like 700, 800 degrees, which is very hot.

• 1:01:40Scott Tolinski?

  That is very hot. I'm going to sick pick something that I, Amazon says I've purchased a lot of times. And I've sick picked this before, but it's been a long enough here that I feel like I should, I should mention this thing. Uh, Anker, maker of really nice stuff in general. The Anker Cube is this little cube. It's currently on sale right now. You can get it for 83 bucks. But it charges your AirPods on the side here, or the AirPods go on the side, right top here. It charges your Apple Watch and then it does MagSafe right here. And it just plugs in with a USB C. So it's the three-way charger here.

• 1:02:25Scott Tolinski?

  And man, this is something I just, like, this is a gift I buy for people. Like, I got my dad one for his desk. But the best part about these things is that, like, for travel, it just, it shows up in this little cube. Now you've got a three-way charger that's not some, like, obnoxious crazy shape to fit in your luggage. It packs so nicely because it's this little cube. And since it's just USB C, you can throw your normal, any USB C charger on this bad boy. Uh, big fan of this device.

• 1:02:53Wes Bos?

  And it probably, like, does fast charging, right?

• 1:02:56Scott Tolinski?

  Yeah.

• 1:02:56Wes Bos?

  Like, it charges your phone fast. That's so key. When you're traveling, you got like the, the mobile SIM, you know, you had an eSIM. And my battery drains when I've got the, the eSIM going in when I'm, you're, obviously you've got maps and you're, you're out and about, taking photos. Um, and nothing is more important than you're back at the hotel for 45 minutes. You know, you gotta, you gotta charge your phone as, as fast as possible. It's so nice having a, you just slap it on there. You charge your watch. That's a key for, uh, for traveling.

• 1:03:29Scott Tolinski?

  Yeah. Yeah. Love this thing. So I, I've purchased a number of them for, for various folks in my life. But shout out to Anker for making a cool little cube. Wes, do you have anything else for us? Any parting thoughts? Any final words?

• 1:03:42Wes Bos?

  That's it. Thanks so much for tuning in. Leave us below what your favorite thing of the year was. And we'll catch you in the next one. Subscribe, like, comment, do everything. Peace.

• 1:03:53Scott Tolinski?

  Peace.