2024: A Year in Review

Welcome to Syntax. This is our 2024, a year in review. We're going to take a look back at what happened this year in in web development in general, what did we do as a as a podcast, and most importantly, we're going through our predictions. So every Yarn, at the beginning of the year, we predict what will happen, and, we'll take a look at if we got some of those very, very wrong. And some of them, we're we're bang on, so I'm excited to to get into that. My name is Wes. I'm a developer from Canada. With me JS always is Scott. How are you doing, Scott? Oh, hey, man. I'm doing good.

Right Node, at our house, this is the 2nd week in in less than a month where we have some kind of stomach bug going around. 1st, it was 1 kid, and we all kind of came out unscathed, if not for a little, like, sore tummies and stuff. But, man, we got a whole another A whole rock. Different stomach bug.

You know, probably came from a birthday party or something we took our kids to. And it is it is tough. It is tough to have to wake up to clean up after, like, kids Vercel several nights. It is rough. It is rough. So, yeah, I'm feeling a little bit. I'm feeling that that aspect of it. But, hey, I'm here. I'm doing good. We recently got back from a couple of conferences, and I'm going to Disney soon. So it's just like I'm feeling in a good place, good way to cap off the end of the year. Right? How are you feeling?

I'm feeling great. I'm, I'm excited for 2025 and, excited for all the stuff we have planned. Actually, maybe let's talk about that right then and there JS we have some changes coming to the Syntax lineup. Not the lineup. The line. This is the TypeScript content we are creating. So we are going to go down from 3 podcasts a week down to 2 a week, and the podcasts are going to be like, traditionally, what we do is we do a hasty on Monday, a tasty on Wednesday, and a guest on Friday. What we're going to do now is simply make the podcast as long as it needs to be for the content and not stick to a specific type on every single day.

So you can look forward to that, and then that's gonna free us up to do a little bit more video. So we've got all kinds of ideas of of YouTube stuff that we can do. Right, Scott? Pretty excited about all of it, and, we're gonna start cooking on all of those things. And that should be on Friday. Right?

Yes. So, you know, even give some background on this JS Yeah. You know, when the podcast first started out, we just did 1 episode a week, and then we did 2 episodes a week, and then we brought on the interview episodes. And we largely had that that format for I don't I mean, it took a little while for us, like, maybe, like, 2 or 3 years before we added interview episodes is even a thing. Yeah. Right? It still feels brand new to me.

And it did feel like we're always kind of, like, having to fit the content into the format. Right? We had the format. Let's, figure out how we can fit it in the format. And sometimes that worked out no problem. I think for the most part, it did. But we heard, especially in the survey that we put out, that maybe there's too much. We're putting out too much, and maybe sometimes the topic could be covered in less time or we need more time on something. So we decided to give ourselves more freedom and flexibility here so that on Monday and Wednesday, right, the topics that we find to be interesting, we can spend as much time as we want to on those topics that we find interesting. And that doesn't mean the interview episodes that we typically did will be going away.

We'll still be doing interviews, but we won't have to do interviews just to do interviews. We will do interviews with the the people who have the most interesting and exciting things to tell ESLint that way, you know, it doesn't feel like a book tour or we're just having the same guests on that everybody else is having. We wanna really make sure that the what we're producing comes 1st and foremost. So yes. And also to head off any anybody who might say that centuries behind this, this is purely Wes and I's decision here. So, you know, we we don't even have any century handlers on the in the the podcast team anymore. We are It's just us. It's just us. It's just us going wild. But, like, I think, also,

with that is that there's a lot of like, some of the feedback we had is we went a little too video heavy a couple months ago. We sent since peeled that back Wes, like, if you're listening on audio, you don't wanna have to see the video. Yeah. But there are other topics that make so much more sense to show on a video because you can be showing code samples and and whatnot. So it's it's nice to say and and, like, we we were talking about a couple weeks ago. We're like, when we wanna talk about something, we will have the medium for that, whether that's a 15 minute hasty treat or whether that's a 20 minute YouTube video or a full we have to bring somebody on to to talk about it. And I like that freedom of not having to worry about the content type. Yes.

Yeah. It that too in, like, you know, one wanting to show more video, I think both the podcast and the video podcast suffered because we weren't able to show as much video as we wanted to. But then when we were showing, like, we had to always be kinda riding that line. But by saying 2 episodes a week are going to be strictly podcast, although with video. Right? The Friday, whatever we do on Friday, is going to be explicitly a video, segment, something that we can do that makes way more sense for just video. And that way, we won't have to worry about the audio product suffering from using video in that regard. So, if you want to get everything that we're doing, it will be on Spotify, because Spotify shows video, and it will be on YouTube.

So a lot of the stuff YouTube specifically, is gonna be the best place to catch everything.

But, again, your normal podcast player JS gonna get them Monday and Wednesday.

Alright. So let's talk about 2024.

What happened in in the past Yarn. Right? Quite a bit in the web development space. I think probably a big one, is React 19 was released.

We've been sort of waiting for server components for for many, many years, and 2024 was the year React nineteen dropped. Server components are now stable.

The React Compiler came out, which is pretty interesting. I haven't seen, like, a lot of people using it just yet, but it's kinda we have it. TurboPack is is now stable. That's kind of the big things in the React space.

Yeah.

Solid Scott was released, which is the, you know, Solid JS meta framework. So if, folks out there were were using Solid and really wishing there was a more, like, opinionated, full stack framework for Solid, that that was released. Also, Ryan Carniato joined Sanity. So, shout out to Ryan. We gotta get him actually on the show to talk about, Solidline now that we have well, we had access to him before, but, now that he's part of the the Sentry team. We had Tanner on talk about TanStack start. So TanStack start is

Tanner Lindsley who's behind React Query and React location, I believe, is is his router and and behind a whole bunch of the really cool 10stack packages. 10stack queries, obviously, is probably the biggest one. He released a beta just last week of 10stack start, which is the, like, Next JS equivalent.

It's client by default opt in to server, which is the opposite of of Next JS. And, it just seems like a really fresh approach to a framework in in that. Also, like, also along this lines is is Remix is is dead. It's not really dead, but it's, all of the parts of Remix have been moved back into React Router 7, and React Router 7 was was released at the end of November.

So I believe now they they haven't explicitly said it, but the the idea now is is you're not building a Remix app. You're building a React Router app. And, I believe, eventually, Remix will will go away and and not be a thing anymore.

Yeah. It is one of those things I I still don't feel like I under I understand, like, where that's at or what's happening there, but, you know, I think that's a a good explanation.

I'll be I'll be looking forward to even more clarity of what's what's going on. Because I still people talk about, like, Remix. But, like Yeah. Yeah. It's it's kind of an odd one. Like, they didn't even in the announcement

post, they didn't say, like, Remix is dead, but they they did say, like, you should migrate here's how you migrate from Remix to React Router 7. Mhmm.

So it's kind of a bummer because I the name Remix is is sick. I like that a lot. I know. But And the logo. Yeah. Sense that, like, the the router really is the the main part of of your website. Right? Your most websites, you start from a router, and and that's especially Wes we start doing server client stuff, you really have to buy in at a router level. So it makes sense that that's why they've they've brought it back. Yeah. Totally.

And, also, you know, let me just say, back to the tanstack stuff. Man Yeah. Hanging out with Tanner at JS Nation, I know we got to hang hang out with him on stream, and he's such a he's such a dynamic kind of, like, exciting person to talk to about this stuff. But just getting to hang out with Tanner at, JS Nation, maybe really, like I really just hope that stuff succeeds even harder. Because what a cool dude. What a great project. Yeah. Really enjoyed, spending time with him and and getting to know him a little bit more. AI editors really popped. Specifically, Cursor was the the big one that people have, really been latching on to. You know, personally, myself, I I don't use anything other than the cursor anymore, which is you know, it's short term here. It hasn't been that long. But I don't if Versus Node opens by accident, I'm closing it. I'm opening cursor. I I I just really like the way that the UI works. It it feels really good. Yeah. Yeah. I often see people, especially on Reddit, be like, I don't get why people like cursor. Is it really just is it really, like, just people hyping it up who get paid to say it and stuff like that? I don't get paid to say Cursor JS great. I never even I don't even have any contact with the Cursor team, but I use it and I love it. And it for me, it just it it fits that workflow just a little bit better than any other tool currently. I'm actually really excited to see, given that cursor has shaken things up so much, I'm excited to see, like, what comes next from that.

Totally. Because, like, we did see at GitHub Vercel, Copilot released a lot of the features, not all of them. Yep. We're still waiting for a couple. But and then, also, Node released their own fork of Versus Node called WinSurf.

And, it's, again, it's it's gunning for the same area. But Codium has also been in that space of, like, context providing context to the model for quite a while, and it's interesting that they have their own editor. So quite a bit popping. You're starting to see these, like, dudes on Twitter who say they built entire apps with it, which I'm not buying because every time you see one of these guys, they've got a course to sell you and an empty GitHub.

So

I I don't know if I buy that just yet, but, it's a exciting time for sure. Yeah. An exciting time. And in general, with AI tools Vercel, it it's a scary time, I think, as well.

But I think right right now, we're at the position where you can use these things and feel very productive or take care of a lot of stuff, without having some sort of crisis of, am I, just a robot writing out code that a robot could do better or something? There's also Vite 6 was released very recently. It was released in November. I believe November 26th.

And, Today, as of recording this, it was released like a couple hours ago? Yeah. The not just a good memory. I, I'm actually terrible with dates and time. So, the fact that I know that is because it came out today. Vite 6. Man, Vite is one of those projects that I'm so happy to see continue to grow, continue to evolve.

And now it's part of void 0, which is I I believe the funding platform. We're gonna have Evan Yuan to talk about this to to really get a handle on exactly what void 0 is. But, Vite 6, stoked to see that these changes are are still advancing. And, one thing I'm really excited about is the eventual edition of roll down, which is the next gen version of ES build and roll up. So combining the functionality of those 2, having one thing to do all of your builds and having it be as fast as ES build or faster. Who knows? I don't even know.

But roll down. A really cool project, and I'm it's one of those ones that, like, very, very, very excited for it. And, hopefully, we'll get to try it next year.

Yeah. The the thing with with Vite is that in development, they use Wes build. And then Wes they build your app, they use roll up.

And it's always been 2 different ones, and I guess there's some inconsistencies.

Although, I've I've never hit any myself, thankfully.

I'm I'm sure it's harder on them to maintain both of those. Right? Oh, I guarantee. Yeah. You have to make 2 things, do the exact same thing in development and in in build. That's that's tricky. So, yeah, Avenue has this company called VoidZero, which has raised some money. And I think the idea with the company is they build this amazing open source software, and then they'll eventually have some things that you can buy from them. And I bet it's gonna be similar to the Turbo Pack Wes you can cache your builds and share them between Mhmm. Both build servers as well as as developers' machines.

Yes.

I would love all of that stuff. Faster, better, faster, smaller, all that stuff.

One cool thing that that really, you know, came up about at the end of the year was kind of the reemergence of Blue Sky. You know, we did an episode on Blue Sky when it first dropped. We talked a little bit about this AT protocol.

And yeah, at the time, I just didn't necessarily it felt like it felt like blockchain. It felt like, Web 3. And I didn't necessarily believe that it was anything super interesting.

But the more and more that, you know, Blue Sky has evolved here, now the platform is smooth as hell to use. So using Blue Sky is no longer, like, a worse version of Twitter. For the most part, it's a better version of of Twitter in many regards with the exception of maybe, like, video. Right? I think there's some things here or there that that Twitter still does better, but, Blue Sky There's a lot of features, but it's it's it's an exciting change in the web development community Yeah. Not because Hey. It works better. I'm gonna that's what I mean. Like, as a the I have so many weird popping bugs with Twitter. Yeah. Tweets popping in here or there or refresh things not happening or showing me a bunch of dog shit. Yeah. I I think, overall, it works better as an app whether or not the features are good. Good app. Yeah. It's very impressive. It's also React Native. It's pretty cool. But, like, all of that aside and

also, like, political Bos aside as Wes, because, like, I I was kind of shocked that like, I was really excited that the web development community was moving there just because I like that there JS multiple places for community to be. And then it turned into this weird, like, political thing in the states.

I don't give a single crap about any of that stuff. All I care about is is there a spot where we can talk to other web developers that feels really good? And I I still love Twitter. I'm still there, but I'm I'm excited that there's like, I grew up on forums, and there was many places for people to be. And this is starting to feel like a a pretty good spot, for web developers, which is exciting, when when there's more Sanity. Because, like, I feel like a lot of developers were kinda burned out on Twitter because they they're not able to share what they're excited about because you have to play this algorithm game. And that's exhausting when you just wanna say, I made this cool thing and for people to see it. And and when you say you love Twitter, I'm gonna Sanity Scott not for any specific reason other than content and and usability.

I I don't like Twitter. I I really don't like it because, one, it it's the algo is so aggressive in what it shows me that I'm often like I'm not seeing garbage. Anything I wanna see. I'm seeing a lot of rage bait. I'm seeing a lot of people fighting. And I I try to mute any of that stuff and only follow, engage with people I actually wanna hear from. But at the end of the day, I'm still not seeing the content from people who I I follow JS much as I am on on Blue Sky, which is why it feels better. I'm not playing the Algo games. I'm not, I'm not working really hard on something, sending it out, and having 2 people see it because the Algo didn't pick it up. Right? So oh, yeah. There's a lot of lot of weird little things about it. But either way, I think the protocol behind this is something that is the most interesting, thing Wes it it's kind of like I I can't wait to talk to Dan. We're gonna have Dan Abramov on the show and really dive into, this. But it does feel very RSS adjacent in terms of the feed exists, and Blue Sky is just an interface for the feed, whether that is in the Blue Sky app or you you're working with the feed in other ways. And I think that's the most exciting part about it in general.

Yeah. I think it's really neat that you can, like, you can literally fork the entire Blue Sky app and and connect it up, and you can you can build your own client.

You can host your own version of something, which I think us web developers really like the fact that you can host your own data.

Yeah. Will will any of us do it? I highly doubt it. Half the people on Blue Sky haven't even assigned a domain name to their handle yet. They're just using the built in one. But

Most people didn't edit their Myspace profiles either, but a handful of people did. And it got them really interested in, learning HTML and CSS. So I think that's, like, kind of the you know, back in the earlier days of Twitter Wes the API was still open, you didn't have to bankrupt you to use it. The the people who were doing some of the coolest stuff with the Twitter API. Come out of it. And and that's the stuff that I miss. I miss the most. Yeah. Yeah. There's so many cool little projects. Like, I just I even just

built, a little count on my stream deck that will show Nice.

Like and when a new follower comes in. And yeah. It's just being able to hack on that kind of stuff is really exciting. And it's funny because a year and a half ago, I did a whole bunch of examples.

And now when Blue Sky popped again, all of those examples were were getting getting popular, and people are sending poll requests in. And a lot of people ran the code without seeing what it did, so they I had a couple Bos in there that would auto reply.

And, so every now and then, I get people reply to me with their bots that they obviously were just randomly running code from a stranger on the Internet.

Okay. Back to web stuff. Exciting stuff. Yeah. Yeah. That is web stuff, though. Like, that's that's our community, man. And Totally. It's it's really cool. And, again, I'm kinda bummed that it's been hijacked as a political thing, which is not I I honestly don't think that that's that's where that discussion needs to be. It's just all about, like, where we hang out. Yeah. Totally. But CSS CSS, so many crazy things came to CSS or are coming, in in the next year. CSS has landed late 2023, so we started to like, 2024 was, like, probably the year we see people using. CSS has, relative color is starting to, be well supported pnpm over.

And then all the stuff around just like starting style, allow discrete, calc size, where I think it's like a lot of, like, JavaScript replacements.

Right? Like, you did you did a talk on all this stuff? I did a talk on all this stuff. And, man, it's it's not even just the it's not even, like, the stuff that we can use today. It's the stuff that, came on to the radar that is now, like, going to be here soon. Right? Yeah. The starting style animating, when things enter and leave the DOM, the the parent selector. I know that came at the very end of last year, but it also, I think, came to all the browsers more recently.

And invokers, which is a newer API we've talked about a couple of times, but that's replacing JavaScript to invoke things like opening a Node or starting and stopping a audio player, invokers being done with just purely HTML.

So, like, Wes, we're not only getting better JavaScript tools, which, you know, we're JavaScript dudes. We love JavaScript tools. What's that? We're Costco guys. We're JavaScript guys. Wes like JavaScript tools. Yeah. Guys. Yeah. It is a wild it's a wild world. There there is a world. Podcast talking about the Costco guys. I got some thoughts. I know. I I know. I know. I I do too. Did you watch them on the late night show? I believe they're on, like, Jimmy Fallon, the same thing. I saw some clips, though. Oh, you should watch it. It's I'm a little worried for the humanity that that's what is the most popular thing. But, also, like, go get it. Like Yeah. Don't get it. Probably getting loaded right now. Yeah. Yeah. That and the haktoow girl, you're like, alright. It's it's not for me, but, you know, I I can't really hate on it too much. You're you're, you know, you're making your 15 minutes worth it. So so, yeah, all this cool stuff, man, it is just replacing JavaScript. And the more that we can replace JavaScript, the better, more accessible by default. And just smaller applications will be able to ship with the tools we know and love, and, therefore, we won't have to reach for, building native apps.

We can use the the web, which, hey. We love the web. Exactly.

Big fan of all of that.

What did we do? We'd hit up tons of events this year. Right? We were at React Miami. We did a Syntax Live there up in March.

You were at JS Nation in Amsterdam. When was that? June, July?

Yeah. Sometime around then. It was, Yeah. I think it was June or July. I'd have to look at my calendar. I'm bad with dates. But it was in the the first little bit of the year, at least the first half of the year. And, man, JS Nation Amsterdam, one of the coolest conferences I've ever been to. There was, like, 60 plus people. I I did not real I'm so good about saying yes to things and then seeing the size of the stage and then been like, oh, what? Like, I walked into JS Nation Amsterdam, and I swear the seats just kept going and going and going. It looked like infinity to a point. Yeah. They have a screen halfway down.

A massive screen too. Like a Half yeah. Like, the the screen itself is is probably, like, 40 feet tall.

Most beautiful LED pixel panels, you can like, the blacks are just black, and then they have, like, a 2nd projector screen, like, halfway down because it's so far back.

And, I don't I don't know that there's conferences that big in the States aside from maybe GitHub Vercel, but, like, I don't know that there's a web development conference

that huge Wow. In in North America. It was so cool, and it was such a cool experience for me. But Vercel, conference was really great. A lot of amazing speakers.

You got to hang with a lot of cool people. And it's a 3 day thing where they had a React Summit Amsterdam, and they also had a, I believe, like, a a CSS and web conference that, like, Node was speaking and a bunch of really cool people. So it was just, like, the coolest people popping in and out, an amazing audience. Scott to meet a lot of great people.

And Wes also did, more recently, JS Nation US and React Summit US where I was emceeing React Summit, which, man, MCing was a lot of fun. I was I was I'll be I'll be honest. I was nervous to MC. I've never done MCing in any regard before, and it's it's kinda like just doing this podcast. You just show up and and you get to either read from your notes or talk or whatever. I get to interview, Kent c. Dodds, Eddie Asmani, Shruti Kapoor, and, Theo Brown. Like, I got to just be on stage and talk to those folks, and, man, what a cool experience. You got to talk at in a planetarium.

Yeah. The again, speaking of wild screens, like, it was a it was in a planetarium, and they projected our, our slides, like, on this, like, curved thing. I had to zoom my slides out just so that it wasn't like, I I was watching, and I felt that the slides were too big.

Like, you had to crane your neck up and down just to read it. So I zoomed my slides out so you can see them without moving your neck, and it was it was a really cool conference. Yeah. I had a great time. And then we also did

while we were there in New York, we did Terminal Feud, which was Family Feud. And by the time you're listening to this, it will be available

on YouTube to watch, I believe. And, man I think it's going on Prime's YouTube channel, the Primogen, so check that out. That was hilarious.

Yeah. Let me tell you. I am much worse at coming up with stuff on the fly than you would think I would be, which you know what? There there was when we were doing that speed round, we were doing a speed round where Wes and I were supposed to be guessing different things that fit a prompt, and we ended up just guessing the same things. But since Wes went first, all of his answers were accepted. But so when they ask me a question, the first thing that pops into my head immediately is like, because Wes had already gotten it. So then my brain goes, oh, no. Oh, no. I gotta think of something else. They're like, npm install blank. Like, fill in the blank. Npm install anything. You're just like, I can't think of anything to npm install. I couldn't think of a single thing. It was like my brain has been wiped completely clear. Like, the only thing I could think of was node. I was like, npm install node. That's what my brain went to, and I was like, I can't say node. That's not that's not, like that's gonna everybody's gonna, like, complete it on me.

Well, I got 2 points from it because 1 the couple of pity people had put in Pnpm. I should not have said PNPM. Oh, yeah. I was thinking about it afterwards. I should've just said Svelte because, you know, that's that's I was up there wearing a Svelte T shirt,

and, you know, it's kind of my identity. But yeah. Yeah. That was fun. We also did, Laravel Terminal did a basketball game. Scott and I, what do you what do you call we didn't call it. We We were doing color commentary.

Oh, commentary? Yeah. Typically, in in commentary, you have a play by play guy or play by play person and a a color person. And you know what, man? Neither of us know basketball, so neither of us could do play by play. So we were both doing color commentary, and it was super fun. I I came with a whole bunch of jokes and used all of them in the 1st 5 minutes and then had to come up with more on the fly. But that was cool. That was a a fun experience.

We had a meetup in San Francisco, and that was really fun. We had couple 100 people come out.

I think I think it was, like, between 2.50 ish or around 250 people. Quite a lot. We had a whole bunch of stickers and swag that we gave away. That was really fun. We had a whole team there, met a bunch of really cool people.

Wes had GitHub Universe. We did a couple podcasts live, from the GitHub Universe floor, which, again, that was a very large conference section. I believe it's 5,000 people or something.

Definitely mind blowing. Yeah. Because we don't get to go to that many events like that. No. And, like, I usually go to more, like,

web development homegrown comps. And, like, this was, like, corporate.

Not that it was bad, but, like, the big companies were there announcing very big things and partnerships and whatnot. Yes. We were there for the all the Versus Node Copilot stuff, which JS really exciting. And we got to talk to Cassidy in our our podcast booth, which was a lot of fun. That That was awesome. Yeah. Yeah. Really cool. I spoke at FITC, which is a Toronto conference. I highly recommend you go if you are like to visit Canada at some point or you're from Canada. FITC is it used to be a Flash conference, like, 15 years ago, but now it's a pretty heavy web development. I talked about all the different JavaScript runtimes. So bun, Deno, Node, and kinda went hard on the, like you don't have to worry too much about these different runtimes. It's because we have standards that will work everywhere.

Yes. Totally.

And we also did a whole bunch of podcast episodes, and not only that, ton of video. I mean, syntax overall, man, we had a a crazy year in terms of, like, growth for us where it it is hard to imagine that at the beginning of the year, we were not on YouTube, and we were not releasing these podcasts as videos. Now we've been doing it it feels like since the job, it it's been going so long, and we hired CJ Reynolds to to do video for us on YouTube. So, man, syntax JS a platform has really grown significantly.

And especially with the push to YouTube, it feels full circle to me. And I know you've been doing YouTube a long time, but I really got my career start on YouTube in 2012.

So for me, I put so much time into YouTube. It feels great to be doing a lot of video and a lot of YouTube.

It just feels it feels like I'm I'm back. I'm back. You're back. Yeah. The OG.

Yep. Alright. Let's get into our predictions.

So every year, we predict what will happen in the next year, and then we followed up at the end of the year. And, we're we're gonna go through and see how right or wrong we were.

So the the first one was, types in JS will have real movement.

Haven't really heard a whole lot of that. That's the proposal is still sort of going through the the process, but I thought we would be a little further ahead on this type of thing.

Not that I'm mad about that because if they are trying to figure out adding types to JavaScript or at least adding the syntax of types to JavaScript, because that's what the proposal currently is. It's not adding types to JavaScript engine. It's just adding it to the syntax so that they can be parsed out. Right? So you can use TypeScript or something similar with the with the syntax. So it's not like the browser will understand the types.

Yes. Well, I I do wanna give us some credit on this one. Node came with type support, as far as being able to

run code with TypeScript in it. So That well, that that's one that's a little later on this list was, Node will introduce TypeScript support via loaders.

Okay. And we didn't nail that as it's not necessarily a loader yet, but that is the idea, and Node did ship TypeScript support. So now you can run Node with .ts files, and it will simply strip them out and and run with you, which is super exciting. To me, that's types in JS having a real moment. That's a moment. Yeah. You're right. That's true. Like, that's that's node recognizing This is the way. This is the way. This is people want this, and probably Deno and Bun have a lot to do with that, yeah, pushing Scott node into features that we want rather than having to cobble it all together.

Totally. Next Node, the temporal API will ship in 1 browser. That one's a big fat x. We, we did not do, we did not get that, which is a problem. Yeah. Safari has,

like, 2 of the features behind a flag. Do they really? And that's it. But, like, not the whole not the whole API, just a couple little parts that have been behind a flag in, I think, in technical preview.

Oh, it looks like the technical preview has instant and duration.

And, Safari looks like it's going to be the 1st to ship temporal. So

hell, yeah, Safari. Cool. It's such a huge, huge spec. I think it's it's a bit daunting to have to implement it because there's so many pieces to it. But, man, once this thing lands, being able to use it I guess we could use it via polyfill Node. But I am. I I'm I'm ready to, like, rewire my brain to think in terms of temporal.

I already did that. Yeah. I I've been using a polyfill for a little bit, which may be dumb or not. But, yeah, I do I do like it, and you will like it too, folks, if you're out there and you're wondering, am I am I going to get that much out of the temporal API? Yes. It it even eliminates the need for me to use a library at all for doing dates and times, and it just keeps working with them way easier.

Perf tooling gets easy for easier for everyone to understand.

I know we got a handful of Perf tools in Century, but I don't know if you could definitively say that Perf tooling has gotten easier for everyone to understand.

You know, the browser kinda hasn't changed in that regard. We still have all of the same tools, which are good. But yeah. Yeah. I don't I don't know that we nailed that one. I think,

if anything, like, we got compiler in React, so that's that's a big win for Perf. Right? Yeah. And then we did get speculation rules as well, or or maybe that's coming, but I don't know that the the tooling around that got any better.

But one Node we did nail, CSS continues to get better where you need less JS. Absolutely nailed that. We just talked about all those CSS features where, you don't need JS for them. Not that you shouldn't not that you should hate JS. It's just like if you don't need to run a bunch of JavaScript and DOM traversal, adding classes, wrapping things, duplicating elements, it's it's really nice to not have to.

Yeah. Yeah. It is. And I think Vercel, I don't I don't know if it's just vibes based, but it does feel like we're getting more and more DOM focused Vercel, whether that is via frameworks or HTML APIs and things like that.

Getting more DOM focused. Getting more HTML focused. Yeah. Web web components. I we didn't have anything in here about web components, but That's surprising. There was opinions on web components this year.

Yeah.

I like them. Yeah. We mentioned Svelte five. Svelte five was released and is very fast. We just recorded an episode. It was released on Wednesday about that.

And, yeah, the code's much smaller, very, very fast, and, that's exciting for everybody.

The year of server in frameworks, I think we we nailed this one, is pretty much every framework has either the ability to do server or you see a lot of stuff being server first, server by default. Right? So Next. Js, oh my gosh. I just clicked on I just clicked on one of the time stamps in the show notes, and it says, Wes Bos, our old, like, intro. It just scared the crap out of me.

Wes Bos.

Oh, that's great.

And and it's funny just, you know, classically, having to be contrarian, I have now moved further and further into the client side now that we have all the server side stuff. So, that's just how it goes. Right? I I think I think, it'll be interesting to see what our predictions are for next year because I I do have some predictions for next year. We had Astros going to have a a good year. I you know, Astros had a a good year, but I don't think anything explicitly.

Like Oh, I think so. I think, let's look at the the NPM stats for Astro. I think Astro popped, man.

Yeah. So Astro pretty much doubled their download numbers in the last calendar year, which is is pretty impressive to me. So I would say that's a that's a pretty good it still JS. If I were to compare it against Svelte, Svelte is still 5, 6 times larger.

It had a good year. Downloads. Yeah. But Selt had a really good year. Astro had a really good year.

So, yeah, I think they did great. Our next one we had here is React Vercel components will become popular.

I think maybe we got this wrong.

Not that server components are bad. I'm I'm very much an an enjoyer of of server components, but I did not see the uptake.

It seems like like last year this time, we're kinda just waiting around, seeing what people think.

And I think we're still in a wait around and see what people think area. Obviously, a lot of people are using them, but I don't I thought the uptake would be a lot more. And even, like like, they're not in React Router, Remix, or TANsec start.

So, really, if you wanna use server components right now, you gotta you're still using Next. Js or one of these, like, new frameworks that are are kinda around them.

Yeah. We also had Remix moves away from page based letters to component letters. Well, they moved away. Yeah. They moved away to, as we already mentioned, to being React Router. But, again, I don't even yeah. That's not on my radar at all at this point. We also had Node will become more ubiquitous.

And, yeah, I think Hono's been been more used. You know? CJ did a a a video on Hono that got a lot of views. So I would imagine that that means that people are interested in picking up a modern express alternative, and Node seems to be the chosen.

Yeah. So Hono went from 36,000 downloads a day at the end of last year to 444,000 downloads. So, like, exploded.

And along with Hono, we're also seeing all of the Un. JS ecosystem, get really popular. It's kinda in the same area of of Hono, which is basically standards based server JavaScript.

And, like, you see, like, a Node equivalents their Hono equivalents called Nitro, but then we also saw Vinci, which is what 10 sec start and sol start are built on top of. So some really exciting times for, like, server standard JavaScript or just standard JavaScript in in general because it doesn't matter a lot of times if it's on the server. Yeah.

Next 1, URL pattern standard.

We will see a route matching proposal move ahead and then link to the URL pattern standard. I have not kept up with this at all.

I have not kept so this the idea here is that the writing patterns for routing, like like you were to do in Deno or Express or or anything like that, that standard is going to become a standard API called the URL pattern API, very similar to how we have the URL and URL search params in JavaScript.

And it is currently still being worked on. It's last updated just a couple of months ago. So It seems like it's in very fleshed out. It's in Chrome. It's been in Chrome since 2021,

but no movement in Safari or Firefox, maybe. Okay. Yeah.

Alright.

Bun releases full Node.

We did not see this. They obviously continue to work on their Node compat, but there still is is quite a bit. In fact, they're part of the Unenv, e u n e n v, and it it actually brought Cloudflare Workers and BUN and Deno all up to to full Node. Js compat. It's essentially just a transpiler plus polyfill for server JavaScript, which is which is pretty exciting.

So we're at a spot now where if you have a Node API, you can pretty much run it in most of these these runtimes either via, like, Deno 2 has full node compat.

I tested it myself. I I converted my whole class course platform to run on Deno, and it it worked or via on end, which will sort of polyfill the parts that are are not quite there yet. Bun is Bun is focused, I think, more on, like, killer features rather than Node compat, which people seem to be liking.

They'll release something that is nonstandard.

And as much as the standards guy in me wants to say, no. Do the standard.

Some of those APIs are pretty sweet, and I would like to also use

them. Yeah. We will also see a new linter or formatter entirely replace.

And the ones we had listed were, you know, OXC, Prettier, Biome. I I I don't think any of that happened. I mean, there are things that people are using. People are using it it is Biome. I was thinking it was called Roam now, but that's the other way around. Roam became Biome. People are using Biome. I'm I it doesn't support all of the things that Prettier supports. And until something supports everything that Prettier supports, I'm not using it. So, yeah, I I don't know. I actually understand the people who can use one of these and not have it. Let's see what it doesn't support right now. Like, warp with everything.

Yeah. I believe it doesn't support, like, HTML or CSS or something. Yeah. The the killer feature is once they can parse HTML,

then they'll be able to format, ESLint, pretty much anything. Right? Like, you can view Svelte, whatever. It does support JSX, JavaScript, TypeScript, and CSS. So for a lot of people Yeah. Their whole stack is covered already, and that was not the case a year ago.

I'm still pretty bullish on on Biome taking, you know, taking over, but I I guess we'll see. Yeah. I gotta have that HTML

support, even markdown support. I wanna have markdown support, YAML support. I I Node to support all of the things I use because if I run into a situation, I hit save, and my stuff doesn't I don't even need linting for all of that. Just formatting. Give me formatting for everything I use, and and I'm I'm okay with that.

We said a new TypeScript type checker. Did we really say that that was gonna happen? I'd I man, sweet summer child if I thought that that would come. No. That's Yeah. That might never come. And I think here here's my thoughts on this. We're never going to have a new TypeScript type checker, but we will have a something that comes after TypeScript eventually. And someone's going to come out with, like, probably the 1 project that you should watch in the space is called Esno.

They are basically taking the, like, TypeScript syntax, but building their own type checker on top of that or not on top of it, but they're building their own TypeScript type checker.

And I bet once that matures, we'll see people being like, alright. Like, TypeScript the good parts. You know? No enums and and whatnot. The the errors are a little bit better, but I don't even Node. That prob we're probably many years away from from that being a reality.

Which feels it feels wild, but at the same time, I get it. You know? Yeah. And If it was easy, it would have happened. Yeah. Yeah. It's it's fine.

And Yeah. Like, I I love TypeScript mean, the, like, the type checker itself, it's almost always fine for my projects. You know? Could be a little bit faster and whatnot, but it's it's not a now that we have, like, just strippers, it doesn't get in the way of your actual development.

Yep. Now that we got strippers Yeah. Lightning CSS pops.

Lightning CSS. Yeah. I, I didn't use lightning CSS anymore, or less. It it pretty much was in the same spot for me as it was when we recorded this episode. Yeah. And that that's not a bad spot. It's just I haven't been using post CSS if we're being entirely honest. I've just been, going straight up CSS mostly.

Yeah. That's like, maybe the the new CSS killer framework is just regular CSS.

Tailwind 4 is is using lightning CSS by default now, so that's probably a a major one for using lightning CSS.

There's something else using Lightning CSS. So Lightning CSS is kind of like a post CSS alternative, and it will parse and transpile your CSS back to stuff that works in in all the browsers.

It's kinda like the the babble story. You know? Like, at at one point, we don't need to transpile our CSS, but other times, you you still need tools that can parse and analyze all of your your CSS, whether that's to do things like prefix or transpile or just to get stats on on what's going on. So the light lightning CSS has gone from a half a 1000000 to 1,600,000.

So it's it more than tripled in its usage. So I would say that's a pretty good pointer to this becoming more popular.

Yeah. Yeah. Definitely.

One of them here is, you'll hear more about RS Pack and Turbo Pack.

I think we nailed that Node. Turbo Pack is now stable.

RS Pack, I just saw a really good talk from the creator, Zach, at the conference a couple weeks ago, and really interesting look at moving Webpack over to to Rust. And then he was also at the end of his talk, he was talking about how, like, even if you don't like Webpack, maybe the internals of RS pnpm could be surfaced in a different way. Right? Like, the the reason we like Vite is because it's so easy to use, and we don't have to write Webpack configs.

So maybe in the next year, we'll start seeing, more tooling around that.

Yes. Vite is not going to release anything big in 2024.

They just released Vite 6, which they said was their biggest release ever. I think that's more from, like, a a code point of view, because from a user, nothing really changed.

But they have teased or or have released their new environments API, which is going to, make doing server stuff and different JavaScript runtime stuff a little bit easier.

Yeah. So there was a release, and they say it's a major release. So Yeah. We can say we failed on that one. Relative color will land in all

browsers. Color mix was canned so that we can just use the relative color syntax, which is simply using HSL RGB, whatever Wes you want, and the from keyword. Yes. Yeah. Relative color. It it actually man. It's in. It it's in ish? Yeah. It's in every browser. It hit Firefox in Node thirty three, which is just a couple weeks ago. Yeah.

And, yeah, it's it's in it's in every browser.

Listen. It's not in Opera completely.

So Opera.

What fort uses? I know. I know. It doesn't support current colors. Me about these can I use

JS every time I post about anything, somebody goes, what about Opera Mobile? And, like, that's coming from a person who's never doesn't understand what Opera Mobile or sorry. Opera Mini actually JS, there are use cases for that. But chances are if somebody's using Opera Mini on your website, you don't need to worry about relative color syntax.

Yeah. No. It's available to 88.8, percent of users, which in my mind is

a a good amount of use. It is an it is an opera. However, you cannot use current color can't use current color. Yeah. Color.

Yeah. Big fan of of relative colors.

At at the very least, just to make a color somewhat transparent, being able to add an alpha value to a color without like, the hex value, you know, you can add the 2 the 7 and 8 hex digits on the end of a hex code to make a color transparent.

I can I can never remember what the common hex values are for 50% transparency?

Yeah. I agree. I, I'm stoked. This is one of my one of the most exciting APIs for me as a CSS guy.

We said the color contrast is going to land in Chrome. That was wrong. It's in no browsers right now. It's in Safari behind a flag, but there is they sort of, like, rolled it back, and they're still trying to figure out what is a good algorithm for color contrast. Because color contrast is a hard thing to to get right, and and you can only math it so much. So they're trying to figure out what that looks like. So that still I'm I'm dying for that to be added, but they're still trying to figure that out.

Yeah. Alright. Next Node is scroll animations landing in 2 browsers. That didn't happen.

Did it? Let me tell you. I think. CSS stuff happens so quickly these days that I I've, like, talked about scroll animations. I've used them so much, and then I don't even know if they landed in 2 browsers at this point. They're in Chrome. They're in Edge. And That doesn't count.

They are in Opera. That doesn't count.

They're probably in Brave.

They're gonna be in They're in Arc? Yeah. Yes. In Arc? No. So they are behind a flag in Firefox, and then they are in Chrome, but no sign of them hitting Safari just yet, which is Safari's been first on a lot of this stuff in CSS, but doesn't seem like, this one. You can polyfill the JavaScript API, though. So that that is something. I mean, that you can get them to work, but you cannot polyfill the CSS API. There was, but it broke.

And it doesn't it doesn't work anymore. I don't know, what happened, but I I looked into it myself for my own website, and I opted just to turn that off

for the browsers that don't support it. Word. Alright. What about the year of CSS discovery? I I don't remember what this is, but I'd have to imagine it means that, like, people warp gonna discover all these cool features about CSS. And I would like to say that that did happen because, hey, I give talks about it. You gave talks about it. We talked about it on this podcast. But more or less, I see people talking about the new CSS features all the time now, and I see people shipping them and using them. So I'm at a point now where I I'll, like, show 1 CSS feature in a video, and almost every video is, oh, what what are you using to get that nesting? Is that Sass? Like, no. We've had nesting for

a long time now, and a lot of people don't know about it. I I think part of that is because so many people are just on Tailwind, and they don't know about it or need it.

But there's there's so many cool things landing in CSS, and I think people are starting to starting to figure that out. Yeah. And I'm excited. I'm excited for next year's year of discovery of CSS because that's how that's how the stuff's going at this point. It is Yeah. Moving, in the best way possible.

Safari will ship 3 missing progressive web app support.

They ship something. In fact, well, they they literally clawed back PWA support in European browsers.

Yeah. And then everybody raise a stank about it. And so they what did they they shipped add to add to doc was was 1. We had Jen Simmons on this year talking about all the new stuff. So the thing about Safari is they're not releasing them as, like, manifest per progressive web app, but they're adding the features into the browser without them being, like, proper, I guess. Like, you can now add to home screen and add to your dock.

You can color specific things. You can take the title bar out.

So I guess there there probably was, I don't know, 3. It's it's hard to say. I should've should've looked it up, but still Safari's a drag in their their heels on a few of these progressive web app things. Yeah. I wonder why. Yeah. Yeah.

We had Firefox usage will continue to slip.

You know what? People talk about using Firefox all the time, but I I just don't see Firefox really coming back to be No. Major major numbers.

Bit of a bummer. I don't I don't think it's if anything, like, I would hope that here here's a a sneak peek of my my guess for next year JS that OpenAI is gonna release a browser.

I unfortunately, it's probably going to be a Chrome Chromium fork, but wouldn't it be cool if OpenAI put their 1,000,000,000 of dollars behind Firefox and, like, started paying people to to work on it, that'd be pretty neat. You know what? There has been a world of Firefox

forks recently.

You know, it it since Yarn announced that, like, their Arc browser is done and it basically you know, the browser the browser company pivoting from shipping a browser to shipping AI, which is ridiculous. But Zen Browser is one that people often recommend. I don't know if you've seen Zen hyphen browser Scott app.

Zen Browser is one that people often recommend, and I gotta say, I don't buy it. I just straight up don't buy it because it it is like a very light skin on top of Firefox.

And it's like, oh, we made it look like Yarn. But what they didn't do is copy any of the features of Arc. Oh. Whether that is like the, the at the launcher or any of, like, you know, if you command t to open a tab and that tab is already open, it doesn't it opens a new one. Right? I use Zen, and I was like, this is Firefox with a couple of extensions added on to it. So anybody out there that's been like Zen is the the perfect, replacement for for Yarn. It is like, not quite. But Yeah. I do think it's interesting that somebody made a fork of Firefox that is seemingly getting some attention.

And, yeah, hopefully hopefully, they add more Arc features to actually make it like Arc beyond a coat of paint.

But, I just Firefox in, in this year, 2024. Yeah. You've already been on Pnpm didn't you? For maybe 6 months Node, and and, like, man, installing Edge is awful. Like, there's, like, AI games added everywhere, all this Bos. You Node? Microsoft Clippy. Pretty sure you have to, like, log in via Excel spreadsheet.

But once you turn all that Microsoft Bos off, the dev tools are the best. They they have people working on it. It's not just Chrome's dev tools. Like, it it is, but they have added some selector performance stuff to it. They added the ability to dock the tabs to the left.

There's, like, 5 or 6 different things in the dev tools along with just the overall look and feel of them that that make it really good.

Yeah. Nice.

Yes. Yeah. I I just can't. I'm sorry. There's there's enough Microsoft y things about the UI that it just drives me nuts. I'm still on Arc. Off. Yeah. I'm I'm right in Arc Arc tool. It, can't be, Until they stop updating it. I know. Yeah. The the sad thing about that is

the Arc failing probably means that no one is ever gonna make a a browser that is, like, for developers anymore. You know? It unfortunately has to be a bunch of AI garbage or, like, coupon clipping or, like, stuff built in that will just regular normie web users are going to want, which I think is why OpenAI is probably gonna

be one of the big players in this space. And it makes sense if you think about it because, I mean, we could talk about this in our predictions. But, like Yeah. We we we've seen the AI kind of take over of the search engine, whether that's perplexity or just the the simple, like, assistant type of searches that you do typically. Like, well, last night, I was playing kids sequence with my daughter, and I didn't know if diagonals counted or not. What did I do? I didn't go to Google. I went to chat g p t. Kids sequence. Can diagonals count? Yes. Diagonals counting. Kids sequence. Done. Alright. I Wes.

In your face, daughter.

Let me tell you. My 5 year old is so good at puzzles and, spatial things. She clearly got my spatial skills, and she destroyed Kourtney in kids sequence a couple times. And she comes in. She's like, I'm gonna beat you. And I was like, oh, you don't even know. I got the same brain as you. And, yeah, I'm like, I'm I can take a 5 year old in sequence.

And we played to a draw. And I was just like an actual stalemate. I'm just like, yeah. This is feels like playing myself here. I love it. That's good. Yeah. We also had paid Yarn features.

Yeah. That was wrong. So if you did near Yarn decided they're shutting down Kind of. Well, kind of. They're making an entire new browser, which is, like, all AI focused.

So the Arc itself is is not going to be a thing for for much longer.

But then we had more XR web experiences, as Apple releases Envision Pro.

You're the one with the the goggles. Did that happen?

You know what? The goggles now, they do have XR WebXR support. So that did ship.

Okay. Whether or not people are shipping XR, you I I've seen some cool things and some cool demos, but nothing practical.

The only thing I I really find to be a practical upgrade in the VR space is now that the VisionPRO has an ultra wide monitor that I can use in my car or outside or whatever. But as far as web stuff goes, I didn't necessarily see anything major there. I do think that will be coming.

Especially, we did see some, like, very glasses based, IR headsets that looked a little ridiculous, but they're coming. And once you have glasses that can do what the VisionPRO can do, then Wes is gonna be all over the place. Right? Your experiences are gonna be placing things in in three d space around you rather than, you know, opening up a window to to browse through a website.

Isn't it funny how, like, technology can be so life changing but will not pick up because they're looks dumb? Oh, yeah. Like, the Segway was like that too. Like, electric bicycles, electric scooters have have literally changed people's lives because they now can have transportation.

It's changed, like, food delivery. Like, it they've had a major impact on the world. But, like, Segway

didn't get any of that because you look like a nerd riding it. It didn't help that they, like, made you wear helmets and everybody is, like, in a cluster of Segways. Like, there's a lot of things. But, you know, those, like, hoverboards, I do feel like that's probably some of the same tech. Right? And, like Yeah. Oh, yeah. All all it took was to make it into an unsafe little, toy device,

for people who My daughter has 1. I, yeah, they're they're they're, like, crazy. They're pretty fun, though. I I took Wes apart because I bought I bought a broken one because just so we could have a second Node. And I was just, like, going through how it all works, and it's amazing that they're able to take the Segway tech and put it onto a board that you can buy on AliExpress for $37.

Yeah. I, I do love the, the onewheel stuff. I I don't have a onewheel, but I think it's so cool. I know I'm going to hurt myself very badly. Everybody hurts themselves on them, and I hurt myself doing anything.

I I fractured my tailbone in the, cleaning the bathtub, so I will I I will hurt myself on a onewheel. That will happen, but I want pnpm anyways.

Yeah.

AI real quick. A couple AI ones. You said AI tooling is gonna pop off. I think that we nailed that one. So v Deno by Vercel got really big. We saw Bolt dot new from the Stackblitz, which has has exploded.

Yeah.

GitHub released their own version of it. What? I totally forget what it was called. Cursor.

No. Not Cursor. What was GitHub's? GitHub Spark is their version of it. So, yeah, we saw a lot of AI tooling. Obviously, Cursor.

We had we didn't say the word Cursor this time last year, and it's it's all you hear right now.

Yes. It didn't I don't yeah. It didn't exist. Right? I mean, that's something we didn't predict that there would be a rethinking of Versus Code. I think either of us would have thought, like, oh, Versus Code is just going to get either an extension or Copilot features. Not Yeah. I wouldn't have called the fork. Fork. Yeah. Would not have called that. Or that a fork of it would have actually taken off because there has been forks in different ways. But, yeah, the fork took off, for sure.

Small models that run-in the browser. I have not used any small models that run-in the browser, but I think you have. Right? Yeah. Yeah. I used a bunch this year. Depth detection, background removal Oh, I did. Yes. Whisper OCR. I used OCR. OCR.

Yeah. Wes transformers JS is is behind a lot of those. It's really exciting that you can run those in in the browser.

But on on the flip Node, also, we saw a lot of not for the smaller stuff. That's good. But for all of the, like, coding AI stuff, almost nobody JS, like, training their own coding models now. They're all using Claude or OpenAI.

Yeah. Which are great.

Yes. Apps get Sherlock by OpenAI.

Yeah.

Yeah. Did that that probably happened at some point. Yeah. No. Definitely. There were Yeah. I mean, you know, earlier in the days of OpenAI stuff, everybody was filling in missing functionality on top of it. And now it's like, oh, yeah. I I think just like Apple, I I think anytime they release anything, it's shutting down a couple of people. So,

yeah. Wes said on prem corporate AI. I don't know. I this could probably happen. I I think probably the closest thing to that is Facebook's llama Node, which you can just download and run yourself along with, like, a lot of models. But, like, the LAMA model is up with stable diffusion or some of the, like, big ones that you can can run yourself that can run with the the big boys Claude and OpenAI.

So

I would give myself a a 2 out of 10 on that one. No. Give give be be, graceful with yourself. You you get a 10 out of 10 on all of them. Awesome. Because I can definitely, wiggle myself into a position to say all of these succeeded in Node regard. We can make up something.

But Node. As as usual, we did a great job predicting the the last year and I can't wait for our prediction episode that will be released. And I do want to say this because we didn't say this off the jump when we said that we're gonna be changing the format. We're actually gonna be taking a, small holiday break. So the today is the 23rd. We will not be releasing an episode on on Christmas or that Friday or that next Monday, and we will be back with a potluck on January 1st for you. And then the next episode is going to be our year prediction. So, January 6th, I'm super excited. One of my favorite episodes of the year because I get to feel smart without actually having to have the consequences for it until next year. Right? So, yeah, that's what we got. Do you have anything else, Wes? Anything you wanna say before the end of the year here? It was a great year. Thanks to everybody who who made it

such a great Yarn. And lots of really neat stuff came out. Lots of really cool open source projects.

Still love web development. Looking forward to another year of it.

Yes. Likewise. And I I do wanna say in addition to that, thank you specifically to everybody who came to either one of our our meetups, either 1 this year or before or anybody who filled out our survey, who has left a comment, been a part of this community.

That survey really, was was really great for us, and, I'm sure we'll be doing more in the future if you wanna tell us how you feel. But tell us how you feel anyways. We love to hear, hear from you. Send your feedback in any means

possible at any time because we love it. Yes. And and, specifically,

Wes likes it more than I when you're you're very critical.

Yeah.

Wes when we were doing the the survey form, Wes was like, can you write on there to be very harsh and very critical? And I was just like, no. Don't do that.

I don't want to hear that.

No. I like it when people give it to me straight because it's like, you might be wrong, but, also, there's probably some some good stuff in there. I like it when people protect my fragile feelings here. So,

let's ESLint before we head out for the year, let's get into sick picks and shameless plugs.

I have a a sick pick for us today.

My son, just like most other 7 year olds, is extremely into Pokemon, very, very into Pokemon. Specifically, he's been, like, playing the card game. He's in, like, a Pokemon card game club after school and stuff.

And as a parent, as somebody who I I I had Pokemon when I was in middle school, but maybe not the card game. Right? I had the first I had the blue cartridge.

I never picked up the card game ever once. And so he's playing the card game, and I'm like, you know what? It would be really great if I could, play this with him, and I don't wanna, you know, figure out the rules. But there is an app now on Bos and Android.

I don't know. My camera will not. Either way, it's called Pokemon Pokemon TCGP, Pokemon the Yarn game pocket.

And it is the card game. And I you open little packs of cards, and, actually, Wes, you might enjoy some, UI elements on this. I don't know if I can even show this because I I would enjoy Pokemon. I say, I tell you I will not enjoy Pokemon.

No. But the UI and and I won't even, like, I can't even I can't show you this because my camera won't focus on it. But either way, the UI has these little packs of cards, and it's 3 d. You can spin it around. You swipe your finger over the top to open it, and the cards come out. And if if the card is if the pack is backwards, the cards come out backwards, and you have to flip them around to see what they are. It is a delightful thing, but it taught me how to play the card game. And now I can play the card game with my son, which has been a lot of fun. I feel like I'm connecting with him on that Vercel, and, he's very excited to open the virtual packs of cards in the games. Just don't fall for the microtransaction trap, and it's all good.

You know what? I bet I met a guy at the conference, and I was like, where do you work? He's like, I work at Pokemon. No way. I was like, oh, man. That's amazing. He's like, yeah. He's like, I learned from your courses, and now I have a job at Pokemon. And I was like, did you have to use the Pokemon API in your, Oh, yeah. Because that API is is used in everything. He's like, it's funny because all the jobs I didn't get, we use the Pokemon API as my, like, take home.

That's awesome.

So maybe he he worked on that. I'm I'm curious what the tech is

behind that. That's pretty cool. I applied for a company that did Pokemon's website in Flash back in 2008, And I was very distressed when I didn't get the job because it was in Tokyo, and that would have been awesome. That would have been cool.

I'm going to sick pick something for my kids as well, and that is just buying a huge ass bag of Croc charms.

My kids are crazy about Croc charms, and they, like, they sell them at the store for a dollar or whatever. But I was like, you know what? We gotta like like, I know how to source stuff. So I I think I bought, like, 500 or something like that. And they just lay them out on the carpet, and they go through them and and pick their favorite ones. And then we use them as, like, if you do your chores, you get to have a croc charm, and then they bring them to Scott, and they give them to their friends, or they trade them, and, like, it's just currency.

So, yeah, I I forget who it was that told me that, like, yeah, Pokemon cards for, like, doing your chores or whatever. Our house JS Croc charms, and I'm I said that. Yeah. Yeah? Okay. There you go. It works well. Do you and I think we should get syntax Croc charms because they're Yes. They're very fun. Let's do it. Alright. I'll do it. Yes. Nobody else out there. Nobody steal that. We're doing that. Syntax. Yeah. Yeah. If you see somebody doing that them right now Call them out. Web development croc terms, maybe. Yes. Get a CRT up in there.

Cool. Well, check us out on YouTube, Syntax FM on YouTube. We'll release everything. We will catch you so much more there in the next Yarn. And, thank you so much for hanging with us this year. It's been awesome.

Peace.