Scott Tolinski

Things Scott Says on Podcasts

Teaches JavaScript and front-end development through Level Up Tutorials, a video course platform, and brings that hands-on teaching angle to conversations about frameworks, charting libraries, and tooling choices. Skeptical of the claim that AI coding assistants fix bad architecture, since adding code on top of a mess leaves the mess in place. Co-hosts the Syntax podcast with Wes Bos, a long-running show on web development, now part of Sentry, that covers new JavaScript tools and frameworks in detail.

Where to Find Them

Scott Tolinski hosts Syntax (Wes Bos & Scott Tolinski) . They have also been a guest on JS Party: JavaScript, CSS, Web Development (3 times) , Whiskey Web and Whatnot (2 times) and Elixir Wizards .

Recently: “1056: Convince us that Effect.ts is good” on Syntax (Wes Bos & Scott Tolinski) (November 2026); “1055: What the hell is going on with GitHub?” on Syntax (Wes Bos & Scott Tolinski) (November 2026); “1054: Reddit Closing it’s Doors” on Syntax (Wes Bos & Scott Tolinski) (November 2026); “1053: What’s in Our Home Lab” on Syntax (Wes Bos & Scott Tolinski) (November 2026); “1052: Github Universe Keynote Recap” on Syntax (Wes Bos & Scott Tolinski) (November 2026); “1051: Mourning the Death of Code” on Syntax (Wes Bos & Scott Tolinski) (October 2026).

What They Said

“The largest Reddit open source community has shut its doors to anybody who even glances at the word AI. They've made it very clear that if you do not speak English well, you cannot even use AI to translate your text. And they suggest that maybe this isn't the community for you if you do not speak English well. They literally say that. I think they've lost their mind over at open source.” — Scott Tolinski, Syntax (Wes Bos & Scott Tolinski)

Tolinski reacts to r/opensource banning AI use entirely. He objects most to the rule against using AI to translate, which he reads as turning away non-native English speakers.

Syntax (Wes Bos & Scott Tolinski) · 2026-11-09 Permalink → Listen →
Syntax (Wes Bos & Scott Tolinski) Around 27:00 into the episode
Scott Tolinski

Come on. But

CJ Reynolds

…Absolutely. Absolutely. I don't think that's a conspiracy theory. Yeah. Like it adds to their daily active users. Like any place you go, it looks like the site has activity. So there's, it's, it's supposed to push and pull in order to decide like what they actually do about the bot traffic. So.

Scott Tolinski

Yes. On that same note as Reddit Closing in that regard, another community on Reddit has also closed. And that is the R open source, which is the largest Reddit open source community, has shut its doors to anybody who even glances at the word AI. They've made it very clear that you can't even use, if you do not speak English well, you cannot even use AI to translate your text. And they suggest that maybe this isn't the community for you if you do not speak English well. They literally say that. I think they've lost their mind over at open source. When you can't even talk about are you sharing your screen?

CJ Reynolds

Sorry.

Scott Tolinski

No, I'm not. I'm just talking in general. If you cannot even talk about the Linux kernel contributions or anything in regards to any of that stuff, you are out of your mind. You've taken the exact opposite stance of open source in general and have closed it down. It's crazy to think like, oh, I'm…

Wes Bos

that's it. That's obviously nailed. Everybody has everything that's open source version and everyone makes a new open source version of something and then abandons it a week later.

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.
“My take on it is that Bun spelled the end of Deno because Deno was the alternative to Node… But it wasn't better enough. Bun came out and Bun's just like, we're fast. We're going to put SQLite in this thing. We're going to start shoving in whatever the heck we want… You got the safe choice, which is Node. You got the crazy choice, which is Bun. And then it's like, okay, I guess I'll pick Deno because it's a little bit better than Node.” — Scott Tolinski, Syntax (Wes Bos & Scott Tolinski)

The Syntax hosts reacting to news that the Deno team is going to Cloudflare. Wes Bos had just said Deno tried many things that never caught on; Scott Tolinski blamed its market position between Node and Bun.

Syntax (Wes Bos & Scott Tolinski) · 2026-10-19 Permalink → Listen →
Syntax (Wes Bos & Scott Tolinski) Around 03:16 into the episode
CJ Reynolds

…you can actually run it on your own servers if you want to. So the main news here, Dino being sunsetted, Worker D is going to be worked on by Ryan Dahl. And also he'll have an initiative at Cloudflare to make it the best open source runtime possible. So big news. What are you thinking on this, Wes?

Wes Bos

…bit of a bummer, but like, if I think about my own usage, I use Cloudflare for almost everything. So I'm stoked to see this, right? Ryan is awesome. And that only means that the Cloudflare runtime is going to get bigger and better. So I think there's no better place for this type of thing to go to.

Scott Tolinski

Yeah. My take on it is that Bun spelled the end of Dino because Dino was the alternative to Node, but it was like, here's an alternative that does things in a more secure way by having to opt into those permissions. But it wasn't better enough, right? Where like Bun came out and Bun's just like, we're fast. We're going to put SQLite in this thing. We're going to start shoving in whatever the heck we want. And like the bun, bun, even though it is, I mean, I don't use bun personally, even though it's a little, you know, I don't know. It's a little bit different, right? I think they put Dino in a hard spot because Node was here, Dino was here, and then Bun was like, we're going to be over here. And now where's Dino? Right in the middle of who knows what, right? You got the safe choice, which is Node. You got the crazy choice, which is Bun. And then it's like, okay, I guess I'll pick Dino, I guess, because it's a little bit better than Node. So it was a tough market position for them.

CJ Reynolds

It was, it almost comes down to marketing because they were one of the first to allow you to write TypeScript without having a compilation step, right? And now we take that for granted because you can run TypeScript in Node. You can do it in Bun, but they were the first to be like, just write…

Wes Bos

I think it also comes down to like the usability of these types of things because as Dino was all about standards-based, absolutely everything, right? Like I had conference talks on this. I'm like, it's all standards all the way down. They implemented all of the browser features on the server. And…

CJ Reynolds

And also, how many people are using Bun because they didn't care and Cloud Code just chose it for them? Yeah. So

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.
“D3 sucks to use and having a wrapper around it is way better.” — Scott Tolinski, Syntax (Wes Bos & Scott Tolinski)

Tolinski had been digging through the TanStack Charts source to work out what it was built on, and found D3 packages underneath. The line is his answer to the obvious follow-up, which is why bother with a wrapper at all. He has been making charting-library tutorials for years, so it is a verdict from someone who has spent a great deal of time in D3 itself.

Syntax (Wes Bos & Scott Tolinski) · 2026-08-24 Permalink → Listen →
Syntax (Wes Bos & Scott Tolinski) Around 11:35 into the episode
Scott Tolinski

cool. If

CJ Reynolds

…dial into. You can get the example code to start from. So I thought this was slick. I've used a lot of chart libraries in my day and a lot of them are missing some things or don't work the way that I want them to. This seems to have a lot and it's just in pre-alpha. So I'll be keeping an eye on it.

Scott Tolinski

I was trying to see a little bit of like what this is based on because a lot of charting libraries aren't just like built from scratch. And I did find in the charts core package a lot of D3 stuff, D3, Ray, D3, Force, Geo, HexBit. So it does seem like it is D3 based. And anybody who might be wondering, like, why not just use D3? D3 sucks to use and having a wrapper around it is way better. So yeah, I love a good charting library. I've been doing like charting library tutorials for a long time. So having Tanstack do a charts that's a D3 wrapper, it appears if someone out there works on Tanstack and wants to correct me, it does seem like it is D3 based. That's great for me. Yeah, I'm very happy with this because there's, and I will say, there are some really wonderful Svelte…

CJ Reynolds

definitely cool

Scott Tolinski

about this. Yeah, very, very stoked on this. Yeah.

CJ Reynolds

And no issue with being based on D3. I mean, I think that gives you a lot of the fundamentals without having to do everything from scratch. And plus, if that is the case, there's probably a lot of D3 style visualizations that you could throw an AI AI at to kind of adapt to use Tanstack charts…

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.
“an unmaintainable code base is still an unmaintainable code base with AI.” — Scott Tolinski, Syntax (Wes Bos & Scott Tolinski)

On a Syntax episode about AI coding habits, Tolinski pushes back on the idea that AI assistance fixes maintainability by itself. The line lands while he's arguing that letting a model add code additively instead of fixing it properly doesn't change the underlying problem.

Syntax (Wes Bos & Scott Tolinski) · 2026-08-19 Permalink → Listen →
Syntax (Wes Bos & Scott Tolinski) Around 04:20 into the episode
Scott Tolinski

Yeah, right. Yeah. Totally.

Wes Bos

…integrated. They're a little bit behind and they got their lunch eight on quite a bit of this stuff. But I wouldn't say that if I'd say like, if you're comfortable with this type of stuff, I don't think there's much that you're missing from it from moving to another harness. What do you think?

Scott Tolinski

…I still like, I still really hate the output, like you said, CSS specifically. I really hate the CSS output. And many times it's easier for me to just go in and fix it quickly rather than have the AI try again and try again and not necessarily understand what I'm trying to get at in terms of like the way that I Wanted. And people, you know, when they say, why does it matter? Well, you know, an unmaintainable code base is still an unmaintainable code base with AI. AI can just like additively continue to add things infinitely and patch issues rather than rather than fix them in a correct way or something like that. And yeah, I mean, you could definitely argue that it doesn't matter. You just prompt and prompt and prompt. But again, all that stuff costs money, costs tokens. Yeah. I'm smart. I can fix it.

Wes Bos

I think with a lot of this stuff, people feel like, am I falling behind because I'm not switching up my tool stack? And if you feel like that, I think it's worth switching to something else for a couple weeks just to understand how other people are working. And you might come out of that on the…

Scott Tolinski

Yes, yes, totally. So, yeah, I mean, again, I still like using VS Code. I still like using Zed. And a big fan of Ben Vinegar and his hunk package, which shows you diffs, but I can't personally ride with just a diff in a term. You know, I need like having a diff that you can edit via Zed is…

Wes Bos

problem that cursor and VS Code have is that the freaking sidebar is too small for people. And a lot of people just have a tiny little sidebar and they're used to that. And then a majority of your work has now moved into this sidebar. And the ergonomics of that is really frustrating. It's hard to…

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.

Collections They Appear In