JS Party – Episode #300

Best of the fest! Volume 2

featuring our favorite moments from the last 100 episodes

All Episodes

JS Party listeners and panelists celebrate great moments from the last 100 episodes! You’ll hear from 14 of our favorite humans (and 1 horse) across 11 episodes. Here’s to our first 300 episodes and the next 300 as well. 🥂



Socket – Secure your software supply chain in GitHub PRs! Try it for yourself today

FastlyOur bandwidth partner. Fastly powers fast, secure, and scalable digital experiences. Move beyond your content delivery network to their powerful edge cloud platform. Learn more at fastly.com

Fly.ioThe home of Changelog.com — Deploy your apps and databases close to your users. In minutes you can run your Ruby, Go, Node, Deno, Python, or Elixir app (and databases!) all over the world. No ops required. Learn more at fly.io/changelog and check out the speedrun in their docs.

Notes & Links

📝 Edit Notes


1 00:00 It's party time, y'all
2 00:38 Episode 300!
3 03:17 The return of horse_js
4 06:27 The "His Beloved TypeScript" song
5 08:33 Kyle Beard & the future of React
6 22:20 Mikey G & Jerod's fantastic humor
7 24:39 Jarvis Yang & things bing Litt
8 28:00 Sponsor: Socket
9 31:36 Lars Ellingsen & spicy debates
10 37:58 Brian Zelip & Amal's insights
11 40:58 Kris Torres & Team Jerod
12 44:01 William V & extended convos
13 46:23 Mycale & the TypeScript wars
14 53:02 Nelson & recreating Node
15 57:06 Nathan P & creative coding
16 1:02:39 Amal & peddling vegetables
17 1:10:30 Nick & sneaking it in
18 1:11:53 Chris & Luis Villa
19 1:14:07 Jonathan C & live call-ins
20 1:18:10 Nick's final words
21 1:18:59 Join the community!
22 1:20:39 Closing time
23 1:20:58 Thank you 💚


📝 Edit Transcript


Play the audio to listen along while you enjoy the transcript. 🎧

Oh, my goodness… 300 episodes. Can it be that we have created 300 of these JS Parties? I guess so, because that’s how it works when you increment the number once every time you make a new episode. So we’re here to celebrate, reminisce, and talk about the best of the fest with many of our JS Party friends. Amal is here… Hello, Amal.

Hi. Happy to be here. Great job fake-rhyming…

Thank you. I have a knack for fake-rhyming; not for actually rhyming, but for almost rhyming. They call that a slant rhyme here in these United States… But you wouldn’t know that, because you’re over in Amsterdam, you know?

Yeah… I think in Amsterdam they would just call it bad… [laughter]

Well, they’re far more honest…

Ooh, Amal is laying down the shade…

Yeah, it’s gonna be a fun one…

Alright, so apparently, hungover Amal is spicy Amal.

Oh, my God… It’s not a hangover if it’s non-alcoholic.

Enough said… That’s Kball, bumping in there. What’s up, Kball?

Hey. Excited about this. I was realizing at some point, I think JS Party is now my longest-running gig. I have been hanging out with JS Party longer than I’ve ever worked for a company.

Oh, wow. That makes us feel special.

What brings you back each and every week?

You all, of course. You set me up for that.

But you haven’t been here for a while. So I’m wondering, what did we do?

I was here last week…

I’m just messing around. New job… You know, things get busy. That guy chomping at the bit just can’t wait to say hoy-hoy, but I won’t let him until I introduce him–


It’s Nick Nisi. Hey…

I preempted you. [laughter]

You did. You’re feeling salty as well… Chris - we’re not sure if he’s salty or not. He just rolled out of bed… But he said if I do one headlie, he’ll get excited. I don’t know, he didn’t say that. I just made it up. Hi, Chris.

Hi. Good morning.

Good morning to you. And of course, this is our 300th spectacular, so if you’ve been listening for a while, you know I’ve been relentlessly pestering you to send us messages, audio preferred, but text okay… And thank you all for writing in, for calling in. We have two voice mails to play today, and we have a bunch of listeners who will get shout-outs and I will read what they had to say. We’re gonna talk about some of our favorite parts about the last hundred episodes, some of their favorite parts… And just see where this goes. To do that, I thought it would be kind of lame if I were to just read all these messages… And I remembered my old friend, HorseJS.

Hello, JavaScript developers. I just want to take a moment.

Nick, you know HorseJS, right?

I know of them…

Tell the people about HorseJS, Nick.

They were a Twitter account, are a Twitter account… I guess Twitter’s not a thing, so they were a Twitter –

I think were is probably the way to say it, yes.

They were a Twitter account that would take fragments of other tweets and use them out of context, that were all related to JS.

I will clarify that I do not regret using Redux.

Good times. Very good times.

That’s right. Very good times. And that would be very obscure –

Any JavaScript nerds wanna get rekt?

…and so much so that there was other Twitter accounts that would explain the context for what HorseJS was saying, which was also really fun. One of my favorite troll accounts of all time…

React, it’s okay.

And we actually integrated it into the show. So the death of HorseJS is really bumming out the JS Party. In fact, we interviewed HorseJS one time, right, Nick? Me you and Divya interviewed HorseJS. And at that time, I had to decide how HorseJS was going to sound. And I thought it’d be weird to assign it a male voice, a female voice, and so I was reminded of that great movie… Not Alice in Wonderland. What’s the other great movie? There’s just two of them.

Billy Maguire.

Somewhere Over the Rainbow? What’s that movie?

You lost the rest of us.

Wizard of Oz?

Yes! I was reminded of that great movie, The Wizard of Oz… With the horse of many colors.

See, you just have to think like Jerod. I just had to put myself in Jerod shoes, you know?

That’s right. Well, it’s Alice in Wonderland and the Wizard of Oz. Aren’t those two semantically linked in your head, [unintelligible 00:04:55.13]

For sure. For sure.

Okay. Yeah, it’s just two great movies. So the horse of many colors - I thought HorseJS would be the horse of many voices. And so we’ve had a HorseJS on the show throughout the years, in order to just spice up the show.

Node.js will be dead in two years, and you shouldn’t learn Node at all.

Unfortunately, HorseJS died, and is now–

It’s HorseJS glue now…

…glue, yeah. [laughs] No, we don’t know what HorseJS became.

So you have a zombie voice for us, is what you’re saying? We’re right after Halloween; zombie voice is appropriate.

Well, I thought HorseJS was dead, but - remember in Lord of the Rings when Gandalf dies, and he’s Gandalf the Grey, but then he comes back, and he’s actually Gandalf the White, and he’s even better? Well, what I’ve realized is that HorseJS, the horse of many voices, is actually just like Gandalf. It’s come back, it’s even better…

Everyone, JavaScript is so cool. Have you heard?

And it did not want to read these listener messages, but what it was willing to do was to sing us a song.

Oh, wow.

[00:05:59.27] If y’all could see Chris’s face right now… [laughter]

HorseJS –

I think that should be the thumbnail.

…was willing to sing us a song in collaboration with Amal.

Wait, what?!

The song is called –

I didn’t consent to this… [laughter]

Just wait, you’re gonna love this. The song is called “His beloved TypeScript.” And I will play it now for the first time and probably the only time in human history.

I don’t know what it is, but I’m just digging the mood for this 300th episode.


I didn’t know this was the Nick Fest.

I’m just wondering if Amal isn’t the only one imbibing. [laughter]

Honestly… Wow. Wow.

Chris, your reaction?

I really – I have no words… [laughter]

I’ve left Chris speechless… That’s a win. That’s a win. Alright, well, thank you HorseJS and Amal for “His beloved TypeScript”, the first and only song written and performed entirely by a horse. Okay, let’s move on. Kyle Beard, our first listener to write in.

“Hello, Kyle Beard here. So many good episodes, but I’ve listened to number 267, which is “The future of React” multiple times. Very useful to get the perspective of the team behind RSC, especially at the time.” I thought that might bring out a topical conversation about React Server Components, and maybe server actions in Next.js 14, and maybe the use server directive, and - who put that sequel in my React component? What do you guys – what are your thoughts on this? This is a hot topic - for or against, happy or scared…

So I have a reaction. So I’ve long been in favor of making it easier for frontend folks to build full applications. And I think we’ve moved in that direction for a lot of things, and I think generally that’s good. And that was the whole JAMStack thing, and we’re doing that by letting you just [unintelligible 00:09:35.20] React and write other things. Okay, all these things are good. And I have recently, for the first time, had the experience of having to jump into two large existing Next.js full-stack applications, and oh my God, they are terrible. This is great for building simple applications, this is great for I have to access a little bit of data… But this is not one of the places where separation of concerns and getting rid of it makes for better applications. These things are tangled nests of workflow-dependent mess, that are really, really hard to maintain and work with.

[00:10:15.01] So I think enabling this type of stuff for simple things is great, and I also think that this is a place where, from what I have seen recently, this trend of trying to mash everything together and say “You know what, we can treat our backends the same way as our frontends”, and all of these different things has led to some really awful application architectures, and maintenance nightmares, and all sorts of headaches. And I don’t know all the reasons, but it turns out there’s a lot of specialized knowledge in the frontend - we’ve been trying to get that across to people for a long time, that this is a specialized discipline; there’s a lot of important things to learn. It’s not just simple things, it’s not just - as one of my developers said, “Taking JSON and shuttling it at different places.” There’s a lot to think about. That same thing is true of the backend, and trying to mash it all together and not have to worry about it works great for small applications, works great for demos, leads to some really terrible, unmaintainable systems at scale.

My thought on it is that it does seem weird, it does seem like it would be a tangled mess to maintain, potentially. I haven’t really done much with it… I’ve done some Next stuff and ended up abandoning it, because it wasn’t great at the time. And from what I see on Twitter, it’s still not great. But at the same time, I want to approach this kind of in an opposite way of how I approached React in 2013, when it came out, with that separation of concerns. Bringing my HTML into my JavaScript - that seemed wrong and weird at the time. Now JSX seems totally normal and awesome. In 2033, is that… God, I hope I’m not still writing this stuff. [laughs] I’m kidding. I would love to be writing it in 2033.

Well, if you’re not writing it, Nick, somebody has to be…

I really want to hear from Chris… I have some thoughts, but I feel like Chris’s face is giving me like way more interesting things than what I’d have to say…

I mean, really, I have no opinion. I don’t really know how to use React. I’ve never used Nest, or Next, or whatever the hell it is. So I have no idea. I’m sure it sucks, though. [laughter]

Chris, would you ever write a button where in the on-click you just put some SQL and run it immediately? That’s what it is.

Would you ever write a button?

I’ve written many buttons. I used to be an Angular JS pro…

I’m sorry.

But not anymore.

I mean, Angular was a leader in its day. Angular JS, specifically. Yeah, and I think even Angular in its current evolution is doing a lot of really interesting things as well. So yeah, no hate on Angular. But I think for me this trend of kind of RPC, which is an old pattern that was popular a long, long time ago, and back when single-page apps weren’t really a thing, you know… And so for me, it was really interesting, this old pattern of RPC coming back. So RPC - I think it stands for Remote Procedural Call, or something like that… But this is kind of a pattern that existed a long time ago, before single-page apps sort of thing; think PHP days and before. And so it’s interesting to see this kind of resurgence of RPC in this Reacty/Nexty world… And then also I think Signals is doing some of that work as well… There’s quite a few places in the ecosystem that I think are following this pattern… So I don’t know, I mean, it’s definitely not something I’m personally excited about, but again, not having used it in production, it’s hard to make an informed opinion… Which, based on Twitter, you would think everyone’s using it in production, and has well-informed opinions, you know… [laughs] And yeah, RPC is definitely not unique to web tech either, exactly. Chris just typed that in the chat.

[00:14:14.04] So yeah, I don’t know… Not for me personally, but it’s interesting. I’m eager to see how this plays out. I’m definitely curious to try it in production and see if it makes sense… I agree with everyone, I think in the simple cases - okay; but as soon as it gets complicated and hairy, I would refactor that out very quickly. So that’s kind of where I stand. But again, not having used this in production, it’s hard to have like a well-informed opinion… Which, based on Twitter, you wouldn’t think that.

Well, I’m withholding judgment till I see it in a more serious way, I guess. Right now it’s just like “Here’s a demo of one line”, but let’s actually see that in use. It did give me that response of “This is exactly how I was writing my index.php files when I was in college”, and those became giant piles of spaghetti code very quickly, and I needed something else. And so I don’t personally ever want to go back to that lifestyle… But wait till we see more, because it’s very much [unintelligible 00:15:11.14]

Lifestyle. Wow. It really does feel like a lifestyle, I agree.

It does, doesn’t it? Like, “Here’s how I write my web apps.”

Yeah. You’re either writing it that way or you’re not, you know? [unintelligible 00:15:21.18] one camp or the other.

At least then you were writing it server-side and maybe like doing messed up stuff, but it was gonna be executed server-side and then rendered; not like you’re writing it and you don’t know if it’s server, is it front end, is it gonna be part of my SPA? I mean, you do know, if you know what you’re doing… But when you come to something else, you’re like “I don’t know.” And that just seems somewhat more fraught…

I think these are only available in Server Components. But it is kind of interesting…

I’m not sure about that.

We had this idea of “We’re gonna have Server Components so we can write our same code on the frontend and the backend, and it’s good.” But now there’s some things that you’ve got to use a client on, and there’s some things you’ve got to use a server on… And really, is there actually a benefit from having these things both look like React?

100%. That’s where I come down on it, too. And I just feel like the messaging around like Next 13 and 14 and RFC has just been really jumbled, and really hard to follow. The Server Components stuff on the outset seems like a really good idea, and it seems like this is pushing you towards a better practice of shipping less JavaScript to the frontend. What is Server Actions – what’s the best practice that it’s pushing me towards there? It’s muddied to me. And it just – I don’t know.

Well, it goes back to our conversation with the React team on the episode that Kyle was talking about… I mean, that was like an hour and 15 minutes of which afterwards I didn’t come away feeling like spectacular about the story. I was just like “Yeah…” I mean, Dan was still kind of figuring out how to talk about it, and he gave us some analogies… I mean, you can go back and listen to that; you’ll hear Nick and I trying to follow along… And we are not inexperienced developers. It’s just like the way it’s been presented is not straightforward. And so it leaves you kind of…

I mean, I think there is something here that’s interesting… So for a long time, we lived in a world where we had these really great, ergonomic frameworks that were only available on the frontend. And we said “Oh, okay, we’re shipping SPAs, we do all this stuff on the frontend, there’s a simple API in the backend.” And then we said “Oh, there’s all these downsides of single-page applications. We want to maybe be able to render on the server, send over HTML, maybe we send less JavaScript… Okay, let’s do that.” And we had server-side rendering. And then we’ve got “Okay, these things are still kind of like a SPA, but they’re server-side rendered, but they’re still a separated frontend. They’re talking back to a backend that’s written somewhere else, that’s handling our data.” And people say “Okay this is good, but now I still have to deploy two things. This is a pain in the butt. What if I could do all of my stuff in one application, I could have the benefits of the front, I could have the benefits of the back, I could do all these things together…?” And so they’re trying to kind of go back to this whole single-stack application that you had in the world of a PHP app, or Rails, or something like that, and kind of recreate that, but instead of going back to front, they’re creating it front to back. Is that the right approach? For simple applications, that is great.

[00:18:21.10] I have yet to find something that is ergonomically beautiful and easy to work in as an old Rails application. Those are great. And they have technical limitations, and they only meet certain things, and at some point you want the power of a separated frontend, or something like that. So I think this is kind of in that same world. It’s great for simple applications; you can do everything in one spot, you only worry about one deploy, it goes out on your, Fly server or whatever… But –


Or Vercel.

I mean, let’s be serious, that’s where it goes out, right?

Oh my God, Vercel is such a pain to deal with backends on… It doesn’t do it. They’re trying to fit everything into this frontend-centric world, which works for some sets of things, but…

Right. For me, it’s just like – if we kind of take a step back and look at, okay, well, why are we doing this? Oh, because we’re not really handling these loading states gracefully, and we’re kind of failing users, we’re sending them stuff up from the server that looks like it’s ready, looks like it’s clickable… When you try to do something, nothing happens. So it’s like “Okay, well, how do we get away from that?” Well, you can write code around that. It’s just kind of like, well, I have this little stain on my carpet… It’s like, oh great, let me just bleach the whole room. I feel like this is taking like a mega hammer to a problem that can be solved in a much more graceful way just using like vanilla JavaScript and HTML, and CSS… So it’s just kind of one of those things where I feel like that’s the tool that we have as developers; we’re going to try to solve our JavaScript problems with even more complicated JavaScript, and I feel like we go down the complexity rabbit hole, because we’re just not incentivized towards simple solutions as engineers. I mean, it’s kind of really – it’s a hot take, but that’s real talk. That’s kind of where I stand.

I think we have an episode that’s like “Would you like JavaScript with your JavaScript?”, or something like this…

You’re right. Yeah.

[unintelligible 00:20:15.03] JavaScript sprinkles? It’s like we’re still doing that, but we’re putting it on top of a JavaScript pasta.

Right. Yeah. JavaScript with a side of JavaSlwipt, right? [laughter] For anyone who caught the Easter Egg in one of our episodes…

Ooh, yes… JavaSkwipt.

That was great. That was awesome.

Douglas Crockford calls JavaSkwipt – JavaScript…

JavaSkwipt… [laughs]

Let me say that again. Douglas Crockford calls JavaScript is smelly language…


Says it’s –

Hey, JavaSkwipt. Oh, JavaSkwipt. I love me some JavaSkwipt.

[unintelligible 00:20:55.29]

Yes, you silly wabbits… [laughs]

Elmer Fudd says “JavaSkwipt’s smelly.”


Okay, we’re gonna break the show…

Do you have brownies for breakfast, or what?!

No comment, I’m on vacation. No comment…

Okay, we need to move on. This could be a whole episode, but it can’t be this episode.

Well, hold on, there’s one important thing, Jerod, though, which is –

No, really, really, one, which is like, we’re announcing React features at a Next.js conference. Can we please – can we talk about that?

The unholy alliance.

Like, “What is going on here?” Yeah, it’s just this weird murky waters, where it’s like developers – people have to understand, the React ecosystem is a Venn diagram, and Next is a circle within that. It is not encompassed – like, they’ve got the order wrong. So…

How big is the circle?

I don’t know, but I’m saying a lot of people who use React don’t use Next. For example me, you know?

How much of this is Facebook is trying to be profitable and Vercel is still flying high on VC money?

[00:22:07.13] I don’t know. Either way, it’s sketch, and we should definitely talk about it in a show. So we’ll see. We can move on now, but I just wanted to throw that out there.

It’s an entire episode.

Yeah, it’s its own discussion.

But I want to hear from our listeners, such as Mykey G. Mykey G says “Hello, this is Mykey G”, which is how I’d introduce myself as well if I were Mykey G. “I started listening to JS Party last year and have no regrets.” That’s nice. “I enjoyed episode number 281, as it not only included Jerod’s fantastic humor, but gave excellent arguments for a few methods of debugging, showing a different perspective.” This was the Yep/Nope debugging debate, and Mykey G. knows how to make it onto the show; he gives me a compliment. And you’re going on the show when you compliment it Jerod’s - fantastic? Or what was the word? Excellent. No. Fantastic humor. This is how Amal snuck around early on[unintelligible 00:22:57.23] and I said “You’re coming back, Amal.”

[laughs] Right, right, right. Your mind is a powerful weapon, Jerod.

You’re on. You’re a regular. So this was – who was on that debate? It was Eric Clemens, I believe…

It reminds me just how little we do as kind of like engineers to test for like the non-happy paths; those assumptions are baked into so much code. I mean, you can look at failure states… And it’s actually one of the beautiful things about being in the frontend space as a web developer, is that that’s a portable skill, of being able to work in the browser. You hand me a URL if something’s going wrong, and I’m going to be able to look at these really rich tools that you don’t get when you console.log in Node. I can actually expand out variables, and copy to the console, like you mentioned. It’s almost always like at the network layer, where we see that some happy path assumption isn’t true anymore. And then that’s whenever all the problems arise.

And Nick didn’t show up, so I had to both moderate and debate. Ain’t that right, Nick?

I think it was this one. Yeah.

That was good time. That wasn’t like the time that Amal just didn’t invite you… It was different.

Oh, God…

Remember that one? …where you said anybody can come on except Nick.

Oh, I definitely have never uttered those words…


And yeah, you’re just a troll, Jerod. That’s what I realized. I think it’s taken me so many years to realize this about you… And you love to troll on air, when people can’t really like roll up their sleeves and like punch back… [laughs]

Oh, please do. I don’t ever stop somebody. I mean…

I’m a lady.

…Chris has been coming at me for a long time.

I’m a gentle lady.

Okay. Well, thank you, Mykey G, for writing in about my fantastic sense of humor. Let’s move on to our first audio clip. This is HorseJS… No, just kidding. This is Jarvis Yang.

Oh, Jarvis…!

[unintelligible 00:24:45.11] We all know Jarvis, he’s been a longtime listener and community member. Let’s hear what Jarvis has to say.

Jarvis Yang here. Please include the “This is going to be lit” episode, but include at least one Louis Litt code. I was hoping for at least one reference from the TV series Suits. Interesting episode anyways. Keep it up. Thanks.

Okay two words. Macbeth. Okay? [laughter] There we go. There’s a Litt quote.

So I confess to not being a Suits watcher. So I’m out on Louis Litt. Otherwise that probably would have made it into a subtitle, or something. But I don’t know Suits, so I had to go Google this after Jarvis brought it up… But Amal, you must be a Suits fan.

Oh, Suits is great. Suits is amazing. Granted, it’s taken me several years to get through the last season of the show… I still think I have like four episodes or six episodes left… But yeah, great show. Louis Litt - great character. Thank you for bringing up that analogy, Jarvis. You rock.

Y’all will be shocked to learn that I have zero pop culture or TV awareness… So I didn’t even know this was a thing.

I am shocked.

We are not shocked.

I am shocked.

That’s just right on brand for Kball. You don’t know Kball doesn’t watch TV or movies?

We’ve never had this conversation, because we’re always talking about careers and JavaScript… So I feel like we haven’t gone there.

[00:26:08.04] I tried Suits. I tried three episodes maybe… And it just wasn’t sticking. So then I went and started Billions, and I’m on the final season of that now. And Rick Hoffman is actually in that as well, and he plays a [unintelligible 00:26:19.08] doctor who lost his license. It’s pretty funny.

I also haven’t watched Billions… But I did watch some Louis Litt quotes on YouTube, and… Thanks, Jarvis; I might check that out, now with Amal’s seal of approval as well. It might be next up on my list. This episode, 284, “This is going to be lit” with Justin Fagnani from Lit HTML.

There was a project at Google one time called Razor, which turned into a project called Sky, which turned into what people know today as Flutter. And it was a fast subset of the web that was designed to be embeddable into other apps, and be 120 frames per second fast on mobile devices, and whatnot. Flutter is good at what it does, but it’s not the web anymore. And I actually think the web could really benefit like Electron desktop apps, like mobile apps, or whatever. I just want the web to have even more reach than it does now… And I really wish it had this kind of small, embeddable subset that, say, Servo could target as a thing it could support, without supporting the whole web, or something like that. People could embed into their super-apps in China, or whatever, where micro apps come into them, and stuff. I wish that there were – yeah, kind of the web, the good parts, as a spec.

And that was Kball and Amal. Awesome episode, so thanks for shouting that one out, Jarvis.

Let’s hit up our next listener, Lars [unintelligible 00:31:37.08] He says “There have been so many good episodes that it’s hard to choose. One of my favorites was the Yep/Nope debate episode on whether React is only good at being popular.

Good choice.

So yes, we’ve been having this conversation before it was cool… That’s episode 244, with Josh Collinsworth, I believe, who wrote the blog post, came on and debated… That was, I think, called “The spicy React debate show”, and it did get very spicy.

Do you know why React is so high in satisfaction? Because it’s so complicated to use it makes you feel like you’re a total ninja when you’re using it…

I feel called out.

…when really all you’re doing is using ten lines to solve a two-line problem. It makes you jump through so many hoops that you feel like you’re on American Ninja Warrior, reaching the top of that giant thing, just for writing a little bit of code… When really, they made you do this; this was just solving a web problem.

I enjoyed that one as just a listener… I think, Nick, you moderated. You did a mighty fine job.


Did I also win that one? I think I won somehow.

You never win if I’m moderating…

I always win. He says “I had just been getting to the point where I felt more confident in React, and that episode opened my eyes to what else might be out there. I also really enjoyed the recent episode diving into Nick Nisi’s toolbox, number 278, where for the first time I heard about WezTerm, which is now my daily driver. On a funnier note, the line that made me laugh the most had to be Amal’s revelation that the sound DMX made on most of his songs was supposed to be him barking.

Honestly, that was like a very real revelation. It was like, I had no idea…

What did you think it was?

I still have no idea.

I don’t know.

What is the sound? Do we have this on the board?

No, we don’t have it on the board. I did put it into the episode.

“Elon Musk says X will fund legal bills if users treated unfairly by bosses.”

Okay, I’ll keep it as true.

Yeah, definitely true. I mean, it’s so ridiculous, it has to be true. It’s how I feel.

So ridiculous it has to be true… But is it actually true? Did he actually say that, or did I make it up whole cloth? [win alert] It is true. He said that a couple of weeks ago.

I asked you to repeat the title because I was curious if you said Twitter or X, and you were trying to get us on that.

Oh, I wouldn’t be so malicious. You know I fully support x.com.

Is this where we start playing DMX? [00:34:13.26]

That’s what I was saying – if you listened to our show a couple of weeks back, I was saying DMX is rolling in his grave right now, because he’s getting all of his cool songs again steamrolled.

[laughs] I never realized that what DMX was doing on so many songs was barking…

What did you think he was doing? Coughing something up?

I had no idea that was a bark. [laughter]

He was just trying to DM us, on X.

Anyways, I’m sorry…

Oh, that’d be a cool new feature of X, if that was the DM sound anytime someone DM-ed you on X… It barks at you…

There should be like ringtones for DMs… You know, where that’s a feature.


Amal, can you make that song?

I mean, it was basically like [00:35:07.08] And I don’t know, I just thought he was rapping and making sounds; like, how am I supposed to know that was barking? That’s such a random thing. You don’t assume a human being is barking, you know what I mean? But alas, he was. I also have to say, for the React show, that was like my debut with that song, which I feel like has gotten so much general airtime, the dangerously set inner HTML…

Oh, yes.

You know what my favorite - and when I say “favorite”, I mean favorite-not - feature of JSX is? [singing] Dangerously set inner HTML… What’s so dangerous about HTML’s inner parts? I don’t know… [laughter] But they’re dangerous on the internet… Of React. React’s internet, of course.

[00:35:58.12] That was a really fun show. Yeah, Kball, you were on the opposite side. You were on the opposite team.

We were going at it. It was great.

It was great. We were just like one ridiculous argument over the other.

I love those Yep/Nope shows. They are so fun.

Yeah, they’re really fun. We should do them more often.

I agree. It’s difficult to come up with a premise that will be defensible on both sides, and not pylons… We’ve probably done five or six, and it’s almost like… I just can’t – like, whereas the JS Danger stuff I can just come up with new questions; it’s seemingly infinite. But with Yep/Nopes I can’t come up with the debates often enough. And so I’ve tried to have Kball help me… Maybe this is a good ChatGPT kind of thing, but if you’re listening and you have a good premise for a debate, just shoot me an email or hit me up in Slack… Because I would do these more frequently if we had good premises more frequently.

SQL belongs in your React components?

Yeah, I was gonna just say… I was literally just gonna suggest that as like the [unintelligible 00:36:58.00]

That’s a good one.

I’ll also say that we could probably reuse some of them, too… Because opinions change over time, and flipping sides, and…

Oh… Same debate, different sides.

Yeah. We could redo the React one, actually… Taking into account the new patterns, you know…

Chris, have you ever been on a debate episode? I feel like you have, but I can’t think of which one it would have been.

I feel like I was on one a long time ago.

We did one about “Should we rebrand JavaScript?” which was like because of Oracle, and because…

And I think you were on that one. How’d you come down on that one? I can’t remember.

I don’t know…

[laughs] “Don’t know, don’t care…” I think the answer was it should be rebranded as JS, and here at JS Party we are in full agreement that it should just be JS Party.

That was episode 101. We’re out of scope for today to talk about that episode.

Okay. Sorry. That goes way too far back. Let’s hear from our next listener… Somebody else who called in. This is Brian Zelip, who’s also been on previous shows calling in, so a familiar voice. Here’s Brian.

Hey, this is Brian Zelip from Baltimore, Maryland. Over the past 100 I realized the shows that resonated the most with me were co-hosted by Amal. I always look forward to her insights, experiences, questions, and especially her ethics. Some of my favorite moments included the ESM modules history, Web Components via Lit. The show with Alex Russell, the episode on Playwright, the !important CSS, and more. Thanks so much to JS Party and the whole Changelog roster for keeping an open, explorative and thoughtful discourse going. We really appreciate you. And I’ve already got a JS Party Tee, so please give mine to Amal if she doesn’t already have one. Cheers, y’all.

Oh my God, wow. That was – I’m blushing. Thank you so much. I’m kind of like the grandma on this show… I kind of [unintelligible 00:38:57.29] vegetable shows together, you know… It’s like, kids, we don’t really want to talk about our transition from CJS to ESM… But granny Amal is gonna force you, okay? [laughs]

This is gonna be good for all of us. Yeah, exactly. You’ll thank me later.

Yeah. Exactly. So that’s just my MO. I really appreciate it. And yeah, thank you. Looking forward to the next 100, I guess, right?

I feel like in some ways that goes back to your first episode with us as a guest. Weren’t we talking about TC-39? …which is another very vegetables show.

I was gonna bring that up. It was at Node.js Interactive, and Kball and I were talking to you about – I think at the time you might have been at Bocoup and you were writing tests for TC-39. Like testing things. And you brought such amazing insight into that side of the process, and… I just agree with everything that he said. It’s awesome.

Yeah, thank you, guys. Thank you. I love this show. It’s such a wonderful platform. You all are like such engaged listeners, and… It’s a wild industry that we’re in; the constraints are always shifting, the requirements are always shifting, the web platform is always shifting… And we somehow still have to kind of get things to our users, as well as professionally developed. So kudos to all of you for listening, thank you… And yeah, grandma out. For now.

That guy sounded like Steven Seagal.

Really? How does Steven Seagal sound?


Are you really as good as they all say you are?

Every once in a while…

I kind of want a voice like that…

Gosh, how cool would be if Steven Seagal had an alias that he used just when he listens to JS Party? [laughter] He calls in as Brian Zelip… That’d be amazing.

I think we need to get Steven Seagal on the show now, to help corroborate the story, you know?

Yeah. Confirm or deny.


Next up we have Chris Torres… Or is it? Or is it actually some other celebrity that poses as Chris Torres… Okay, Chris says “Console.log Hello World…” Nice intro, Chris. “This is Chris Torres, a web developer from Carson, California. Aside from the occasional Frontend Feud episodes, I love the playful banter between Jerod and Nick on the controversial topic of TypeScript.”

It’s not controversial… [laughter]

I beg to differ, Nick. I beg to differ. It clearly is. Listen to this; there’s more. “Apologies to Nick, but I am and always will be on Team Jerod.”

This sounds made up. I’m sorry. You’re not a real person. [laughter] Nice try, Jerod.

Oh… No, Chris says “I find it very entertaining and fun to listen to. Anyways, please bring back JS Danger, as I’m an avid fan of Jeopardy. It’s been forever since the last episode. Other than that, thank you so much for bringing me joy and awesome content every Friday. I truly appreciate it.” Thank you, Chris. We appreciate you writing that in. Yes, I do want to bring back JD Danger. I started to do more feuds because we had a nice formula of like podcast versus podcast… And because Frontend Feud is more communal, and less antagonistic. Jeopardy is one on one on one, and it really is how much you know… And if you go back and listen to those - I mean, I was under fire as the writer of those questions… Especially one time Suz and Emma were just coming at me… And I’m like “I don’t need this in my life.”

So the nice thing about Frontend Feud is it’s the people versus the audience, right? The ones who filled out the survey… They’re the bad guys. And JS Danger, I’m the bad guy, because they’re like “Why would you write a question like that?” And so I just shied away from it. But I do enjoy it… We have all the code we need to run the gameboard, so I will –

At least we agree that you’re the bad guy.

Oh, my gosh…

It’s also – I mean, it’s rude when I also win every time… So no wonder. I somehow ended up pulling it out. But yeah, I’m down to bring back JS Danger in ‘24. We’re unfortunately booked through the end of ’23, but in ‘24 I’m down for some JS Danger.

Yeah. And by the way, the fact that until this day Jerod still trolls Nick, and Nick still reacts like it’s his first time getting trolled… It’s pretty funny. It’s just such a Tom and Jerry situation… Jerod loves to troll, and I think Nick loves to defend, so it’s just like a match made in hell, really… [laughs]

My favorite part is how Nick declares it not a controversial topic, and then right after that he gets owned by the listener who agrees with me.

[unintelligible 00:43:46.09]

[00:43:53.02] Chris, please directly contact with Nick with some form of government ID and let him know that you are indeed real. Let’s hear from our next listener. This is William V, who says “I love the episode called “Spicy fonts and static sites”, where they discussed the awesome use Eleventy, and just kept talking even after the pod was supposed to end; it pushed me to want to subscribe to Changelog Plus Plus, which is better, I’m told…” [Changelog Plus Plus. It’s better.]

That one was cool. That’s Zach Leatherman. Of course we’re gonna keep talking to Zach… We’ve known Zach for many years, and it’s hard to stop talking when you get the three of us together, after a long time of not talking.

You know, a lot of these people, when we have them on the show it’s like the only time we get to talk to them, just because life is busy, and we’re all doing our different things… And so many times you’re like catching up with old friends, and then you feel obligated to talk about a specific thing, until the show is over, and then you can just chat… So that is a good place for our Changelog Plus Plus extended episodes. I can’t remember if that one actually had an extension on it or not. It must have… But that was a long time ago.

I was looking for it… That one’s even older than the last 100.

Oh, outside of scope…

But it was a good one. It was a good one.

You walked off the end of an array and now you’re in-memory…

I mean, we could be celebrating all 300. I feel like 300 is a pretty big milestone; it doesn’t just have to be the last 100 that are amazing.

Fair. Thanks for just bloating out our scope here. This is how feature creep happens, people… I’m just looking out for the user.

We just keep expanding. [laughter]

Can I give a shout-out to someone, or someones… I think it’s really been primarily one editor, but we’ve just got to give a shout-out to Jason, our sound editor, who’s fantastic…

Yeah. Heck yeah.

…and edits all our shows, makes us all sound way smarter… And just does a fantastic job. We throw him so many curveballs… Right now I’m in Amsterdam, using – if I sound crappy audio-wise… And otherwise it’s fine too, but specifically audio-wise, it’s because I’m using Pixel earbud headphones that I… Because I forgot to bring my travel mic, and I haven’t had a chance… But he’ll fix this up and make it sound way better. And so I just want to say thank you so much, Jason; we love you. You work really hard, and you’re a huge part of the show. So thank you.

Amen to that. Thank you, Jason. Alright, next listener message. This is from Mikhail, who says “My favorite recent episode was on the TypeScript wars.”

So yeah, I don’t know, should we pull up that tweet and read it out loud, Jerod? I’m not logged on to Twitter on this machine, and I will have to pull it up on my phone. But…

Well, I’m sure Rich has it open… You’ve got the quote tweet there…

[laughs] Yeah. Rich is like, “It’s embedded. It’s a feed embedded in my brain.”

[laughs] It’s his biggest mistake over the last week. It’s gotta be right there…

He’s like “I’m recording this podcast through Twitter, through an iFrame on x.com.”

So a little bit of context around – so David Heinemeier Hansson, he’s the creator of Ruby on Rails. He’s a very outspoken developer and business guy, quasi-professional contrarian, and he’s very good at taking a contrarian view… And he has a library called Turbo, which is a JavaScript library that helps your website go faster by basically hijacking anchor clicks and replacing them with Ajax non-full page refreshes. It’s a long-standing thing that’s on its eighth version; it’s gone through a lot of iterations. Actually, we use it, an older Turbo, 5 I think, on changelog.com. I’ve used it for many years. It’s decent software… And it’s an open source project that’s pretty much controlled and managed by him, and his company. And they took TypeScript out of Turbo; not the way that Svelte did it with type annotations, or with JSDoc comments, but just by actually removing it wholesale. And DHH wrote a blog post about why they did this, and he had a tweet about it, which Rich has now found, and I’m clicking on, which says “So farewell TypeScript. May you bring much rigor and satisfaction to your tribe, while letting the rest of us enjoy JavaScript in the glorious spirit it was originally designed, free of strong typing.” So that’s, I think, probably a pull quote from the blog post, as his typical fare is. So that’s the context. And then Rich… Do you wanna dunk on him again? [laughs]

[00:48:29.23] You should read this in your Jay-Z voice, or your Barry White voice. Either one, you know…

Hang on, I’ve gotta find my own tweet now…

Yeah, I liked the Barry White voice. That was good.

Okay, here we go. Do you want me to read out my own tweet?

Oh, I can pretend guitar…

Okay. So just, again, for context, a lot of people had already been attacking me… [laughter] This sounds like I’m an absolute psycho. Okay, okay–

It’s just like being forced with your bad decisions like the morning after… “I’m sorry, I’m sorry to make you read your naughty tweet on a large podcast…”

If I had spent a little bit longer on this tweet and thought a bit more about the reaction… I probably need to change some of the wording, but here we go.

Did you know that you were gonna be reading it out loud? I’m just kidding… [laughter] Anyways…

“Removing types from your own code is clownish, epically misguided behavior. But whatever, to each their own. Removing types from a library that other people have to use, however, is just user-hostile *bleep*.

*bleep* - is that even a word that we can…? That might even be censored. I don’t even know.

We’ll have to find out whether or not it gets bleeped… But it’s a great turn of phrase, I think.

This was the one that Amal refused to bring Nick on, even though I lobbied for him. I’m like “Come on, he deserves to be here. He needs to represent his side of the argument.” And she’s just like “No, I’m just – I’ve heard enough of him.”

I understand.

This isn’t manufactured controversy. Okay? Nick was invited, Nick was the first person I invited on that show… He just – you know, his body just chose the wrong time to get sick. So… He just wasn’t able to make it. But that was a good show.

I mean, the rumor was all the hubbub actually made him throw up, because his beloved TypeScript was so under attack that he was literally –

I was silenced…

…he just couldn’t even show his face. [laughs]

Now’s your chance, Nick… What would you have said?

Yeah, you tell Rich Harris how it is.

No, I listened to that show and it was great. I loved Rich’s take on it. He’s got a very level-set take on the whole controversy, and I thought it was great.

It was a solid show, and it was really great to be able to walk through that nuance with [unintelligible 00:50:38.09] and learn directly from him on some of the very nuanced decisioning, and also kind of the benefits of that decision for him and his team… It was fantastic.

It really did – like, he was the perfect person for that too, because he’s gone through the process of being in TypeScript, and switching back, and laid out the valid reasons for that. And I think it was different than the controversy at the time, because he still very much supports the end users of Svelte using TypeScript… And that is the most important thing. I understand why he wants a build step to be missing. That’s totally fine… Because it was like a double-build step in Svelte, right? And so that makes total sense. I thought it was a really insightful episode.

It’s a weird world, Nick, where the most important thing is that people use TypeScript.

Why is that weird?

But it’s your world, and I’m just living in it. Why is it weird? Well, because there’s other tools in the toolbox. Maybe not in your toolbox…

No, I think his point is it’s important that other people are able to use TypeScript. Right?

I know, but I’m trying to take his sentence out of context, Kball… And I don’t need your help to recontextualize things. I’m winning over here. I’m winning.

This is what I do. I put things in context. That’s my job…


Oh, my God…

[00:51:56.10] Kball… I have a word for you. It’s called buzzkill. You know, back in the day that’s what they’d call Kball, with the context… “Actually, guys, it’s not the correct context…” Okay, back to Mikhail’s message. So on that show I kind of went on a mini-rant about developer identity, and how we need to be able to detach ourselves from our tools, and float above the short-term… And to that, Mikhail says “As a new frontend dev, I love telling people why they are wrong for not liking the thing I was told to like.” So there you go…

Oh, yeah… And I want to say, Jonathan – I’m sure this is Jonathan Creamer, right? The Jonathan that’s in our chat, he just said that he loved the recent “The death of Node.js has been greatly exaggerated” show, and he said that it was so much fun to hear from the folks like Matteo… You had and provide context about what Bun is trying to do. Yes, I agree. And he also loved the show “Automating the pain away”, which he was on almost a couple years ago.

Oh, yeah. I remember that.

That was a really good show. John, we need to have you back, Jonathan. Consider this an invitation.

For 2024. Because unfortunately, we’re all booked out for 2023.

Let’s hear from Nelson. “Hi. This is that kid. One of the best pods was “Recreating Node.js” with Eric. The talk gave me inspiration to dive into the depths of Node. I’m not a contributor yet, but someday I will be. Thanks for the show.” That was a crazy episode. Kball, wasn’t that you and I interviewing him, all about how he recreated Node.js from the ground up? A simplified version…

I feel like that’s actually a key to becoming a good developer, and to going deep in all of these things. It’s like, once you get outside of the domain you know, it’s gonna be hard. There’s gonna be dead ends, there’s weird, esoteric knowledge that somehow has not made its way into the documents, or into ChatGPT, or into whatever else you’re using to teach yourself. And you’re gonna get stuck for a while. And you’ve gotta not give up to easy, and keep banging your head, and try changing your question or your search phrase until you figure out what is the weird thing that somebody’s documented in a blog post that wasn’t picked up by whatever, that gets you past that barrier.

It’s kind of like a video game… There’s two kinds of video game players. There’s the ones who get stuck and they’re like “This isn’t fun anymore. I’m here to have fun. I’m gonna move on.” And I totally understand that, because that’s logical. Like, if the goal is fun, and this isn’t fun - why am I doing it? But then there’s the kind of video game player that I am, where it’s like “Oh, I’m stuck right here. My life is gonna be hell for the next seven hours until I get past this level.” And I’m just gonna go over and over and over until I get past it.

Sometimes I feel like programming has been like that, for me personally, where I’m like “I’m just stuck. I don’t know my way out.” This is pre-GPT tooling, pre-lots of helps… And I’m like “Well, it’s me and the keyboard here. Let’s bang our head on it until we finally figure it out.” And it sounds like you’ve persevered through some of that yourself, Erick, in getting this thing out there.

Yeah. In my case there is always some voice here, there’s a reason… Because why anyone hasn’t done anything that you are trying to do, right? My video on recreating Node - there’s no content on the internet; so this is why I’m building blog posts, making a lot of stuff, to try to get more people. But when you’re the first, this is very nice. Like, “Oh, I was the first. Mad science.” I actually implemented the WebSocket protocol using JavaScript from scratch, like binary data, and a lot of stuff, because I was making questions… And this is very nice when you reach the point. But the path - oh, my God. You think “I’m gonna give up at some time.” Your mind is like “No, you shouldn’t do it. You have a lot of other stuff to do.”


[00:55:48.03] Yeah, it was a fun one. I think Erick does a really nice job of kind of breaking down these things that feel overwhelming and hard, and showing how they’re not that different from problems you’re probably already solving, and kind of building things back up again. So yeah, I love having folks like that on. It’s a really important skill, because I think getting into this industry now… There’s so many layers of stuff out there that it feels like you have to learn… And really, most of it is like applications of the fundamentals, in one form or another. And so kind of breaking that barrier of “Oh my gosh, this thing has been around for 15 years. How am I possibly able to dig into it?” and saying – you know what, it’s using the same things that you’re doing in your applications. “Let’s just look at how they’re applied here, and kind of making it accessible” is super-powerful.

Not to mention his enthusiasm for the content, and just all things is contagious, and he makes you want to go and try things as well that you otherwise wouldn’t… So we should definitely get him back on at some point as well.

Alright, last listener message… This is from Nathan P. “I loved the episode with Alex Miller, which focused on making web art through the affordances of grids and web APIs. The interview inspired me to start doing some creative coding in my free time. Some of my other favorite episodes were the interviews with Alex Russell and Evan You. I’m a big fan of JS Party. Thanks for all the hard work.”

Alex is getting a lot of love today. I’m gonna have to message him and tell him that. He’s at Web Directions in Australia… I don’t know why I said it that way, but I did… So – that’s so cool. And that’s amazing that you’re making art. Have you considered making it in an NFT? [laughs]

Good question. Good question. Well, that’s episode 275, with Amelia and I talking with Alex Miller, aka Space Filler, about indie web art and the work that he did, which was an essay/artpiece/coded thing called Grid World.

“The emptiness of a totally blank page intimidated me by demanding that I make the first move. But graph paper invited my participation by steering my pencil in the grooves of its strictly regular lines. The grid was like a friend who had already done half the work for me”, and I feel this exact same way, but I never really thought about it in those terms, of like “Why do I like graphing paper?” Or “Why do I hate blank pieces of paper?” Or an empty, white canvas that is a browser viewport before you’ve actually put some HTML onto it. And it’s like, there’s just – you can put anything, anywhere. It’s like the ultimate paradox of choice, right? But with graphing paper, with grid paper, it’s kind of just like “Hey.” It’s approachable. Here’s a starting place, right here where these two lines cross. That’s pretty poignant.

Thank you. Yeah, I think it’s something that I have thought about over the years…

I thought that was a really cool conversation. One thing about Alex that I learned on that conversation is that his dad made Myst, if you remember the game. Chris, you seem like the kind of guy who played Myst. Yes? [laughs]

You’re trying.

I am trying really hard. You didn’t play Myst? It was epic. It was a classic. It was amazing. It was the dawn of the PC video gaming era.

You know, I think at the time I didn’t have a good enough computer to play it. Because I remember it was very graphically intense. I might have had a CGA monitor at that point.


You can still get it and go back and play it. My kids have actually – I have one kid who’s really into puzzles, and my wife remembered Myst fondly from her childhood, and they went through it together.

That’s awesome.

It’s super-fun still.

[01:00:05.23] Yeah, it’s an exploratory puzzle game… And you’re trying to – almost like Escape the Room, because you find yourself in certain areas of this island, and you have to get to the next area, and you have to figure out some sort of puzzle in the area… And man, the satisfaction I just remember as a young boy finally figuring out how to do it, the order of operations, or what I had to put this thing in that thing… It’s just pure joy when you unlock the next section of Myst. For me, it was probably – next to Zelda, probably like the game that really turned me into a video game fanatic back in the day. So I thought it was cool just knowing the guy who made Myst’s son, and having a conversation with him, who is Alex Miller. And he’s doing cool stuff, too. So that was a very – I thought that was kind of a deep conversation. A lot about art, a lot about the creative process… And yeah, happy to hear that it inspired Nathan to doing some creative coding of your own. So… Very cool.

That’s really cool, Nathan. It’s really unfortunate that a lot of people – their only experience of programming is kind of “Sir, let me talk to a database and get things out, and show it on a screen”, or make an API… And there’s so much more to writing software. I would encourage everyone listening to this podcast and go do something creative. You want to do it the lazy way? Just go to scratch.mit.edu, and just use blocks to make a little game. If you want to get serious about it, you can look at – was it PJS? Or P3? Am I thinking about the right thing, the right library? It’s escaping me… We’ll put the link in the show notes.


No, not phaser.

It’s called P3…

Well, D3 too, yeah. You can definitely have fun with – the P3…


P5, sorry.

P5. I knew I had the number wrong. P5…

.js.org. Yes. P5 is –

Oh, my God. Okay, stop. p5js is a JavaScript library for creative coding, with a focus on making coding accessible and inclusive for artists, designers, educators, beginners and anyone else. So check it out. We’ll put a link in the notes; do something with yourselves, your partner, your kids, your friends… Don’t talk to a database, basically. Do something that’s not that.

Right. Do not create, read, update or delete anything. Just create. Just the C. Alright, well, those are our listeners’ favorite bits. What about y’all? What did you think of? What did you care for? What do you want to hear more of on the pod? What were your favorite moments, and why was I there? [laughs]

No, I think the real question is “And why was Amal there?”, because it sounds like Amal is–

It sounds like she’s the star of the show, doesn’t it? Amal, your response…

I mean, just – vegetable grandma. I’m just peddling vegetables, you know? And the good thing about vegetables is they don’t taste great, but they’re really good for you. [laughs] No, actually, they do taste great, too.

It depends on how you cook them, right?

Honestly – yeah, I think we’ve had a really great arc. I think, full disclosure, we’re definitely looking at expanding the panel. As you notice, we have a few people on our list that you don’t really hear from as much anymore; people who have had a lot of life changes… And so I’m personally really excited to – for kind of the next chapter of JS Party, as we expand the panel, get some new voices, hear new perspectives… Yeah, it’s this fun show where we get to kind of talk about the thing that we love so much. I mean, we’re so privileged… So here’s to the next 100, I guess.

There you go. And while we’re doing the vegetables analogy, if you roast certain vegetables, they’re amazing. Even the smelly one… What’s the smelly one? It’s green, and is in a circle…

[01:04:01.23] Asparagus?

No, circular green.

Brussel sprouts.

Brussel sprouts. Asparagus is the same exact situation, although asparagus generally tastes better than brussel sprouts when done poorly. Like, a bad brussel sprouts - awful. Like, just steam it and it just smells like a foot. And then you’ve got to put that in your mouth? It’s like, I don’t like feet my mouth. But roast brussel sprouts, roast asparagus…

That is not a universal truth, Jerod…

This is just one man’s opinion, okay?

Okay, just putting it out there…

Are you saying we need to be roasting Amal here?

Oh, my God…!

Yes. The more you roast her, the better it – no, my point is that when you take something that’s good for people, good for your health, good for your career, good for your life, and you present it in a way that makes it good to digest, you like it, you like vegetables - like, that’s a win/win, right? And I feel like, Amal, that’s what you do with JS Party; you take these conversations like the history of ES modules - “Boooring… Don’t care… Why?! What’s the point?” And then it’s like “No, this is good for you to know.” You may not even know it yet, that it’s good for you to know… And the way you do your conversations, the way you host the show… You make it taste good, and enjoyable. And so it’s not like dry, and boring, and smells like feet.

No, it’s like Mr. Robin had a baby with… What’s that guy? The funny one…

Tim Robbins? Or are you thinking about Mr. Rogers?

Mr. Rogers, sorry. Mr. Rogers had a baby with – what’s that guy? Is his name Peewee Herman, or something?

Yes… Both these men are dead, so this is going to be a bit strange…

Okay. And then they had a third baby – they had a third partner who contributed to the baby. That was – I don’t know, who do I…? Oprah. [laughs] Let’s go with that.

Oprah. There you go. Okay, so Oprah meets Mr. Rogers meets Peewee Herman, and talks JavaScript.

That’s me. I was gonna say Steve Jobs or something, but he’s kind of mean, so… Yeah, so I went with Oprah. But yeah, I don’t know…

There you go. Put that on your LinkedIn.

Oh my God, that’s what I have to work on this week. I have to work on my LinkedIn. It’s like really outdated. I don’t use it.

Oh, boy. Ask Kball. He’s been working on his LinkedIn.


Not now. I mean, you’ve got a job now. But whenever you were between stuff, you had to work on your LinkedIn, right?

I was posting things on LinkedIn. Yeah, I still post some things…

Yeah. My job was recently impacted by restructuring. I don’t even think anybody here knows this, besides maybe Kball.

[unintelligible 01:06:31.13]

I think you do. Yeah, Kball does. Yeah, so not that I even want to be on the market again, but I will be. I’ve decided that I’m leaving, I’m not going to do an internal transfer… So it’s good times doing that, that whole dance… Yeah, I know. It does suck, but also, change fuels the soul, I guess…

So yeah, I figured “Okay, well, I guess I should have an updated LinkedIn profile.” Start there.

I don’t know about you, but I find that whole process kind of bizarrely fun… Because you get to talk to – I don’t know, I geek out on companies. Maybe this is the entrepreneur in me, but I geek out on “Oh, how are you setting up your business model? And what are you trying to do?” And so interviewing places is kind of a chance to get people to tell you about all their different dirty laundry, and how – they’ll probably just show you the clean laundry, but the ways that they’re approaching things… So you get to talk to a bunch of companies and be like “Alright, well, how are you doing this? How are you setting up your dev process?”

And how does LeetCode prepare you for that?

I have never once in my life done LeetCode. LeetCode to me is teaching to the test, right? It’s like the equivalent of studying for your SATs. There is some correlation between your LeetCode performance and how well you program, but when you study LeetCode, it is not helping in how you’re going to do you regular job, generally. And there are people who are good at LeetCode, and good at software development, and generally there are people who are bad at LeetCode and good at software development, there are people who are good at LeetCode and bad at software development. That whole spectrum exists.

[01:08:10.25] So yeah, it’s – I mean, it can be worth it if you… If you are bad at taking the test, where the test is software development interviews, particularly at companies that like to do LeetCode style, but you are good at software development; it can be beneficial for you to spend the time studying LeetCode, so that you can ace the test, so you get into the real work. But God, it drives me bonkers that that is how so many people run their interviews.

[unintelligible 01:08:38.06] for applying to jobs right now. Applying to jobs online sucks. Everybody’s got 5,000 applicants, and they’re machine-parsing them and scanning them… Always get a referral, which - you probably know that, Amal, but I’m surprised by how many people I’ve talked to that don’t realize that. Getting an internal referral is a low-barrier thing. Most people will just do it. You can reach out to people at the company and be like “Hey, can we talk for a little bit?” They get to know you, they realize you’re a real person, you’re okay, and you could say “Would you feel okay referring me into this position?” It just gets you past the machine parsing, so you can actually talk to a human being, which is what the point really is.

Yeah, referrals for the win, for sure. Yeah, I think for me it’s like – I’m just kind of trying to decide where I want to land. It’s like, every place has its own set of problems. You just have to kind of decide on which ones you’re okay with living with, and which ones you want to try to tackle. Because you’re not gonna be able to fix everything. So it’s like “What problems can I live with, and which problems am I interested in trying to kind of drive change for?” So… An interesting time to be back on the market, but feeling of oddly optimistic, I think. So hopefully I end up in a good place. I’m really looking to kind of – I’m looking for kind of like my retirement job out of tech right now. It’s kind of weird to say that out loud, but I just – I kind of have like eight years of like wanting to work at a corporation… So eight years left in my tenure plan, and… So yeah, I don’t want to be working for a corporation in eight years, so…

Well, if anybody out there is looking for an awesome – are you looking for manager jobs?

Engineering manager, yes.

…yeah, an awesome engineering manager - I hear a rumor. Amal is going to be on the market. So maybe jump the queue and reach out to her.

Yeah, great job.

Well said. Nick, any thoughts from you on the last 100 episodes, on the next 100 episodes, anything that’s not vim or TypeScript-related that you’d like to say before we call it a show?

Why do you have to box me in like that, Jerod?

Because you’re just so predictable, Nick…

[laughs] I will say, one thing that I’m really excited about – or one of my favorite types of episodes or segments that we do, that I feel like might be going away, is the Explain like I’m Five piece. I think that those are so fun, and the stories that we come up with, and tell, and all of that… But no matter how we do those in the future, it’s always tainted by “Well, AI could have generated this.”


It can generate it pretty well. So the creativity is always in question there.

Are you tipping your hand, or what are you saying here?

Oh, no.


I don’t know, I feel like when we try – I tried to get ELI5 to reproduce your Mawana story…

Monad’s hook…

Monad’s hook… And it was so much worse. I think you have a future in ELI5 for as long as you want it, because AI is not taking that level of creativity away.


Well, thank you.

As long as you stay excellent, Nick… Because all of its stuff is very average. And you’re excellent. So…

Yeah. I eat my vegetables and write my TypeScript.

No, I said don’t talk about that. He snuck it in. Do you see how he snuck it in?

ELI5 Jerod trolling.

B0neskull? What would you like to do more, or hear more, or see more of JS Party in the next 300 episodes?

[01:12:02.29] So I was gonna bring up an episode, but it is too old…

No, Kball expanded the scope, if you want to.

Yeah, I’ll bring it up anyway. So when we had – I really liked the episode when we had Luis Villa on to talk about Copilot. And I would love to have more talks with that dude. Because it’s incredibly interesting, if you’re doing open source, or have interest at all in any sort of licensing, that sort of thing, he’s just fascinating to talk to. I don’t know if he’s doing – I think he retired from talking about open source licensing, and now he’s looking at AI or something now… But yeah, very interesting guy. And definitely those topics, I think, are maybe more underserved. Certainly we talk about tech, and we goof around on the talk shows, but there’s this whole licensing thing, it’s just kind of a topic that I like to talk about. But yeah, and I think it’s useful.

Yeah. Actually, on that note, “What’s in your pkg.json?” I don’t know if that was in top 200, or – I don’t know what number that is.

But that was a personal favorite of mine… As was the recent show that we did with Matteo and James Snell, the Node show. That was fantastic. Yeah, I’m just trying to think of recent ones. And then we just – it’s not published yet as of today, but it will be by the time you’re hearing this… We just did a really great show with Valerie Phoenix, on Tech by Choice, an organization that she started to help marginalized folks enter, stay, thrive in tech… And it was just fantastic. It was like such a real talk show. I thought that was like – Valerie kept it very real, and I hope you all enjoyed it.

Okay, we’re gonna try to take a real-time listener call, as we’re using shiny, new features of web-based tooling… We don’t necessarily expect it to work, but if it does, this will be a first for JS Party, with Jonathan Creamer from the chat.

Thanks for calling in. Your very first live caller-inner.

I’m excited.

So cool.

Yeah, this is rad.

What are you bringing to the party? We’ll put you on the spot. What have you got going?

Yeah, I’m at Microsoft now, since we last talked, and… You know, I’ve been enjoying that for a while now. And still listening to y’all all the time… That Bun episode - that’s what I called out in the chat - was so good that I shared it everywhere I could inside the Microsoft teams network that I have, because I thought it was just awesome.

The one with Matteo and James? Yeah, that was solid. Agree.

Yeah, the one with Matteo and James, exactly. Yeah, it was so good, and it was prescient, because everybody inside all of our team’s chats was talking about Bun and everything, and I was like “Hey, guys, listen… Just listen to JS Party. You’ll understand what’s going on. Don’t freak out, it’s okay…”

And they dropped so many gems, Jonathan… I listened to that episode three times, because there was so much that they dropped. It was just gem after gem after gem… It’s like, man…

Yeah, yeah… I felt the same way. It felt so good to hear from them. Because it was like - yeah, you talked about Bun, but then I also learned about how the Node.js ecosystem actually works, and all this cool stuff. So I thought it was really great. Yeah, that’s what I’ve been up to, just doing my same DevOps stuff that I’ve been doing. [unintelligible 01:15:49.29] who you guys had on the show, another old, old episode… He and I were just at Connect.Tech in Atlanta together, and we were talking about that DevOps stuff. He actually keynoted on DevOps, which was pretty cool, to about 400 people…

Because I think you guys had him on first, and then me after that, and so now we’re talking about like partnering up on some more, and doing all that…

[01:16:13.23] Yeah, you’re both overdue to come back, you and Ben> I spoke with Ben more recently, and Ben is like “Yeah, I’d love to come back.” And obviously, you… So you have an open invitation… But we’ll have to coordinate with you at some point.

Yeah, definitely. It could even be fun if we both did the same episode together. Yeah, and talk about DevOps, and automation… Because his keynote is basically about – we love the idea of DevOps, and helping people understand frontend developers who don’t do frontend… And it was all about all the different crazy tools that we use to do frontend stuff, even though we’re not technically like writing JavaScript all the time to do that. We’re doing Docker, and blah, blah, blah, and blah, blah, blah, blah, blah. But yeah, that’d be great. I’d love that. 2024. Let’s get it. Let’s get it.

There you go.

That’s great. I mean, I love this idea of combining guests, because our schedule is such that, you know…

Yeah, kill two birds with one stone.

Yeah, that’d be super-fun. Kind of panel style…

No birds are injured during the killing.

Well, thanks for having me. Let me jump in here. I don’t want to kill the party, but I wanted to say hey, and how much I still love listening, as both a caller and a speaker on past episodes… It’s such a great podcast. Y’all keep up the good work.

We love that. Thank you, Jonathan. Appreciate the call.

[unintelligible 01:17:28.15] the best listeners…

I’m just happy that worked very well. I think that this may have opened up a new idea for future JS Parties, right? Live call-in shows. We have the technology now… Talk to more listeners, man. Just take some questions. Take some comments. Hot takes, warm takes, microwaved…

Yeah, but for Changelog Plus only… [laughs]

Plus Plus. Come on man, you’ve left a plus off of that. Was that on purpose?

No, I just wasn’t sure how many pluses it was… [laughter]

Yeah, I think for you one Plus is about appropriate. You’ve gotta increment that sucker. It’s an increment operator, Chris. You know increments…

That sounds like a good point to toss to Nick for the final word of this episode 300. If you do anywhere near the world you did last time I put you on the spot, we’ll just have to close early. But Nick, I mean, here we are, episode 300, we’re at the end of it… We have huge plans in ‘24. We now know we can take live calls. We have games, we have debates, we have deep dives, we have vegetables… There’s just so much that’s going to happen. What would you like to say as we close out our 300th episode?

Coming soon in 2024… In a world where Ruby on Rails is no longer cool… Jerod tries Typescript, and he loves it! And he comes and says to Nick “Thank you…”

[laughs] Oh, that was spectacular. That might actually get me to do it. Probably not… Alright, that is our show. Thank you all for listening. Thank you especially to our listeners who took the time out of their busy lives to write us a nice note, to record us a nice message, or to hang out in the chat while we record.

We don’t do these things on YouTube anymore, and we’re not keeping a set live schedule like we used to, every Thursday at 1pm US Central. It’s not like that. 1pm US Eastern actually it was… We’re not doing it like that anymore. We’re giving ourselves a little grace, a little flexibility… But we are still sharing the link to the Riverside now, with our JS Party channel in Changelog community Slack before we record. So that’s pretty much as far as we’re going to be putting it out there. That being said, it’s still fun to hang out in the chat. Hear us record live, hear all the times I mess up, or have to cough and start over… And be part of the gang. So if you are interested in that, head to JSParty.fm/community. It’s totally free, sign up, and hop in the JS Party channel of our Slack to discuss with us throughout the week, not just during our shows, but whenever something interesting… Even join the #funny channel, where Amal tries to be funny daily, maybe even multiple times a day, with fun posts of other people’s memes…

I was gonna just plug #funny.

You were going to plug that?

We’re the fastest-growing channel in the Changelog community Slack. Almost 30 people strong, you know…

[laughs] Okay, so let’s get those numbers up, folks… We’ve gotta keep going up and to the right of the funny channel.

We need the hockey stick, like any good new tech thing.

Alright. For Kball, for Nick, b0neskull, and Amal, I’m Jerod, this is JS Party, and we’ll see you on the next 100 to 300 episodes.


Our transcripts are open source on GitHub. Improvements are welcome. 💚

Player art
  0:00 / 0:00