Open Models Replace Big AI

That so often I would post something to Stack Overflow, and I would get, why are you doing it this way? And and sometimes that's the that's frustrating, but sometimes that's the best thing. I don't know that, like, the quick fix from a lot of these AI agents is often, let's take a step back and and redo this. Often, the fix is like, alright. Well, here here's how you can fix it, the hole that you're in. So that kind of makes me bummed because, like, you people are not going through that. Like, what's the best way to approach it? And and, coincidentally, that's one of the highest skills you can have right now JS, like, not just writing the sheer code, but how do you tackle these problems?

Welcome to Syntax. Today, we are talking about all kinds of stuff. Wes has been gone for two weeks, and now he is back, and the entire web world has forever changed.

Everything is different. Holy smokes.

Yes. Everything is different, folks. We're gonna be talking about all kinds of stuff in this episode. View three point six has entered release candidate, and there's something called alien signals. That sounds cool as hell. We, we're gonna be talking about how you can stay on top of every single browser update that happens. We're gonna be talking about an, what JS this? A a work tree alternative. Work trees. My gosh. Those are one thing that I can't seem to get a handle on, so I'd love to see that there is an alternative idea. And we're even gonna be diving into open wait models. There's been a lot of new open wait models released. There's been a ton of crazy conversation around that, and we're gonna host a funeral for Stack Overflow. With me JS always is CJ Reynolds and Wes Bos. What's up? CJ, what's up, Wes? Yo. Doing good.

Wes, how's it going? You've been gone? How was your vacation? You feeling good? Ready to be back? Fantastic. Yep. Went to New Yarn. Went to the cottage.

I've I was gone for, what, two and a half weeks, and I feel like like, I don't know what I don't know what soul is.

Fable JS back, apparently.

Kimmy? Is that Kim Kardashian's model? The hell? Like, I can't It's Kimmy Antonelli's, model. Wes I was gone.

Yes. Kim Kardashian's, AI model, Kimmy Antonelli's AI model, all that good stuff. Wes, do you know Node Kimmy Antonelli JS, mister, Lando Norris himself? No idea who that is. Who's that? He's the the current first place Formula one driver, and he's, like, 19 or 18 years old. He was a Formula one driver before he had his driver's license. That's crazy. Holy smokes.

So he's a he's a little young guy, but he is going to win formula Node, probably. What's up? CJ, I think we're gonna get into your story first talking about the latest release from the Vue JS folks. I'm stoked just because it seems like it's got some cool naming stuff, and I'm down to hear about some cool naming stuff.

Yes. So for the uninitiated, Vue JS is the progressive JavaScript framework. Vvujs.org, they're one of the OGs. They came out around the same time as React. They've been here all along.

They're not new, and, they've been working hard on on some new stuff.

So Vue I've never heard of it.

I'm sure most people have, but, yeah, you know. It looks vibe coded. Is there this big gradient on the text? What is this? A new That's fast JavaScript framework? We can look at the web archive. This was probably before LLMs even existed.

Yes. Created by Evan Vue himself. Evan Vue. Yes. Okay. But version 3.6 RC has been released. So RC means release candidate, and that basically means, that the API is stable. It's ready for people to try. So if you're a user of Vue, if you just wanna try it out, you can try out the r c one. But there's two big things that are happening in version 3.6.

The first is a major refactor of Vue slash reactivity. So when Vue moved from version two to version three, there's a lot of internals that were reworked, and they essentially made it so the reactivity piece, the piece for state management JS actually a separate package that you could use without Vue if you really even wanted to.

But they've been hard at work refactoring it using a library called alien signals.

And so Alien Signals is a signal library that's really fast.

Mhmm. Really, really fast. And there are other frameworks that are adopting it under the hood as well.

But the idea being that and and you'll also notice this this is not a major version bump. Right? We're not there's no breaking change major breaking changes. We're not going to version four. It's just version 3.6. So once this is finally released, all view apps will instantly be just a little bit faster because it's using alien signals under the hood.

So that's one one bit of good news. And then the other bit is vapor mode.

And Oh. They've been they've been working on vapor mode and talking about it for a long time.

But the idea with vapor mode is you can essentially build your Vue components, your Vue ESLint a bundle that does not include the virtual DOM, does not include any extra stuffs. It's just as little JavaScript as possible.

This idea was popularized by Svelte and Solid JS, but now we're getting that inside of Vue JS.

Little things about, vapor mode. So in Vue JS, we use SFCs or single file components.

And in version three, they introduced this setup keyword. Essentially, on your script, you throw setup, and that allows you to just define all of your state variables and functions at the top level.

And now you can add vapor on there. And it's opt in per component, but it's also opt in per app. So you could actually have a regular plain old view app where it works the old way with the virtual DOM. I will say an optimized virtual DOM. It's a faster virtual DOM than React.

But if you have, let's say, one component that needs to be really performant, let's say it's like a a data table or, an analytics dashboard or something that that requires a lot of updates and would basically have overhead if there was the virtual DOM. You can just throw the vapor keyword on there, and instantly, that one component will now use the the native compilation and be a whole lot faster. Mhmm.

And so it's opt in, which is cool. And then the other aspect of this is if you're writing an app from the ground up, you can write it all with vapor. So instead of saying create app, you say create vapor app, and then you essentially get a similar build pipeline as with Svelte or Solid. Whereas Wes you run Vite build, this is creating a a really small bundle that doesn't include all of the view runtime, all of the virtual DOM stuff.

So why is this faster? Like like, what's what's going on here? I understand, like, with Svelte, it doesn't have the entire, virtual DOM, to be able to diff everything. It it simply just compiles to divs or or elements that can be updated. Is that the same thing? Yeah. Exact same idea. Essentially,

right now, if you're building a a Vue app with Vue version three, it actually compiles into render functions. So the the the output of a a view build is very similar to React, where you have these functions that get instantiated and then added to the DOM. And then whenever an update happens, like a state changes or an effect, something changes inside of an effect, the virtual DOM reconciliation kicks in to do the diff and then update the DOM. Okay. Vapor with vapor mode, that it's very similar to Svelte in that the built code essentially includes ESLint calls to update the view whenever a variable's changed. So that way, there's there's no extra run time that it needs to ship with.

Yeah. So instead of saying Wes this variable has changed, figure it out and update it, it's compiling it down to this span will need this number updated, and when that happens, call this function. Yeah. Exactly. So it's more it's more fine grained Yeah.

And so faster overall.

I've always liked that Svelte can can compile to that because just, like, the output of it is like, looks let alone performance. You know? Yeah. But Wes the sim simply the output of this, that they don't have to to carry along the whole different library.

Definitely. And I would say, like, early early days, I wrote an app with Vue.

It was I wanted to have, like, the the hacker effect of, like, you type in a password, and then it, like, slowly looks like it's revealing each letter, like it's it's hacking into the thing.

But it was really slow.

Yeah. One letter at a time. You know, like movie style. But it was really slow with Vue, because of all the virtual DOM updates. And back then, I was like, I'm just gonna try rewriting this in Svelte. I rewrote it in Svelte almost like a one to one port, but Svelte doesn't have a virtual DOM. It it builds to more, performant codes, direct update codes. And Yeah. The moment I built it with Vue, it was instant. It was, like, spinning really fast. Like, I didn't sorry. The moment I built it with Svelte. It was super fast out of the Bos. So we're gonna be able to do similar things with, Vue vapor Node. So I'm super excited.

Sick.

Love, more improvements like that to view. And I think more frameworks can embrace not having a virtual DOM. So thank you to the view folks.

Let's get into the next story here. If you are done, CJ, are you done? Done. I'm done. That's it. Alright.

Get work trees. So, folks, before we get into this next story, which is rift, get work trees, I wanna say what we're doing here is we each brought some stories, what's been going on in the web ecosystem, what's been going on in the dev space. We're gonna be talking about all kinds of stuff. Stick around because we're gonna be talking about open weight models, which has been a huge topic of conversation in just a little bit. This show is brought to you by Century. Century is the perfect place to track all of your errors and exceptions and fix them. I'm currently tracking down a problem with our Slackbot, Tasty. Tasty told us this morning that he didn't have database credentials, which is Bos.

And I looked into it, and it turns out the Sanity log showed that we, are on the free plan of Neon, and, therefore, we have run out of space, already. So I gotta figure out what the heck Tasty's been doing with all of our free database space.

Oh, agents. We love them. So let's get into the next story.

But first Yes. The three of you, Wes, CJ, do you guys use work trees?

I've tried. CJ, you go ahead. Sorry. Yeah. Yeah. Yeah. I so I have tried. And the issue with want like, needing using work trees is you have to be you have to really plan your app. You have to know what are all the things that I need to be working on and what can be worked on in parallel. Because the idea with work trees is you can basically, two two different agents can be working on the same code base and not interfere with each other. So Mhmm. I've tried it, but because the amount of planning it requires up front, I've kinda just settled back into just one sub agent at a time. But, essentially, you know, multiple agents can work on the code base without interacting with each other. That's that's the idea with work trees. Right? Yeah. I've I've used GitWork trees

more with with non agenta coding Wes I simply just need to have two of the same code bases working. So, think of work trees as if you were to have two branches, but you can literally have those both open at the same time. You don't have to switch between them. The way that it works is that it creates a secondary folder on your file system that has access to all of the files of that branch, and then you can you can work on both of them. So it's kinda nice when you can, like, reference both of them at the same time. Or if you're, like, if you need to do, like, a quick hot fix, but you don't wanna, like, commit or whatever and you wanna have both of them open at the same time, then you can do that. So I've I've used those plenty, and I do reach for them every now and then in agentic coding.

But I don't find myself running so many things at once where I need to have them all run at running in parallel, unless it's something like if I have, like, six or seven Git issues and I wanna fire them all off at once, yeah, that's a good use for for a work tree where it could

go and do that. Right? But See, c j n I six seven. Yeah. I was like, oh, I didn't even know.

I didn't even know. I'm so brain rotted. I didn't even know that I said that. Okay.

Now let's talk about Rift.

Rift is from Anomaly, which is the folks behind OpenCode, so they kinda know what they're working working with here.

And they have implemented a better alternative to Git work trees. So I saw this on on Twitter today. If you don't know what Riften Riften experimental alternative to Git work trees, it creates isolated, writable workspaces using copy on write file system primitives instead of copying your repository. So one of the downsides to using work trees is that, your GitHub blobs and storage and all of that stuff, that is shared between, branches and and work trees in Git.

But what is not shared is it literally copy pastes every single file. And even if you don't have a particularly large, like like like 10 gigs worth of code, you could have thousands and thousands of files, and you know that copy pasting many, many files can can take a little bit of time. So what this does is it uses some primitives that are in your file system. So on macOS, a p f s, most modern Macs are are using a p f s, or I would say all of them.

And what that does is it uses clone file, meaning that it will clone the file, but it will not actually make a duplicate version of that file until it absolutely needs to.

And the what that allows you to do is is you simply can make a work tree much faster. It's not like, oh, wow. This is is amazing. I just think this is pretty nifty. It's not something that's built into Git just yet, so people are looking at alternatives to it. Looks like it works on some Linux, all of Mac, and I I don't know if Windows has a primitive like this or not. I was looking into it. Maybe chat can let us know, but it'd be it'd be I I don't see why you wouldn't, dip into something like this other than it is experimental.

Oh, that's a perfect, thing for me to dip into. Yes. It's experimental. Experimental. I love it. Yes. Yeah. Just your description of it sounds great. It's like, duh, why isn't Git doing that already?

One of the other issues I had with work trees is the fact that that sub agents would have to do a PNPM install in every single work tree. I wonder if this has any solutions for that.

I'm I'm guessing not because maybe you you do need a separate node modules folder depending on what the agents are doing in each of the the work trees. Yeah. But yeah.

Yeah. I I don't think so. Here, there's some some hooks. Post create, Npm install, frozen so it no. You still have to do a a PMPM install. Although, if you have all the same dependencies, that shouldn't be a major Right.

Time thing because you would have all of those files on your system already cached. Instant. Yeah. Yeah.

Nice. Yeah. Have you tried it out yet or just early days, like Yeah. I I, tried it out this morning, and, like, it works. I don't I don't know what to tell you. It makes a, folder. Here, let me let me bring up my terminal here.

So I just did rift Sanity, rift create, name, rift test. I had to sudo it. Of course, this didn't work right off the thing. And what it does is it creates by default, it creates a folder in the parent directory called riffs.

That's always a weird thing about git work trees. It's like, by default, it will put it in the same folder that you're in. So, like, what you're working on is now a subtotal, and I think that's part of the reason why people get confused.

Ideally, you would you create the work tree in, like, a parent folder or you have a separate work tree, like, temporary folder that you're working in.

So I just simply did that, and I have a dot rifts folder. And each of my rifts, which would be a work tree, are now now live in there. All of your node modules are in there as well.

All of your your Git history is available to you. So, like, yeah, it just worked. It it wasn't anything like, holy smokes. This is hard to learn, or this is amazing. It's like, oh, wow. That that worked. That was very fast.

Oh, cool. Alright. Yeah. If you if you look at the docs for work trees, like, I got lost in it. My agents got lost in it. Like like you were saying, I had to figure out, oh, create a folder, git ignore that folder, point it at that folder.

This kind of just takes care of it all built in, so I like that. Yeah. Yeah. It's nice. So we'll see if it, it's again, all of these, like, new ideas, you can't put too much weight into them. It just means somebody had a cool idea and then typed it into a box, and it it's now a thing.

But you gotta think, like, the folks at OpenCode are thinking about how do we make our product better. And one of the downsides is that work trees, for some people, are very slow to create.

Nice.

Sweet. So if you're just joining us, this is Syntax Weekly.

We're getting into news, new libraries. We just talked about Rift. We talked about Vue 3.6 RC. We've got some upcoming news about open weight models that have, are on par with some of the Frontier models.

And, but before that, Scott has some stuff to talk about.

This is about staying up to date. Right, Scott? What do you got for us? Yes. People ask me all the time

about staying up to date on web stuff. And one of the resources that I had always been using is this MDN's update page. I'll share the link for this in just a minute here. But I want I I talked about this in my conference talk in Amsterdam, and I had so many people being like, I looked everywhere for that page.

Where is it? And then I was like, you know what? I thought it was easy to find. And I started prying around the MDN website for about fifteen minutes and could not find this page. So, I would assume that most people don't know about this or cannot find this page. I'll post a link. It is basically developer.mozilla.org, forward slash plus forward slash updates. This page contains every update for every API, JavaScript, HTML, HTML, and CSS as they get added to each individual browser as well as things like Node. And if you're into consuming a lot of data or creating process to understand what's being added here, this is a really great resource to have. I wanted to call out a couple of really neat APIs. I saw that just were added into this.

Well, before I do, it looks like I have a sandwich delivery. Sorry. I'm trying to stop that. Sandwich delivery every single episode.

Guys, this sandwich had some grapes. Wow. It's it's got it's got pesto and prosciutto and mozz on here. Oh my god.

Yeah. What a sandwich. We need an overlay with sirens and confetti when Scott gets Sandwich delivery.

Courtney opened the door and was just, like, laughing because she knew that I was going to be calling it out immediately.

Yeah. Oh, that's so fun.

Well, thank you to my lovely wife, Courtney.

So one of the cool APIs I wanted to show on this was text fit, and text fit does exactly what you would think it does. This is the property of my dreams.

Scales the font size of techno text Node to perfectly fit the width of its containing box in CSS. It's in Chrome, baby. This is in Chrome. It's in here.

It's only in Chrome right now, obviously, but here it is, folks. What? I annoyed you this was coming. This is like a like a fit text. Right? This is a fit text.

Some might call a fit text a text fit, and they have. It's a text fit.

This was added to Edge July 1.

So just to give you some context there. There's so much cool stuff in here, like flex wrap balance, flex flow balance, text fit. This is just a really awesome listing to keep your eyes on at any given point and just scroll through here and just see what is arriving in the browser.

Or, again, you could always take this information, distill it down to, like, an agent table of things that you could tell your agent to use whenever it's supported, blah blah blah. You could do so much with this. Either way, I I just wanted to call out this specifically as a nice resource for you to have to to check this out. Rule row rule row rule was added as well. And it it I put the filter in. Oh, a popover hint was added to, WebView Android, which means that popover hint is being added to more things. Popover hint for making tool tips with popover, nice and easy with low effort. Above popover hint.

Background border area. Man, like, what is some of this stuff? Every time I go through here, I get curious and fun. So, check this out. I'll we'll have a link in the show notes description, folks. It is for, and and also, I I when I posted this on Twitter, people were calling out this JS being an AI driven design considering JS there heavy border left on these things? I do wanna say that this page has existed before that was an AI trope, and I can say probably pretty confidently. I think it's it's not that. Maybe MDN JS the patient zero for this little fingernail border. Yeah. Wes. But very possibly.

Yeah. This design needs to be able to collapse every single Node. Because, like, I don't care what just dropped an android opera.

Oh, yes.

Yeah. You kinda gotta know. Node that.

You kinda gotta know what you're looking for a little bit or at least go through here. Yes. There's too many things. And then, also, when there is a property like Roarul, it's, like, easier to just Google it than it is to than it is to, like, actually go somewhere from this. But just a good, nice little viewpoint in what's coming up in the browser.

Looks like a bunch of the sanitizer API stuff just got added as well. That's an interesting one I'm gonna dip into. I've been waiting forever for, like, a native sanitization API for the DOM.

I'm in. I'm in. I'm in. What also I'm into is, CJ, you're gonna talk to us today about open weight models.

It seems like when I was gone, absolutely everybody released some sort of new Node, and you're gonna give us a rundown of what Inkling, Quinn, Kimmy,

View. What else? That's the plan. Yes. So if you're just joining us, this is Syntax Weekly. We're going over news and such.

And the big news is that just just the in the past five days okay. So first of all, Kimmy k three launched, and this was on Thursday.

If you're not familiar, you might have heard of Kimmy k 2.5.

Essentially, it's an an open Node Kimmy Kardashian? Yeah. Exactly.

But it's an open model that you can run on your own hardware, but there all Yarn all there are also cloud providers that will give you access to these AI models. If you're new to this space, essentially, there are AI labs that are have been training models and releasing them out in the open, for people to use and run themselves.

A lot of them are Chinese companies, so Kinney is a Chinese company. We're gonna talk about Quinn. They're a Chinese company as well.

But on Thursday, they released Kinney k three, and they're calling it Open Frontier Intelligence. So that's why we care about this. That's why this is news is up until now, most of the open models have been decent, but have never really been able to be on par with, like, Opus level models or g p t five five level models. But now with Kemi, we're there. And the benchmarks look good, and the rumblings of people using it on Twitter look good as well. But this is a 2,800,000,000,000 parameter model. It has a million token context window, and it's natively multimodal, meaning you can pass it images, PDFs, documents, and it can figure it could basically figure out what's in them and respond accordingly, just like you're used to when you're talking on chatgpt.com.

It can do all of those things.

And the the thing to look at are these these coding coding benchmarks.

Node, again, benchmarks are just benchmarks.

But but if you look at these charts, Kimmy k three is sitting and for a deep SWE, so that's one of the benchmarks, it's sitting above GPT 5.5. It's, like, point 5% better and just below Fable five, and a few points below GPT 5.6 SOL. Wow.

Yeah. And so on all of these benchmarks, it's either it's, like, in the top three, and that's comparing it to Opus and Fable and GPT five six.

So the fact that you can eventually run this on your own they're saying that open weights will be released by July 27. So right now, if you wanna use this model, you do have to talk to Kimmy's servers, which are hosted in China. So, don't do it on anything you wouldn't want them to have your source code of.

But on July 27, there'll be an open Vercel, so you can run it on GPUs in the cloud. This is a massive model. This is not something you're gonna be able to run on, like, a Mac mini or anything like that. You need lots of GPUs.

But once they release the open weights, we're gonna be seeing probably a lot of people, making this model available. And, for instance, GitHub Copilot made KEMI k 2.5 available via their API.

And so, eventually, you're probably gonna get access to Kimmy k three as well.

Mhmm. So, yeah, that's the news with Kimmy.

Thoughts, comments? Yeah. Yeah. Well, there's a lot of chatter today about, the Trump administration, apparently, considering blocking open weight Chinese models.

So, get your downloads in. I'm like Or Canada,

folks.

Yeah.

In the chat, I see people asking about quantized versions.

Because no no model has actually been released for people to run themselves yet, we're not gonna see any. But the idea with quantized versions is you can run bigger models on lesser hardware.

But e but even with a 2,800,000,000,000 parameter model, the the best you're gonna get is maybe, like, a 300 gigabyte model file. And that means you need, like, at like, at least 300 gigabytes of video RAM.

So it's not necessarily something you're gonna be able to run yourself yet. I I think

the, like, running it yourself is cool, but I think the the exciting bit here is that this is significantly cheaper than the Frontier models and seemingly just as good. Like, to give you some some pricing here, if you look on OpenRouter, the the weighted average so they do oh, OpenRouter has this thing called effective, let me share my screen here.

OpenRouter has this thing called, effective pricing, Wes they kinda, like, show you what the price effectively is because, how tokenization works and and pricing and caching and all of this type of stuff, makes the pricing kind of hard to compare. But if you look at it, it's about 50¢ input versus a Fable JS is $2.68.

Maybe not totally fair to compare it to Fable.

And then the output, $15 per million tokens, whereas Fable is $50 per million tokens. So significantly cheaper and seemingly almost as good. I Wes we'll we'll we'll see with that type of stuff. So that's pretty exciting to see that type of stuff. And I will tell you, I've been in DMs. I'm in a couple NDAs right now of testing some, like, up and coming models, and I last week, I got two emails from people saying, we've delayed our model.

Meaning that this came out, and they said, oof.

Oh, boy. Okay. We gotta make ours a bit better.

Yeah.

Nice.

A few more stats to share, and then and then we'll talk about, Quinn as well. Yeah. Anything to add, Scott?

No. I I I think the open weight models, like many people are saying, like, that's clearly the the future of things. But I think, just the word open kind of leads people to think that they could run these, local hardware. And for the most part, most people aren't gonna have rigs that can run these things to get them anywhere near the, performance that you're looking for. No. But what where I imagine is first of all, you saw we saw the pricing that that Wes just showed. Like, it's significantly cheaper. And so if you're paying API costs at enterprise for Claude or OpenAI

Mhmm. It this looks a lot more interesting to be able to run this yourself, because maybe you're an enterprise and you can afford the hardware or renting the hardware.

So that's something to to think about as well. It's it's really gonna be it's gonna give the the, big companies, OpenAI, Anthropic, a run for their money in terms of they have to figure out how to compete on pricing as well.

Can you speak on this comment? Someone says OpenWay does not equal open source. Thank you for teeing that up because I do wanna talk about that. Yes. So open source ESLint the traditional sense is about licensing of software. It means, for open source, licenses like MIT or Apache, basically, they boil down to, you can look at the source Node. You can modify it. You can do whatever you want with it. And, and then there are some open source models or open source licenses that say, you can look at the source code, but if you make any modifications, you must release those as open source as well. That's things like the GPL license. So that's about source code.

Here, we're talking about open weights.

So the the process of actually training a model is long and intense. Right? They have to they have to get all of the training data.

They have to run it on GPUs, and they run They have to distill all of anthropic's models.

Exactly. We're gonna talk about that next. Okay. But but yeah. So, basically, there's this whole big upfront process that they do that at the end of the day results in a file that has billions of numbers inside of it. And so when we say open weight, they mean you can look at the weights. But the thing about neural networks is just looking at the weights doesn't tell you how it was trained or what they did special with it. You just can see the numbers. So that's what we say when we mean open weight.

And then on top of that, these models also have various licenses. Like, Wes, you can run this for profit, or you you can only you you can run this model, but you, can't charge people for it. So, yeah, that's a good distinction to make. We're we can't see into how they trained this thing, but we can see the numbers that the training process produced.

So something to think about. And, like, I'm curious. Like like, you obviously wouldn't be able to take this model and then start charging people, or I'm not sure what the license actually JS. But, like Yeah. I don't know what the license is. Wes you were to, like, slap this into your product that uses AI? You know? There's a rules around that as well.

Exactly. You yeah. I'm I'm not a lawyer. You'd have to look at their their terms of service and licenses for each of these models, but that that's the kind of thing. The other cool thing you can do with these open weight models is fine tune them. And so, like, there's a whole ecosystem of, taking an Openweight model and then further training it on specific types of data to get specific outputs. So Mhmm. That's the other cool thing about Openweight is, like, we could take a a specific model and then train it really, really good on all of the the syntax podcast TypeScript.

And then it would be, like and this is as opposed to something like retrieval augmented generation Wes you just, like, paste in the transcripts. You could literally fine tune the weights to know more about how Scott and Wes talk and what topics they talked about in what episode.

Or if you work at an enterprise, you could take all of your internal documentation and and everything else and fine tune a model on that. So instead of having to wait for API calls, you have a model that knows your company,

inside and out, that kind of thing. Yeah. Remember everybody remember that was what everybody wanted to do? They're like, I can't wait till I can train my own model.

Weird. And that doesn't seem to be as as as they got better and as RAG got better. I don't it doesn't seem to be as popular, but I still I certainly can see the the use case for it. Definitely.

Yeah. Somebody asked about the architecture. So this uses a mixture of experts, and it says, sparse sparsity effectively activating 16 out of 896 experts.

So a quick plug from my video on how AI works.

In that video, I talked about the, basically, transformer blocks Wes data passes through the blocks. But there's a a different architecture that basically bolts stuff on top of that bef like, in inside of each block.

And the idea JS of activating all of those for every single prompt that goes through, they train it so that it only activates some of them. And what that means is that even though it's a 2,800,000,000,000 parameter model, if there's only, 16 active experts, it actually can run on, lesser memory than would be required if all of the experts were were active all of the time.

So there's that that aspect of it.

Wanna keep moving because I've been talking about this a long time. The other well, another bit of news is, forty eight hours after it was released, they cut off access because it was getting so popular.

So I don't I don't know if they've reopened access since then, but, yeah, it really took the world by storm.

It's exciting news. But on top of that, just, three days later, ESLint, which is another AI lab, I believe, by Alibaba,

which JS, like, the Chinese Google of sorts. Is that accurate to say? Yeah. Yeah. They're Okay. They're they're huge. Big company. Yeah. They're they're in ecommerce, but also they're kinda like Google as well.

Yeah. So they released Quinn 3.8.

And this is a 2,400,000,000,000, parameter model. And so on par with this one that we just saw from Kimmy.

And, again, they haven't released it for people to run themselves yet, but you can call their API to to interact with it. And, we're we're seeing a similar similar benchmarks.

The other bit of news that's more interesting in terms of if you're from The US is this company called Thinking Machines.

They released an open model called Inkling.

And what's cool about this is they are a US based company. So both ESLint and Kimmy and z AI and all of these others are China China based models that have trained on distilling larger models. So that's what Wes Wes talked about earlier Wes they're not supposed to do this because it's in the terms of service of, like, the anthropic API and the OpenAI API. But, essentially, what they do is they make requests to, let's say, Claude Opus four point six with a bunch of of, like, question answer pairs to see how Opus four point six responds, and then they use all of those, question answer pairs that are in the style of Opus four four point six to train their own model. So that's called distilling.

You basically, like, prompt another model a bunch to get the data out of it, and then you train another model using that data that you got out of it. And as far as we know, that's how these Chinese companies are able to produce their models and do it so cheaply JS they're basically piggyback piggybacking off of all of the work that OpenAI or Anthropic have done.

But the cool thing about,

who is hold on. Who is piggybacking on the work that the rest of the world has done and put on the Internet?

Absolutely. I didn't I didn't wanna lead into it, but you're totally right. And I'm I'm not saying that in from I'm not I'm not I'm not backing the the the big AI companies because they also are have

stolen the data or borrowed the data, however you wanna say it. But it's kind of a weird world. You know? And, like, I I'm I'm busting their anthropics balls here. Right? Like, obviously, they should be mad about this. I I would be as well if you spend billion dollars making Fable, and then somebody just cheats on your homework. But Wes with a top Node ball buzz. Yeah. I mean, I'm just a little sore that my 300 blog posts got scraped, so can't continue.

Yes. Yeah.

So, Inkling is a new model that was trained from scratch by a US company. So the former CTO of OpenAI, I believe, Mira. Yeah. Previously, CTO at OpenAI Yes, Mira.

Is now working at Inkling, And they released this. It was trained from scratch, and they released it as open weight so you can run it yourself or or run it on hardware that you rent.

And it's not as big or as capable as Kimmy and Quinn, but it is from a US company. And it was trained from scratch. It wasn't distilled as as as much as what as what they're saying.

And if you look at their initial, benchmarks, the one that they led with was actually Design Arena, and that puts Inkling really high up. So Design Arena is a benchmark where these models build out websites, and then the resulting websites are actually ranked by humans in in terms of how good they look and how well they work.

And in this one, Inkling is right between GPT five six soul and cloud opus 4.6. So in terms of design, it's really good, and it's open weight. Once you start to look into, like, the software benches, though, it's not as good.

It's probably more on par with Kineke k 2.5.

Yeah. It's a little bit all over the board in terms of all all of the benchmarks, but, ultimately, the news is we we have an open weight model from a US company. It was trained from scratch, and this is also gonna give OpenAI and Anthropic a run for their money because Yeah. Nice to Vercel. And and, also, there there won't be necessarily, like, the restrictions being placed on Chinese models if you're in The US. So Mhmm. It's good news.

That's cool. There's a company in here in Canada called Cohere that does, they're making their own models as well. They're, like, the Canadian AI model maker that everybody is touting.

And it look just looking at their website, it seems like they are really gunning for the enterprise because, like, that's going to be, a, the people that spend a lot of money, and, b, these companies are not going to be allowed to use, a Chinese model. A lot of them are not. They're gonna have to use something that is like like my bank. You know? My bank's not gonna be able to hook up my bank account to, Kimmy even though I probably already have.

They're gonna need to use something that's from Canadian soils.

Definitely.

Man, this, new Mac Studio with 1.5 terabytes of RAM needs to drop.

It's looking real good right now. Right? And I think yeah. I mean, it's gonna be super expensive, probably, like, minimum 10,000, maybe 20,000.

But it's an investment in your future because you'll be able to run these open weight models on your your local Mac Studio, at least maybe some of the quantized versions eventually. Yeah. Yeah. Full weights,

for Inkling require 1.9 terabytes of just disk space. Okay. Where where's the RAM or something? Possible. Apple doesn't even offer that.

That usually corresponds to how much video RAM you need, but that also depends on, like, the mixture of experts.

I do have numbers here, though. So the they released two models. Inkling's big bigger model is 975,000,000,000 parameters with 41,000,000,000 active parameters.

So it's a similar idea what we talked about before where not everything has to be active, meaning it doesn't have to use necessarily as much, video memory when it's processing. But as a size comparison, this is, like, less than half the size of QUIN 3.8 and QUIN three. So we know that they're not necessarily gonna be, or inkling isn't gonna be as good as those, but still pretty decent. And then they released a small model, which was 276,000,000,000 parameters with 12,000,000,000 active parameters.

Alright. Sick.

Inkling and good branding. Good good looking branding. I like the cool inkling stuff. So, Scott,

I see Node some some apps for us. Or

Oh, yes. And when I am talking about appetizers here, I'm talking about whole ass meals of apps, if you if you wanna call this that.

I I have a couple of really cool apps, one of which is a CLI, called MOL. Now MOL has been talked about quite a bit all over the web, but MOLLE is really great because it's a Mac cleaning CLI that you can ingest all with Brew. And I like this so much that I was really stoked when they released a full on app.

Then the app is really great. So, as far as, like, a better system process viewer like, I I use BTOP a lot to do my system process checking, but, like, nice GUI for everything, find and remove old files and uninstall stuff and delete caches. And that type of this type of app has been done for a billion years with, like, CleanMyMac and some of these other ones. And this one just feels so nice to use. And if you just wanna use the CLI, you can. But I just wanted to to shout out Node at mole.fit.

Really great little app here.

This is Scott this. Yes. It's everybody I I was I posted about I forget what it Wes. A tool that I used to delete old node node modules because I'm always, always out of space on my computer.

And, usually, what I do is I'll run this, like, CLI tool, and I found, like, a 100 gigs of old node modules I didn't need. And then I would run daisy disk, to see, like, are there any, like, random weird files that are using up eight gigs? You know? Like, I found old ScreenFlow caches from three years ago that I could delete. But, like, this looks like it puts it all in one single tool. Everybody is recommending it, so I am installing this right now. Yeah. Sometimes pnpm everybody recommends stuff, I can shut it out. But, like, to me, when I tried this, I was like, oh, it does everything I want, and it has it all in one Scott. And it's very nice and easy. So I've used the CLI tool. I didn't see that they launched this this GUI.

Mhmm.

And, initially, I was very hesitant because the CLI tool has full access to your machine to delete cache files and stuff. But I ended up throwing a model at it to audit the source Node, and then I was like, I'll take the risk. And then it freed up a bunch of gigabytes on my my hard drive. But One thing the reason why I bought the UI, because you have to buy the UI,

is that it's a $19 onetime purchase. No subscription.

Oh, thank you. That's it. Mall. Yes.

You release a CLI, and you give us a onetime purchase. Thank you. Mall, you rule, the developers behind this.

Another app here I wanted to shout out was Moshi. I had tweeted out yesterday, are there any, terminal apps for iOS that support touch? Because, my god, when you have a system that, like, Herta to manage all of my my t mux kind of stuff, everything is based on leading keys and prefixes and, keyboard shortcuts. And then you pair that with a stupid mobile keyboard, and you gotta be kidding me. Like, I I'm gonna be using my mobile keyboard to do control b or even set up, like, macros to do that for me. I need to be able to click on stuff, and I couldn't believe just how none of them did. But, Moshi was suggested to me, and I installed Moshi, and it worked first try. This is git moshi.app.

It is a terminal app. It works for Apple and Android.

It's, has touch support. It even has built in herder support so you can get directly to your herder tabs if you are using herder to manage your agents.

I don't know why it it has dictation as a feature. I guess that's fine because, like but, I mean, the phone has dictation built in. Dev viewer, chat viewer, all I know is that this thing allowed me to connect via MOSH, which is an SSH alternative to my server. It allowed me to use my herder and allowed me to ding prompt from a dang phone, and it did so in a much better way.

So, Moshi, get moshi. App. Really enjoyed this.

So what's your stack now? You got herder, Mosh.

What's the Mux one that we were doing that's a Tmux alternative?

That's Herder.

Herder. What about okay. Herder JS the one we did the episode on. Man, like, right before I left, we did an episode, and I was like, I love this. And then I came back this morning. I was like, what was the app that we were using?

I'm also been using from our good friend and former head of syntax, Ben Vinegar.

I'm using Hunk from modem, and I'm using that as a diff viewer as another tab in my herder setup. So I am using Hunk for my diffs.

I just opened up my herder from before I left, and this is this is why it's so good. I opened up all my projects. I have all my sessions.

Everything Wes just there. What I want. Because that was the thing. I opened up my terminal. I was like, what was I working on before I left? Yeah. My herder, everything is still there. It's amazing.

I know you can restart your computer. You can do all it just your sessions, your tabs.

It's it's the best.

Beautiful.

Yes. Yes. Beautiful. But also beautiful is Stack Overflow, rest in peace. That's beautiful. I it's not beautiful. It's actually kinda sad. CJ, you had a story on here for RIP Stack Overflow.

Can you talk about this? Yeah. It's it's nothing official, but, this was actually shared on Hacker News. So, if you're not familiar, Stack Overflow actually releases all of their data that you can then query.

If you're a teacher, it's really good for teaching SQL because they give you, like, tons of tables, and you can do joins and stuff like that. And they also have a a data explorer.

But this query, shows us how many new questions were created each day.

And this graph just shows the decline of Sackerville. You can see that in in just just yesterday, only 880 questions were asked on Stack Overflow. Whereas if you look, like, at their at their peak back in, 2017, they were getting as much as 200,000

questions asked per day.

And we we know why. We've we've talked about this, but, basically, you can see right around 2022, so this is right around when ChatGPT was released.

Yeah. People's people just started asking ChatGPT instead of posting their questions on Stack Overflow. And you so you see this slow decline. So in 2022, we're at about a 115,000 questions per day, and then slow, slow decline. In 2024, we're at 40,000 questions per day.

By 2025, it's only 15,000 questions per day, and now less than a thousand questions per day. So, first first f in chat. Throw throw your f's in chat for for Stack Overflow.

I I actually like, I don't like seeing this because, that means there are a lot of questions that people have that aren't getting indexed on the web. Right? They're having a one off session with Yep. Chad GPT.

They solve their problem, but then when someone else comes along to solve that same problem, they have to pay token pricing. Right? Like, they don't they don't get to benefit

from a forum with all of these questions that have been asked. Well, that's Stack Overflow is trying to do that. They're they're they released, like, Stack Overflow for agents, where, like, agents can post what they had, but it doesn't seem to be catching on, at least not yet.

But you're right. It's just like, oh, you have to everybody solves the same problems over and over again. And is is that a problem?

Yeah. I mean, to me, that that seems like a a step backwards.

Yeah. Because it's it's more compute. It's more powered. It's more resource. It's more potential time spent because an agent is spending to try and solve that same problem.

Yeah. So what you mention I hadn't heard of what you mentioned, but that could be cool Wes where agents are putting their their questions and answers on a on a forum.

What if we just generated all of that every single time we needed it and boiled the oceans because of it? Like

Yeah. You know, what what makes me think is weird about this is that so often, I would post something to Stack Overflow, and I would get, why are you doing it this way? And and sometimes that's the that's frustrating, but sometimes that's the best thing. If you're debugging something with, like, a coworker or or or posting it on Stack Overflow, often, the answer to your problem will be, like, you're you're coming apart approach. You're approaching this wrong.

And I don't know that, like, the quick fix from a lot of these AI agents is often, let's take a step back and and redo this. Often, the fix is like, alright. Well, here here's how you can fix it in the, like, the hole that you're in. You know, we could patch it here. We can add an if statement when this thing pops ESLint. That'll cover that use case, and you start to make a bit of a mess.

So that kind of makes me bummed because, like, people are not going through that. Like, what's the best way to approach it? And and, coincidentally, that's one of the highest skills you can have right now JS, like, not just writing the sheer code, but how do you tackle these problems? Have you ever considered that chat GPT

is correct? And, Wes, you are absolutely correct in your ideal implementation here, and you, made no mistake. So this, and I, of course, was wrong for my, my suggestion.

Yeah. Yes. And I think you can get those things out of an agent, but I don't think that those are those are automatic. I'm just looking at it. Agents dot stack overflow dot com.

Node, seems a couple hundred hundred. Here we go. Agent activities, 1,200 posts created.

That's in all time. And this launched a couple weeks ago. So yeah. Nothing nothing really.

So I wonder if this is is it, like, an MCP server where your agent will post after it solves an issue or something like that? Or the agent's actually actually asking Wes? Yeah. It's a skill. Yeah. It's a skill. So they just post things.

Yeah. It's weird that they ask questions.

Like, why would you Oh, there's a today today I learned from an agent. Today I learned VLMs, kv cache, d type auto silently promotes compressed tensors. Yes.

Fascinating. So some of the best learnings. It's like, okay. Well, you figured it out. It took you three hours.

Now summarize it and post it online.

I think if people could get in the habit of doing it, this could be good, but this is also another avenue for just AI slop. Just Yeah. Just post that actually don't work.

And then they're trying to game the system to get more points. Yeah. One thing Yeah. Exactly. Thing I'll mention is so Stack Overflow is actually part of a a bigger community of question answer websites.

And, I'd be curious to see the data for these other ones as well. So there's, like, ask Ubuntu, mathematics.

There's a specific software engineering one. Plumbing ones. Yeah. There's plumbing. There's, like, pet owners, movies and TV.

And I I would be curious if they're seeing a drop in questions asked because, like, that's the other aspect of what was great about the Internet before AI is there's it's people talking and people sharing and giving real people opinions. Very similar, like, what we try to use Reddit for now, but that's slowly going away because it's overridden by bots.

So,

yeah, rest in peace. Let's let's check it. Okay. Can we run the same stat?

I think so. Let me see.

I think I can just copy the URL because this is change? Instead of

Stack Overflow for instance, let's try just server fault. Yeah. If you change the Stack Overflow in the URL to math, you are also seeing the exact same drop.

C.

Blender, WordPress.

What's something that's not destroyed by AI?

Oh, add that to the possible

question.

Well so this is for

Law.

Yeah. For server fault, also, we see a drop. I'm curious, like, Yeah. What what would be a good one to look at? How about English language and usage? Like, because that has nothing to do with computing.

It's just on the English language.

I mean I I'm not I wouldn't be surprised to see that have the same exact drop. I mean, I know I'm Yeah. All my English Wes, I'd be asking to AI or or Google. It's the same drop as well. They I mean, at their peak, they were getting 1,600 questions a day, and now they're getting 50 questions a day. Yeah. Yeah. Yeah. I I I've asked a plumbing question in the past on whatever the Stack Exchange plumbing one is. And then the last time I had a plumbing question, I just went on Reddit. Wes they just like, are you sure you want to do that?

Well, I I hear somebody immediately would I I had an answer within, like, three minutes. You go to my Reddit and look at it, but I think Reddit is a better avenue for this stuff. Reddit. Yeah. For sure. Or, like, Facebook groups. I know you guys hate Facebook groups, but there are some cracked people in these very niche Facebook groups. Some cracked 90 year olds answering your questions. Yeah. No. No. There's there's a lot of, like, dudes wearing white sunglasses Okay. Like, make it doing the laugh emoji to everything, but there are some smart people in there. Nice. Okay. So that's all I had. Funeral for Stack Overflow.

I'm gonna pass it off. Wes in peace. Yeah. RIP RIP, Stack Overflow. Yeah. Pass it off to Scott. We have I don't know if you've Pedal? Yeah. Have you talked about your foot pedal on the channel yet? We talked about it in the DAX episode. I got a foot pedal.

When you Google computer foot pedals, man, they're all from, like, the nineteen eighties. They're crazy bad. But Elgato, of all people, actually made a really good one, which the reason why it's good is because, one, it actually doesn't look like complete ass. Two, it has three pedals instead of just Node, and the three pedals is really great. So what the heck am I using a foot pedal for? Well, I use the center one to push and hold for doing dictation.

This one does enter, and this one monitors my herder. Randy, if you could can you throw me and my herder up on screen? Okay.

Let's see. So, ideally, what I would do is I would push this one like this, and that sends me to the next tab. And then I would push this one to speak, and then I would push this one to hit enter. And I would just do that, and that's how I Oh my gosh. That's how I operate my, that's how I operate with my foot pedal.

But, yeah, this thing's dope. I, I like it quite a bit. I was couldn't I was just making my own dogs out and, like,

for those flinch. Yeah. For those listening to this, bare feet

live on stream. So Oh, yeah. For free? For free. Yeah. You didn't mean to talk to free. Sorry, folks. Yeah. Well, I had to show the dexterity needed to require, for this this foot pedal. I can use it with shoes too, but I prefer not to. I I got a nice little foot feel on there.

It's nice.

That's all I got for the foot pedal, folks. That's how I use it. The software is all Stream Deck software, and you can do macros or whatever you want with it. So

Sick.

I couldn't have just used my hands, Max. I couldn't have. I needed to show how it really worked.

CJ, you got a bunch of other stuff. Do you wanna get into it? Yeah. I got a couple more links to to wrap us up here.

The first one is called decoy font.

So this is a font that hides what you're typing from AI.

And, the idea is, this won't work with just, like, plain text on a website. Basically, if you give an image to AI, any of the main models from Anthropic or OpenAI or Google or whoever else, if you give them an image that has text in it, it will basically be able to read the image because it's been trained on image. It's not exactly OCR, but it basically can pull out the text and understand the text that's in the image that you gave it. But if you use this font, they showed in their Wes that even the most frontier models can't actually see the hidden message. And, basically, what it does is it puts your your real hidden message in a kind of, like, blurry behind the, text on top that the the robot the AI will actually see. And if you zoom out, you can see the actual text that you you had written. So for instance, if you if you're publishing PDFs online and you don't want AI training on them, or images and you don't want AI training on them, you could use this font instead.

And when AI pulls this image in, it sees just the text, sorry, robot. Whereas if you're reading it just at a normal distance, you see the text, happy human.

So pretty cool. It's it's an interesting idea, but the whole the whole thing is basically from at a distance, you can see it blurry, whereas the the model the AI models only see the higher level text.

And they showed a bunch of, example, threads where they're, like, asking the AI, are you sure you don't see the the the that other message? And it it couldn't figure it out.

So

That's funny that somebody figured that out. Yeah.

And I'm just curious how easy it would be to figure how help the AI write a script to reverse it.

Well, I think if it yeah. If the AI knows it's a thing, it could literally just downsample the image, like, zoom it out Oh, yeah. To be able to read it.

But, like, in this example, you can see the embedded image says this sentence is written in decoy font. And then when the AI tries to read it, it's just gibberish, just a bunch of, like, random letters.

So

yeah. Cool.

And I love it. Like a is this just a funny thing or, like, somebody has, like I think it's probably a funny thing. I mean, it's funny, but at the same time, if you're publishing yeah. I mean, if you're publishing content on the web and you don't want AI trained on it, you could use this font. Like but it specifically has to be rendered documents. Like, it can't be text on your website. It has to be a PDF or an image. So So you just give access

accessibility out the window?

Pretty much. So what you're saying, CJ, is that you hate accessibility, and you think it's wrong. ESLint people,

CJ? I knew it.

I knew it.

Moving right along. I got another Scott. Let's cancel, CJ.

This is this one's really fun.

So it's from Fabian Sanglard, and

they went deep on Jurassic Park. So, Wes, have you seen Jurassic Park? I have seen bits of it. Oh. I remember at a pool park Come on. The kids are playing it. Maybe, like, five or ten minutes of Jurassic Park. I understand. It's got the dinosaurs and the stupid jeep and things like that. Also has computers.

Right? There's yeah. There's lots and lots of computers in Jurassic Yarn, of servers, server racks, CPUs.

And this article goes into the fact that everything they showed in the movie was a real computer. Like, the they kind of go into the fact that there there were they knew that nerds would be watching this movie, and so they didn't wanna show computers that were fake or wouldn't be what somebody in those positions would really be using.

So they shot the screens. I I would so do those screens Scott have, like, refresh rates that couldn't be filmed? Because I know that was such a major concern for filming TV for so long. I believe you can kind of tune your,

on the camera itself. It's like the shutter rate. If you get it exact I don't know if they did that, but if you get the shutter rate exact, then it won't show the lines.

That's exactly what I had today. My I went into I'm at my cottage right now, and the LEDs were strobing at a different rate than my office at home. And my camera was just was was rolling. Strobe.

Yeah. So I had to change the shutter.

You had to change it on your camera? Yeah.

Pushed a bunch of buttons, and it started working. I I need to pee for my camera, man. I Oh.

Stupid

little Sony things. I don't know what any of these things do. The Sony menus are terrible in those cameras. And to make matters worse, Wes, the I have two Sony cameras, and they're both the menus are so different. And and one one non menu based thing that drives me nuts about them, they both have two SD card slots on them. On one of the cameras, the, number one slot is on the top, and two is on the bottom. On the other one, it's Vercel, as well as the cards flip front to back differently. So every time I open the flap on my camera, I'm like, which one is this gotta go in in which direction? I gotta, like, try. It's, like, worse than the USB problem.

And you know they'll never fix it because, like, the professionals know those menus cold. Yeah. And it's just such an awful interface for everybody else. There's people that make custom, firmware, but ain't no way in hell on doing that on my expensive camera.

I will say, though, Wes, MCPs for me have, like, really leveled up in the past forty eight hours or so, maybe longer than that. Why? I I've been using, Sigma MCP to so one thing that I don't want to do is I don't want to do AI thumbnails on this channel. Right? We don't want them to have AI creating the thumbnails because AI makes all design look like that. But what I wanted was I have a design direction, and I wanted AI to be able to, shift these components around. And so I had the Figma building blocks in pit place, and I told the Figma MCP to give me several different directions using these assets. And it did a pretty freaking good job, at least, moving things around to the point where I could then and then there's no generation happening. It's essentially just shifting things around and changing copy for me, just because I was stuck creatively. And that got me out of a little bit of a creative rut, and then I finished it myself.

Two, DaVinci MCP.

The DaVinci Resolve MCP is so good. It's so, so good. I wrote a little Python I wrote AI wrote a little Python script that could tell who was talking, me or Courtney, based on the frequency of our voices and then did cutting based on that. And it was just like, this rips. I love this.

And if you watch my Ricci mini video on this channel, every single graphic I made in that video was done with browser tech using DaVinci MCP to, generate the well, it would first generate the motion graphics that I have in an app that I'm building, turn that into a video using DaVinci MCP, inserted the timeline with the markers at the exact timings I wanted to and could go back and forth that way for all computer graphics.

Man, MCP rules.

Big fan. Yes. The DaVinci Node in my learning, I learned DaVinci over the last, what, like, two months or so. And just simply understanding what the heck is going on, being able to type into a box and ask it these Wes, so good.

Yes.

Questions in box. Good. Alright. CJ, what else you got for us? Got one last thing for you, and this is just a fun one.

So this is a three d voxel environment where you can ride some of the trains in Tokyo live.

So you choose a line, and this is real time because the the Tokyo, controls. Okay. The Tokyo transit has real time data about, like, where that train is, how far away it is from the next stop, when it's stopping, how long it's stopping.

And so they created this three d voxel environment that looks like, Tokyo, and then you get to just choose a train and ride along with it. So right now, we're on the outer loop for, Osaki, but then you can switch trains,

and ride a desert train. Awesome. I'm going to Tokyo in March, and I'm going to be riding the hell out of these trains. I've ridden the the Tokyo, train quite a bit. But,

this is sick. Where does this data come from? Is this, like, Google Maps or Apple Maps? No. I don't have the the actual Tokyo transit provides the real time data.

Man.

Nice. Folks are cool. I'm gonna need some Tokyo recs. I already do have quite the itinerary planned out for the ten days we're gonna be there. We're also gonna, head up head over to Kyoto for a couple days, but, I'm very, very excited about planning some stuff out. So if there's anything unique that we have to be doing in Tokyo, let me know because I'm gonna be there. Yeah. I'll DM you some Rex.

It was a blur. I was only in Tokyo for four days last year to try out the sushi. But

Oh, thanks, Wes. Yes. No. I'm just dying because last time I had good okonomiyaki was in Tokyo, and I've never found a place here that does it well. So I'm stoked. And, I get to use my language skills, which I am also stoked for. I've been doing some practicing.

Nice. That's all I got. Just silence. Just silence.

Nobody says, gosh. That was just safe. Story, bro. Fake.

Just do give me that. Placate me there. I From practicing, you're Japanese.

Wow. Yes. Are you gonna have a sword? I

Yes. I can and I'm gonna have a sword? No. Wes, what are you talking about? Oh my god.

Oh my gosh. CJ. CJ's even a bigger nerd. Okay. So let's stop being mean to Scott and move that over to CJ here.

Yes. Alright. What else do we got? Is that it? That's all I got. You guys got anything? That's it.

Sweet. I don't have anything else. I'm gonna I'm gonna leave now. K, guys?

Slow exit.

Yeah. Where JS he going? He's gonna do more feet.

Let's do the feet. More feet. I'm not doing more feet.

Yeah. So that's what we that's Yeah. That's all we got for you today. If you wanna see Scott's feet, go watch the VOD.

And, we do this every week. So if you're just now tuning in, be sure to watch the VOD. But every Monday, same time, come hang out with us.

And we're gonna try to do a raid on Twitch. I don't know if we can we'll be able to find anybody, but that's basically where we take all the viewers that are currently in our stream and send them over to somebody else's stream. So stick around on Twitch, twitch.te twitch.tv/syntaxfm if you wanna join in on that. But this has been awesome. Thanks for joining me guys, and I will see you all next week. Peace. Peace.