Three... Two... One... HAPPY NEW YEAR!! \[laughter\] Spectacular welcome to 2024 from your friends at JS Party. I'm Jerod, and I am here with Amal. Happy New Year, Amal.

Happy New Year, Happy New Year. We're having a little too much fun already. Let's just put it this way - this show was supposed to start 30 minutes ago, our recording time anyway... So we're like -- we've just been \*bleep\* about, so... Happy New Year.

We are going to have some fun today. Kball is also here. What's up, Kball?

'm celebrating, and I just learned I have a built-in kazoo.

Maybe even better than b0neskull's, who had a kazoo that he brought with him... Because that's Chris. Hey, Chris.

Hey!

Thanks for bringing that kazoo.

You're welcome.

Happy New Year, man.

Yeah, it's really exciting to be in 2024 right now.

A-ha. So exciting.

The excitement is palpable. \[laughter\] Nick is here as well... What's up, Nick?

Ahoy-hoy. New year, new me. I wear sunglasses now.

He wears his sunglasses at night... So he can, so he can... Throw TypeScript shade... \[laughter\]

Shameless for not using Neovim...

Yeah. Right, right.

Well, you have arrived at our fifth annual JS Party New Year's celebration. This is a fun way that we like to kick off what is this new year, without us knowing what is this new year. We're going to guess; we are going to reflect a little, we are going to review past predictions, we are going to perhaps cast forward some predictions, and maybe talk a few of us into being so foolish to make resolutions right here for everyone to hold us to account. So that is the plan. Where should we start? Should we start with a quick lookback at last year's predictions and see how they held up?

Let's do it!

I was just looking back... I definitely missed it. But maybe I should re-up it.

Yes. Kball's big prediction - in fact, this one was so bold that it turned into a bet, I think, amongst participants... Twitter is gonna go into bankruptcy in '23. \[laughter\]

Wait, wait, had Elon taken over at that point? I can't remember.

He had. He took over in, I think, November of '22, and so we were right during the big hubbub, and multiple organizations were suing Twitter, and he had laid off two thirds of the staff, or whatever that number is... And Kball thought this couldn't possibly continue forward, and yet here we are, a year later, and not bankrupt.

Well, but Twitter is dead.

Not his prediction. His prediction was Twitter will go bankrupt. Actually, Twitter will file for bankruptcy. He should have been more vague; he should have been much more vague.

Twitter will be dead... Yeah. I mean, I think it's a reminder of a variation on an old thing... There's this saying that says the market can stay irrational far longer than you can stay solvent. In this case, it's Twitter is staying solvent far longer than seems rational.

There you go. Would you like to -- well, I guess Feross would be here to be on the winning side of the bet, but he's not here, so I guess he's still is a loser... Sorry, Feross. \[laughter\] Would you like to re-up it? Would you like to double down, maybe go all-in twice and say by 2025, by the end of 2024...? Or do you think at this point you're wrong?

What was our wager? Did we have a wager?

It was like internet points, or something...

Okay. Well, I'll go double or nothing on my internet points, for sure.

\[laughs\] Okay. Alright. So we'll see you here next year for Kball to eat crow another time. I think it's going to just continue along. You know, things tend to go slower and steadier. Maybe Elon will land this plane in a controlled fashion. Who knows? Call back to the pre-show. Amal, what do you think? Do you think Twitter's going anywhere? X, f.k.a. Twitter...

Honestly - so I have very close friends of mine who judge me on the daily, whenever I send them links from Twitter... And I can basically hear their eyeroll. I'll text them a link and I could hear the eyeroll on the other side, like "Oh, are you still on there? When are you gonna get off?" And here's the thing, I was off. I was off for almost two years. I just came back a few months ago, and... I think I've been having fun. It's definitely a lot different. It feels like an echo of itself. It's not the same platform from 2018, where I think for me tech Twitter kind of peaked... But, you know, it's still the fastest way to get news and reach out to people and share information. \[00:06:06.05\] I mean, real talk, I just -- I just needed help from someone the other day on something; this person is like a really big deal on the internet, and I was like "This person is uniquely suited to help me with my problem", and I literally reached out to them, and in two minutes they responded back to me, in 30 minutes we were having a conversation on our cell phones. I mean, it was that quick. And so I feel like we're still -- I don't know what's going to be that when it comes to kind of news connection and information.

Yeah. There's still value there.

Yeah. But -- yeah, do I need to feel like I need to take a shower after using Twitter? Sometimes yes. But am I going to stop using it right away? I think I'm gonna maybe go down with the platform; that might happen for me. But we'll see. We'll see.

Yeah. I always thought Twitter was a cesspool from the beginning. So for me - you know, does it feel different? I thought for like a while it did; it was like it was too much about the main character being Elon Musk every single day, and I feel like that started to fade slightly, perhaps. And there was -- too much Twitter was talking about Twitter for a long time, and so that was annoying... But I feel like as that kind of settled out, and it seems like "Okay, it's going to kind of continue on..." It's still the place, I think, where the big stories are broken and talked about first. For example, the whole OpenAI Sam Altman debacle, that five-day drama, it pretty much unfolded on Twitter. Now, was it valuable for all of us to be part of that? I don't think so. Did we gain anything there? No, but that's really where the story unfolded, so it still is a bit of a gravitational pull for stuff like that... But it was always for me trashy, and so now it just feels like more trashy, but I was already ready for it, so I find value where I can find value... And I roll my eyes, maybe more than I used to.

I was wearing high heels over the trash. Like, I felt like that bougie woman that was wearing a fur coat and some high heels, and like stepping over trash, like "Ew... Get out of my way." Like, that's how I treat Twitter. I definitely am selective what I engage with and who I follow... And you have to really curate it heavily. Otherwise, you will go nuts. There's a lot of triggering stuff there. It's meant to be triggering; the whole point of the platform was to invoke rage.

Yeah, exactly.

But yeah, you were saying, Nick...?

I said you definitely grok it as a callback to the --

Oh...

\[unintelligible 00:08:31.26\]

Good one.

Oh, my God... \[laughs\]

You know it's a good callback when you have to explain it.

For the record, for everyone listening, Nick is still wearing his sunglasses...

I don't think he has any plans for taking them off.

Well, he was rocking out like --

They look like EDM DJ Ultra Music Festival sunglasses...

The best part is I can see myself in his glasses now, so now I'm staring deep into his eyes...

I can see the whole monitor reflection... \[laughs\]

I'm very aware of what's on my screen now...

Yeah... \[laughs\] We can tell when you're not paying attention.

Well, Nick's jokes may crash and burn, but his prediction from last year wasn't as bad as Kball's. Nick predicted that we have Bun, we have Deno, we have Node... His prediction would be that Deno and Bun end up making Node better, rather than one of them supplanting Node. What do you guys think of that prediction and how that's played out this last year?

I have so many thoughts on this... Yeah. Like, I just want to say, Nick, that was a really good prediction. Congratulations.

Thank you.

"Congratulations..." \[laughs\]

That is definitely happening. I'll actually link to some discussions on Twitter, the forbidden platform. We'll put some links in the show notes to some conversations I was kind of a sidecar on, where this exact thing happened, where Jared was like --

Jared Sumner.

Yeah, Jared Sumner, to be clear; not Jerod Santo.

Just for clarity purposes.

\[00:09:55.13\] Yeah, Jared found this area of Node that was slow, and then the maintainers were like -- or I take that back. It wasn't that he found it, it's that somebody when they were doing benchmarking found this new area... And then the maintainers looked into it, and it was like "Oh, it has to do with some old dependency that hadn't been updated", and yada-yada-yada. It's just fascinating how these discussions are happening in the community now, and Node is getting better as a result... I'm very, very happy about that.

Chris, your take on this sentiment. Do you think it's true? Are you happy about it? You're a -- I think of you as a Node guy. I'm not sure if that's the right way to think of you, but I very much associate you with Node.js. What are your thoughts on this?

Yeah, I mean, I think the same thing is gonna happen; you know, after Yarn came out, it pushed Npm to add some features and stuff that it didn't have... And it made Npm better, and I think the same thing is gonna happen with Node.

I agree with all of that.

Of course you do, it's your prediction.

And this is why it's good. It's healthy. It's so healthy. This is what you want. Otherwise, you have stagnation. I think competition is really healthy. So it's important for us to kind of have that...

Absolutely. And there's a lot of new cool things coming to Node proper, that have been in Bun or Deno before. One that I can think of off the top of my head is specific permissions. You can disable networking, or disable file system access, probably... And that's something that Deno - like, that was there from the outset; you can only run this in a secure way, and get access to the things that you need access to, and nothing else. I think that's really cool. And there's a huge push towards more secure Node modules, too. Or maybe that's just the Feross propaganda in the back of my head...

\[laughs\] Very true. I agree with all that. I think it's kind of cliché at this point, but competition breeds innovation, and lack of competition just creates stagnation... And it's awesome to see new entrants come in, and projects get a new reason to do awesome things, and new ideas, like "Oh, we didn't think about doing it that way", or "We have these constraints, you don't. Maybe we could change one of those and modify that we work to get 80% of that, versus the 100% that you have." But it's all good to see. Whether or not Deno and/or Bun will actually gain a significant foothold on like user base, I don't really have much prediction there. I think probably Bun has a better shot, because Deno's more different... But gosh, who knows? Time will tell. And Node has such a huge user base right now that it would be an upstart browser trying to take browser share from Chrome... Which could happen, but...

The Bing versus Google Search analogy I think is \[unintelligible 00:12:43.01\] in terms of scale. Most projects in the wild use Node, period, for lots of different things.

On some of the shows this year, when we talked about these different things, one of the things we talked about is that you don't have to have Node versus Bun in your decision-making. You can use Bun in particular parts of your deployment, where performance is particularly important... And other deployments that are more focused on backwards-compatibility, or need certain features that it doesn't implement, just don't use it. It can become a tool in the toolchest without having to supplant Node.

Yeah. I do have to say though, for me as a tech lead - or former tech lead at this point - I would say the fear I have when I hear about that is it just kind of... Like, I think really hard about introducing new things into my stack, and what's the benefit that you get versus the cons... And for me, the cons usually outweigh. And so if I can get 80 with the existing tools that we have, then it's worth the compromise, because there's lots of other better ways to spend that engineering time.

Not to cross-promote here... I don't want to cross-promote things that Jerod does, that aren't TypeScript-related... But that episode of Changelog & Friends with Searles about - I think it was It Dependencies... It's gotten me constantly thinking about "Do I really need to add this new dependency?"

\[00:14:05.13\] Oh, I love that.

That's good.

Yeah, that was a great show.

I have to listen to that.

I love that we have you thinking that way. I think it's a healthy way of thinking. It doesn't mean you don't end up adding it, it just means that you stopped to consider it, and you weigh the pros and cons, and you think "Hm... This has a total cost that I need to consider before I add it." And maybe you end up doing it anyways, but at least now you're taking intentional steps with your codebase.

Yeah. And I think for me, just again, to give some more context to where my kind of extreme trepidation or what seems like a very conservative answer - I'll give you some context... It's not just me and my team and my engineers that have that cost. It's like our ops team, our security team... There's a huge ripple of people in different parts of the company that are impacted when you introduce large new technology into the stack. So I just want to put that out there. Like, it's not just devs. It's SRE, it's ops, it's security... And for teams it's platform teams, it's all kinds of stuff. So just think about it that way.

Yeah, I would also strongly consider the licensing and ownership of the project... Because stuff like Bun and Deno, they could pull those permissive licenses if they want, right?

Yes.

And there might be an incentive or pressure to do so... Which if you're a small company, maybe you're not going to be able to afford it, or something. And so you've really got to be careful about the "Where does your open source come from when you're picking open source?"

Yeah, well said. We've definitely seen prior art now, of that not just being a hypothetical situation that may happen to you. It's actually happened on more than one occasion of a relicensing of a majorly dependent upon open source software, until we're suddenly - everybody needs to sit down and decide how are they going to forge a path forward given these licensing changes. So it's no small thing, even if it's a small package that you rely upon. Well, let's now turn the focus to me. I had a prediction last year; I don't know, you guys be the judge. I feel like it's kind of happened, but not 100%... I predicted - and remember, this was the end of 2002. We'd just had the Twitter takeover, we'd just had Chat GPT end of November. The AI Revolution had begun. The buzz was peaking. Maybe not peaking - it's gone higher since then - but what I said was that I felt we would see AI plateau in the second half of the year. I thought it would continue to improve, but not at the same pace that it had improved up until then. I specifically said we'll still be writing our own code this time this year. What do you think? How did I fare?

Well, according to the advertisement that I see constantly on GitHub, they're not writing 55% of my code.

\[laughs\]

I thought it was 40-something last time I checked...

I've seen that one, too. They're really shoving that...

Maybe they're A/B testing that number...

\[laughs\]

Well, no, no, I heard that 40% of code on GitHub now is generated by AI, but I don't know if that's actually true. That sounds ridiculous if that's the case.

Oh, you're right. It says "Make me 55% faster."

That's cool.

I think there's probably a research study that went behind that number, but I think other numbers are most likely misinformation flying around at a pace... Because it's very popular right now to tell people how good you are at coding, now that Copilot's writing your code... But I don't know, most of the demos to me don't look like they could stand \[unintelligible 00:17:25.11\] for more than the 30 seconds they were recorded on...

70% of the time it makes me faster 100% of the time.

I was gonna say, I definitely experimented with some of that, and took it out of my config, because I did not find it overall sped me up.

Yeah, same here. I think for me it's only useful for boilerplate code. Other than that, I'm always refactoring around it. But it's really great for learning a new language, or a new tool, which is how I've been using it... Because I'm learning C++. I learned it a long, long time ago, and I just blocked everything I knew out of my brain... So I'm relearning that; so that's been helpful.

\[00:18:07.25\] I will put an asterisk on that; it is really good for learning an old tool that is new to you. If you try to use it to learn an actually newly developed tool, it will mislead you all over the place.

Yes. Lack of data.

Yeah, lack of data. Right. But no, I think for me it's been a good learning aid, but when using it in a context where I'm an expert, it's only useful for boilerplate code, or helping me come up with regex'es, which is how I've also been using it quite a bit.

Now, are y'all talking about specifically Copilot, or are you also lumping in like talking to ChatGPT, or Bard or...?

Both.

I find ChatGPT to be more useful as a "person" that I go ask questions to, versus anything that generates code in-line inside my editor. When I started type, even - I've never been a huge fan of IntelliSense, which I know makes me like a very small minority of developers... It's great if you're trying to know what functions are available in this scope. I like it for that. But anytime I'm like halfway typing something and stop, it's not usually because I'm trying to figure out, it's just because I'm pausing my brain... And then what I've found specifically with Copilot, but I've also tried Cody, and Tabnine - this was probably two years ago, so I'm not sure the current state of Tabnine. If I do it that way, it just puts out like "You should autocomplete this", and it's almost never what I want, at least... Even if it is, I'm stopping and then I'll think about code that I wasn't caring about before, and now I'm like thinking about something else. And so it takes me out of my flow. And maybe that just takes time to get used to... But I like to go somewhere; instead of going to Google, almost 9 times out of 10 I will go to ChatGPT and say "Write this regex for me. Write this \[unintelligible 00:19:46.25\] And for that class of problem, where I already know how to solve it, I just don't want to, I find it to be a big productivity boost. But I'd rather go to it than have it integrated. You guys?

That's 100% where I find the benefit of Copilot. Like you said, it will generate crap. And then I feel like it pulls me out... Because I already know what I want to write, and it's trying to help me by autocompleting that... But then more times than not, it just -- I have to pause my train of thought, read over what \[unintelligible 00:20:14.24\] and then either decide yes or no. And if it's not right, then I have to get back to my train of thought, which is not always foolproof...

Right...? Failsafe?

Yeah. But the only place where I'm totally like "Yes, just generate, and I will accept yours, and then try and tweak that from there" is unit testing. It's actually pretty darn good at generating unit tests.

Absolutely. Agreed on that.

Makes sense. If you're into writing tests. Chris, what do you think?

Yeah. I mean, I've I think I've had good success with Copilot. I haven't tried to use ChatGPT directly for coding, but it's cool that they have -- I don't know what they do now, but it has some sort of understanding of the project you're working in. And so I would be like - I'd select this class, and be like "Okay, refactor this class in this particular way", that would be tedious to do manually, and it does it. And it uses my types, and everything; it tries to keep the same style. And with unit tests and testing in particular, it knows I'm using a weird, a non-popular, just kind of an obscure assertion library. But it knows all the assertions I've written before, and it's able to figure out what to use. So it's not like I'm asking it to write unit tests and it's going and using try syntax, or \[unintelligible 00:21:45.06\] syntax, or something... Because it doesn't; it knows what I'm using in it, and it does it correctly four out of five times.

\[00:21:55.02\] I think this is kind of the natural process of maturation of a new set of capabilities that was developed, and we're trying to learn the best ways to use them. And I think, for example, writing unit tests, doing other things - like, that is a productivity boost. I do think there's a lot of hype cycles around the productivity boost that you get from writing new code, that I think are baloney... I don't think it's actually -- I mean, to Amal's point, it's really useful when writing boilerplate. And if you're writing a set of boilerplate scripts, or you're trying to do little things to push data from one service to another, I think it is a dramatic performance boost there. I have definitely seen, particularly like a junior using code completion, and then getting things where it has to go through many cycles of review and feedback, because it's not matching styles, or other things from the rest of the project... And I think it's a performance cost. I mean, I think we need to figure out where it's useful and where it's not, but some of that is getting past the hype cycle and saying "Okay, it's a useful tool in these scenarios, and it is not a useful tool in these other scenarios, and we should stop trying."

Yeah, yeah, absolutely. I couldn't agree with you more, Kball. And thank you so much for bringing up the juniors thing, because I have thoughts on this, Jerod, which I really want to share on air... So I'm really, really concerned about the arc of our junior engineers, actually... Because I think remote work has been terrible for them. I've managed and led junior engineers in this remote environment, and trust me, it's not the same as being in an office with them, where they can just walk over to you, and they get that ambient learning from their team. So I think remote work isn't the greatest. It does provide access to work, but it's not the greatest when you are very -- you know, in the first one to three years of your career. The other thing is, AI - I look at tools like \[unintelligible 00:23:50.24\] VZero from Vercel, and all these other kind of code generation AI tools that are specific to kind of developing UI components, etc. - this is fine. I mean, this is the work that - listen, as somebody who has been in this industry for, I don't know, 10 plus years, I don't want to... This is not work that I want to do. This is actually work that I have not been doing for years. I can't remember the last time a company paid me money to make a component. You know what I mean? Like, I'm managing infra, and architecture, and all these other things... And who's writing components? Our junior engineers. They're learning the ropes, they're doing the gruntwork, so that they can kind of get their reps in, the repetition, so that they understand how these systems are connected together. They're the little building blocks, right? And so I'm just really worried about what does the future look like for them? How are we going to have -- are we going to even have junior engineers? Because AI is doing the work of what I would consider junior people, and I think starting at a higher level of just -- I don't know; I don't know if that is really doing them justice. I don't know. Maybe this is an irrational fear, I have no idea... But I'm just saying I'm worried.

Amal, you have nothing to worry about, because the AI companies have this all figured out; if you ask them, there won't be any engineers in five years. So... Problem solved.

Oh, gosh... I'm just saying it's a concern, you guys. And this is an us problem, it affects our industry; we should be figuring this out, and making sure we have a path for people at all levels, senior to junior. And I just want to make sure that people can progress those paths in a way that is conducive, and healthy, and sustainable. And I'm not saying that even being a junior engineer -- some people get through junior in six months, and they're done. And they've moved on to mid. Some people are there for a few years. So it's not even something that's like a universal standard, or timeline, or whatever... But I'm just saying, I just want to make sure that we have a path for people to learn, effectively, so that they can manage these complex systems. And when things go sideways on the AI written code, they know how to debug at 3am, if they need to... Because that's what happens. Incidents happen.

\[00:26:01.16\] Well, I think I'm with you. I think that thinking back to when I was a junior, I didn't know how to debug at 3am either, until I had to debug at 3am, and then I had to figure it out. So I think that still all those same processes apply, just perhaps maybe in scarier ways... I don't know; maybe it was pretty scary back then for me as well.

I think it's more that you're debugging at 3am as a senior, or mid-level person, or above. It's just that like --

No, no, I mean, when I was a junior, I said; back when I was a junior. How I learned to do it was by doing it.

Oh, I see.

There's certain things that you learn to do by doing. And you can't actually impart that to somebody until they go through the fire, hopefully with somebody alongside them who's been there before, because it's a lot better that way... But I don't know, The Kids Are Alright.

I hope so. I hope so. I'm so worried about this younger generation. I feel so privileged and blessed to be in my mid to late 30s... \[laughter\] Inside joke there...

It is concerning... Yeah, I do have concerns, because I use these tools every day; I go to ChatGPT before I go to Google now, almost 100% of the time.

Same.

\[laughs\] We should make that a T-shirt.

But I also have -- almost every single time, I'm asking it to help me write this thing, and then I have to literally... I either literally copy and paste the error that I got, or I'm like "That method doesn't exist. What does it always do? You're correct, that doesn't exist! Let me correct that, and go for \[unintelligible 00:27:30.00\] And having to just constantly do that as a junior, where you either have -- you have to do something, and it's constantly giving you this BS all the time... It would feel overwhelming.

Yeah, but think of the alternative. Go back, Nick, when you were writing C for the first time, in like Intro to Computer Science class, or whatever language you're writing. Java. And you would type out the thing and you'd say "Okay, GCC, whatever, compile this." And it would be like "Compilation error." And it would just stare at you. And you'd be like "Uhhh... Okay..." It wouldn't give you anything besides maybe chunking out a whole bunch of binary-looking crap... And you'd be like "What do I --" Think what the kids can do right now. They take the output, they put it to ChatGPT, they say "This didn't work", and it says "You are correct. Try this." And then they try that. And so like, we were just out there -- I mean, I'll speak for myself, because I'm older than you, Nick. I was on an island when I was learning. I didn't have any help at all. Pretty much. I had a book that didn't change the words when things changed. And I had a compiler that didn't really say much when it wouldn't compile. And we all survived. So I don't know... The Kids Are Alright, guys. They'll be alright.

So I think there is a key thing here... Amal, you brought this up and you said "I don't know if this is just me." It's definitely not just you. I think this is a real concern. It's a concern that happens anytime technology changes.

We're not talking about it, though, Kball.

Well, I mean, you say we're not talking about it... It was the subject of one of the big talks at a conference I went to.

Okay, that's good.

There is some amount of this in the discourse. It was a management-focused conference, so it may not be -- I don't know. But yeah, there was definitely a question. Now, the speaker in that case was sort of pushing his book; not his physical book, but like his stance, because he runs a training company... And he was saying, "Oh, if you're not going to learn these things through the course of doing anymore because of AI, we need to do more formal training." That is one angle to this. Like, if you think about calculators, we force kids to practice doing calculations without calculators, because it helps them start to learn the underlying pieces, even though at some point they pretty much start using calculators for everything. There may be an analog to what we need to do in software. Maybe it's more formal training, maybe it's something else, but there may be something where we say "If you are learning, you don't use these tools, even though they would help you, because you need to learn the underlying fundamentals before you start applying these tools." \[00:30:08.01\] And we separate out the doing for learning from the doing for doing... Which is not something that happens right now a lot in entry-level positions. There's a lot of "You're doing this thing, and you're expected to learn on the job, and kind of go." Maybe we need to formalize the separation a little bit more, of like "Here's a set of things you do to learn principles, and here's a set of things you do to get the job done."

In college, all I learned was principles, and I didn't know anything -- I didn't learn anything about doing a job. And you read articles where employers say that's a huge problem about college grads, where it's just theory and first principles, and they don't know how to ship software.

Yeah. But yeah, I think the applied part of engineering is you've gotta go to a tech school for that. \[laughs\]

Well, yeah, but I mean, if you go through college and you haven't used AI -- I'm sure you do now, but... If you don't know how to do it, and they're gonna expect you to know how to write a prompt, I mean... I don't know.

Yeah, no, I hear you. I'm sorry, and just -- I'm very biased towards tech schools, because I went to one. I didn't graduate. That's like its own show, fun backstory there... But I did go to a tech school, and I felt like they are the only ones that I saw doing a ton of like hands-on learning projects. They make sure you can do the thing that you learned. I'd love to see more universities do...

Well, the problem with college isn't merely that you don't get applied education, it's that you end up with a giant heaping debt that you never pay off your entire life. And it's the only thing you cannot file bankruptcy against. That's the problem with college. But we're on a whole other podcast talking about that.

I do wonder, coming back to the generative AI thing, if part of the challenge right now - and this is coming in from the chat, but the challenge right now is sort of this assumption pushed by people who have a lot of investment in AI, that AI can actually replace people coding. And they're pushing -- you have all these studies, "Oh, it's improving your productivity, it's doing all this", and so everybody thinks "Oh, I've got to do this or I'm falling behind." And as we were highlighting, for some problems it's a big help, and for other problems, it's crap. And it's not helping you get more done, and at the same time, it's inhibiting your ability to learn. So I think some of this is pushed by people like the Sam Altmans of the world, who - they have an agenda. And it's very clear that they have an agenda, but they're kind of taking this... It's like the NFT boom. "This is gonna replace all these things. This is gonna be doing these things." Well, there's more value in AI than I think there was in crypto, but there's also a whole lot of junk.

And the question is, that none of us know the answer to, is like "Where will the pace of progress take us over n years?" Which goes back to my prediction; I predicted we'd have another plateau. I haven't seen a step change like we saw with transformers since then... And now we're just kind of like at this new plane, where we can do generative AI, now we have these tools, and now we're gonna integrate them, we're gonna test them, we're gonna figure them out, we're gonna have these minor improvements to our work and life, that don't replace humans at all. The question is, will the next step get us to a place there, or not? Or is it or is there going to be another one? And when will those step changes happen? This last one took about five years. Is there going to be another one at the pace of -- that was what the buzz was about back in the spring, was like "Look how fast we're moving now. It's going to just hit the stratosphere from here." We have seen that not take place. We are learning how these have improved our lives, but now we're seeing where they stop, and the question is \[unintelligible 00:33:54.09\] in five years there won't be any engineers; like, that could be true. I don't think it is, I don't think the history has played out that way. Past results do not predict future performance. But maybe these people are right that you won't need humans in the loop in 5 to 10 years, and the AI will do it all. I think all five of us are probably on the betting against that, but we've been wrong before, haven't we, Kball? \[laughter\]

\[00:34:20.13\] I think that there's less of a concern of it fully replacing us, but I do think that there is some truth to the idea that humans who use the AI well will outpace the humans that don't.

Sure.

And that might lead to -- I mean, I've heard the argument both ways. That might lead to less overall jobs, because you can really have a "10x developer", who's 1x plus the 9x AI... Or is it gonna be like the -- another argument I saw was the push from assembly languages to higher level languages didn't make it so that there were fewer programmers because it was easier to program, it made it so there were way more programmers.

Yeah, because there's more opportunity, and cheaper -- more people can play the game. Yeah.

Yeah. I mean, I think there's a huge swath of businesses whose economics don't make sense at the current cost of software development, that might make sense if you reduce the cost of software development by 10x, or 5x, or something in those domains. There's a huge swath of businesses that exist today, whose economics don't make sense based on software development, and they only are alive because capital was so cheap, and we're learning that.

Sure.

But maybe those sure businesses do make sense in a world where AI makes software developers 10 times more productive.

I just wish those businesses would die. I'm sorry to say that. And it sounds so harsh, but really, it's really bad for all of us. Because what it does is it creates this churn, y'all; all these incredible, smart, kind human beings go work at these companies with a hope and a dream, and then they get laid off, and it just creates churn. And all they want for Christmas, New Year's, whatever, is stability tech. Stop creating churn in our community; stop it. It sucks.

It's a natural process though, of all creation, is churn, and life and death, and things survive and things don't, and that's the way it plays out. You can't just know what's going to work; you have to try things.

Too much churn. We can do better. We can do better, you know? And I would rather we be growing at a slower rate and have it be more sustainable and less churn-heavy than what we have today.

The last year and a half have been brutal in this industry. They've been absolutely brutal. And I think a lot of that has been a hangover of a couple of years that were manic... It's almost like the industry itself is doing a manic depressive thing. Coming back to predictions, I would actually predict that towards the second half of next year, we get back to something that feels a little bit more stable in the tech industry. I think we've still have some overhang to work through. I think there's going to be more startups going bust. But I think both because we've worked through a fair amount of it, and because I expect financial conditions to ease up, the second half of this year I think is going to look more stable in the tech industry.

Yeah, I think so, too. I think overall 2024 I'm hearing is looking up, even just from recruiters and people that are waiting on hiring.

Define stability. I want Kball to define that, so I can hold his feet to the fire later. This is way too vague. I feel like you're gonna be right, even if it's not specific. What do you mean more stable?

I've learned my lesson from Twitter. \[unintelligible 00:37:32.02\]

Well played, well played.

It's a good question.

Less layoffs...?

Maybe it's less layoffs... Which we've had reduced layoffs over the course of the year; we will probably see -- I think we saw a few coming through in December again, and we may see a spike up at the beginning of the year again, just because everybody's doing their annual "Oh my god, what are we trying to do next year?" So I think that. I think a part of it is big tech will be expanding and hiring again.

\[00:38:03.12\] Which we've seen of the big tech. I think Facebook/Meta is the only one so far that has shown that they are, which may be just be the first of all, or maybe...

Oh yeah, no, I'm being poached for roles at Meta and Microsoft and Google right now, so...

You're being poached? I thought you were funemployed.

Oh, I guess I'm funemployed, but I mean, they're poaching me from my first choice. \[laughter\]

You're being recruited?

They're poaching you from your life of leisure...

Yes. Yes. Yes.

Well, that's good to know.

Yeah, I'm being recruited. I'm being recruited. Yeah.

What about us plebs? Can us plebs get a job offer, Amal?

Yeah, I guess. Sure. And technically, another letter in the FAANG, but I'm not gonna say which one. And no offense to anyone who works at any of these companies, I'm not trying to work at any of these companies. I'm trying to work somewhere else. But I'm just saying that the recruiters are back.

Recruiters are people too, you know? That's what I always have to remind myself. Cool. Chris, any predictions for this year, 2024? You'd like to put your name on any future goings on?

Well, we've already heard that Twitter's gonna go bankrupt...

\[laughs\] You can put your money behind that one.

Yeah... Can we do like a death pool? Or no?

\[laughs\]

That's where I'm at.

It's gonna get pretty morbid around here...

Okay, let's not do that.

Who would you like to see die this year? No, uh --

I mean, I don't have a preference, but...

Okay, but who do you think might die?

Well, Jimmy Carter doesn't have long...

\[laughs\]

That's true... But then again, he's been in hospice for like the last five years.

That's true. I thought he was gone already. He hasn't died? Wow...

No, he's hanging on.

That's amazing. That's a sound choice.

So that must be it. That's my prediction.

I hope Jimmy Carter is alive. I hope he stays alive. He's one of my favorite living presidents.

I hope he survives, yes, just so that we can call Chris wrong last year... But that's an epic call. Alright, Nick, can you top that? 2024 prediction, better than what Chris just did... Because one's amazing.

I don't know... I like too the idea of a Deadpool... Not that I want any one, or any --

Like a sequel?

Not that I want anything to die, but I just feel like there's going to be churn enough that the kings are going to at least be challenged more than they have been in the past.

Which is good. 3; And the things that are making me think that --

Get specific.

I don't know if I want to call it out specifically, but... \[laughs\] I feel like the close-knit \[00:40:47.11\] -- I don't know my words today... My CO2 is off the charts because of podcasting.

\[laughs\] Oh, gosh... The quantified self.

Yeah. I think that the really close marriage between React and Next is going to turn out to be a mistake that hurts React more.

Oh... Do you think there's gonna be a divorce?

No, no, they're not gonna get divorced... But something else is gonna supplant it, or at least supplant it in the mindset, right? Because nothing is supplanting jQuery yet.

Okay. Mindshare.

I'm worried that -- I'm not worried, I'm predicting potentially that Next... Everybody's gonna start seeing through the Next facade to the Vercel advertisement that it is...

Okay, I think that's already happened, to a certain extent. You think it's gonna go viral?

It's gonna really affect React's market share.

People are actually going to move away, versus just talking about it.

Yes.

Okay.

To Astro.

How do we measure that? Oh, to Astro. You have a specific one.

Astro is awesome, okay?

I think that's how we put a nice, hard prediction on it. Astro overtakes Next.

Yeah. And we can just use the State of JS survey results.

Not every site's a static site, though. I mean, I think Astro is great for --

They're moving the other way.

How so?

Isn't Astro becoming less of a static site generator and more of the...?

\[00:42:10.09\] Yeah, yeah, yeah. Yeah, I guess you're right with the newer... Yeah. I mean, that's fair. I mean, you could still do very rich interactions with Astro sites, it's just that because it's not the hot path, which I think is the right thing, it's just one more thing to do. And so if that's all you're doing, it's maybe not the best choice, I would say; maybe use Lit, create a bunch of Lit components... You know, that's the way I would go.

Yeah. I was gonna say, maybe Angular is cool again.

Angular is cool again.

Oh, we're gonna find out -- we'll find out in January, as Kball and Amal host a few eagerly-anticipated and requested Angular coverage... Coming to JS Party. There's my prediction.

Sorry, we suck at Angular cover coverage, guys... Just so you know. I think it's just like not a lot of us are using it anymore... I was managing a team for a little while, an Angular team... But I was a manager, so I was dealing with all the other problems, and didn't get a chance to really dig into Angular too much. But I'm excited to do that this upcoming year.

Yup. January, February, we've got a couple on the books... And if those go well, I think now we have some connections into those teams, so we can get more.

Yeah. And I have also just a really great community show planned with a couple of really nice folks from Poland as well... I would love to do that in like March, April. Because the Angular community is amazing. They're the best community, I feel like, in the frontend space; they're just the most lovey-dovey... I don't know, they're great.

Have you ever heard of Ember.js?

Oh yeah, I take that back. Ember is great, too. I just know less people. So... Ember is amazing, too. But those are definitely the best communities, by far.

Any other predictions for 24, Amal?

My prediction is that -- so first, I want to clarify something. Some of the smartest people I know in our industry are writing components, and they write way more complicated components than I could ever even write... There's nothing wrong with writing components. I just maybe wanted to clarify that I'm not being paid to create buttons and interactions on a screen anymore. Like, I'm paid to do the other stuff. So I just wanted to correct that, because I feel like \[unintelligible 00:44:14.23\]

But I thought your point recently was you're not being paid to do those things yet.

Oh yeah, yeah, I'm not being paid to do these things yet. Listen, do you understand the meaning of it's really hard to quit funemployment? I'm having too much fun. I don't -- like, if I could do this for another year, I'd be straight. But alas, I have to get a job. Gotta help my husband pay the bills. My predictions are we are going to start embracing simplicity. So I think we're kind of at the point of the pendulum swing where our problems have problems...

Oh, that's a good episode title.

Yeah, our problems have problems. So it's like, we're just gonna start to realize that we have dug ourselves into way complicated mess, and CSS and JavaScript and web APIs are giving us some really great primitives, that are gonna potentially help us write more idiomatic code all around, including type annotations, which I'm super-excited about... We're a few years away from that unfortunately hitting a browser, I think... But still, that's very exciting. So I think we're going to start embracing simplicity, because I think we're going to realize that less is more, and when you have more time, especially, it means you can do more things for your users. So that's what I'm hoping for. I think we're gonna see a lot more projects embrace JSDocs over TypeScript as one small step towards simplicity, I think \[unintelligible 00:45:44.28\] around like build architectures, and stuff like that. I think we'll start to see a lot more apps shipping unbundled JavaScript, but I think minified unbundled JavaScript... So a little bit better than what DHH recently shipped with Once, but very close to it...

Hundreds across the board, wasn't it?

\[00:46:08.28\] Ah, sure, but I think you have to understand there's a big difference between Lighthouse and simulated performance, versus like in the wild. Very different numbers. And I think that's why a lot of performance experts --

Don't they create those, so that we can actually do our tests against our -- I mean, aren't we all striving for that though?

It's that whole thing about once the metric becomes the goal, it gets gamed. So those metrics were useful when we weren't targeting them as much. And now that we target them, we game them in a way that isn't necessarily representative of real world performance.

But you have information about Once, that shows its real-world performance?

Well, I have a friend who I really wish I could -- they just don't want to start a public beef war with DHH... I haven't started a beef war, but I definitely disagreed with him publicly, and I dealt with all his reply guys for a few days... So that was fun... But basically, his whole thing was like "I want to just take his side, and just run those files through a few build steps, and show him how it's faster." But minifying and compressing those files is gonna be faster than what he has. It just is. You can do benchmarks with any other website in the wild and see that, so... So hopefully -- anyways. Either way though, he's taking a step in the right direction, so I don't really care about the specifics. I think, in general, a step towards simplicity. So that's my prediction.

How do you measure that?

I don't know, Jerod, that's a you problem.

\[laughs\]

Any measurement I come up with, you're game, so...

Twitter sentiment is measure is -- that is a scientific unit of measurement, okay?

Oh, Twitter sentiment?

Wait, wait, we're gonna run a survey this year, right? So maybe...

We're gonna ask people if they value simplicity... Who says no to that? Nobody says no.

I don't know. But maybe we can come up with some sort of proxy metric that we don't expose to people, but you figure out how you want to measure it, put it behind the survey, run a survey beginning of year and end of year, and there we have a way to start to --

Yeah. You guys, I've gotta tell you a story about this thing called a smoot. There's this bridge right next to MIT, where they literally took some fraternity guy and they just measured how many times can we lie this person down across the bridge. They basically came up with a unit of measurement which was his height, and it was like "How many smoots does it take to get across the bridge?" So they came up with this unit, and... Anyway, so all I'm saying is that we have something called a smoot...

Where is this going?

...that was a made-up unit... So we need something like that that's like a Twitter sentiment type thing, you know?

Oh...

So how many squirrels does it take before you see someone complaining, or praising something?

\[unintelligible 00:48:48.11\] already something. Wasn't it called clout?

Prediction - clout will not be renovated in 2024. Okay, so assuming that we can measure sentiment towards simplicity, it's going to increase in 2024.

I think so, because I think enough is enough. We're really peaking on complexity, and making our lives so much harder than they have to be... And I think as a result we're hurting our industry, because people on the outside are just looking at us solve problems in different flavors, and... You know, JavaScript just kind of gets a bad rap in enterprise as a result. So...

Could we rank different open source frameworks or other things in terms of complexity, and then measure that, or do something -- like, there's a couple different angles I could see taking this. So one is like certain frameworks are more complex than others, and maybe we could just have a ranking and then see how many people are starting new projects based on those frameworks. We could do dependency counts. Number of dependencies is like a rough correlation with complexity of simplicity. We could just do how many monoliths are getting started on GitHub, versus non-monolithic applications... I don't know, I feel like this is something that we could put up some proxy metrics for.

Yeah. Well, I can ask Twitter, to be meta...

\[laughs\]

Let's just say "Hey, Twitter..."

\[00:50:10.15\] There you go.

"...if I wanted to measure this metric, what are anchor posts that we can use?" And whatever Twitter suggests, we can...

But Twitter is going to be bankrupt.

Right. We can't do that anymore.

This sounds like a huge waste of time.

Yeah... Here's the problem - you'll never get past the part where you have to define what simplicity is. You're just never gonna get past it. There's PhDs about this thing. So I think we just keep it simple, and just declare Amal wrong at the end of the year. I mean, that'll be the simplest, right? \[laughter\]

Okay, whatever... It wouldn't be the first time I was wrong, so...

I will say, based on Twitter sentiment, it does seem there is a swing back towards more monolithic approaches, all in one frameworks like Ruby on Rails, and Elixir, or Phoenix, and things like that...

Htmx.

Htmx... And the kind of commentary I've heard about it is like "Oh, because the tech industry is shrinking at the moment", or if not shrinking, at least struggling a little bit more, "there's a lot more emphasis again on productivity over pure play scalability, or technical perfection", or whatever. And arguing that some of those other approaches were a zero interest rate phenomenon... But I don't know. I mean, I think, to Amal's point, there is a sentiment shift that seems like it's going on, and one could make arguments for whether that's continuing to be true... But yeah, an objective measure seems beyond us.

Yeah. And I think the React Server Components - it was a big catalyst, I think, in kind of making that a higher-level conversation... Because I can tell you, this simplicity thing has been happening -- these are conversations that have been happening, at least in my circles, for a while now. For a while, like, years. \[laughs\] I think the React Server Components thing really just pushed it to like this other level, where people were just like "Whoa, whoa, whoa, whoa, whoa, whoa... What problem are we actually trying to solve here?" So I in that sense, I think it's a good thing. But I think for me as just someone who cares about the health of the web -- I just want us to build cool stuff for people, and make... We need to focus on the next generation of problems, like how are we going to get our sites translated in all these different languages, and how are we going to make performant and accessible experiences that are for emerging markets...? And how are we going to do cooler things on mobile? How are we going to just give people no reason to use a native app? How can we create web experiences that are just good enough, you know? So we're just not there yet... We have so many other things to be focused on, and we're just like circling around these same problems, and I'm like "Let's move on already", you know?

Well, not to be a downer, but I've had enough trips around the sun now to know that when it comes to the software development community, shiny always beats simple. And we will be interested in simple until the next shiny. And then we will all quickly abandon our principles and chase shiny, until shiny stops shining, and some new shiny comes out.

But is generative AI stopped shining yet? Or is it still shiny?

Good question. Find out next time, on -- no, I don't know. I ran out of stuff to say.

\[00:53:31.18\]

Let's do resolutions, as we are getting near the end. Does anybody -- we have a few predictions; we'll see what happens next year, of course. All in good fun. Resolutions, how about? I tend to just keep mine private, so I can fail to myself... But some of y'all like to put them out there to the public, so that we can help you stay accountable... Does anybody want to be resolved in this new year to maybe change something about their lives, or have a goal for your career, or for your funemployment? ...anything, before we get into the big announcement.

So I'm working on a project, and -- well, I've already published it, but right now I'm working on a docs site, and a major rewrite, and all that stuff...

Really?

And I want to get it out there, and try to get it in more people's hands, and...

Awesome. Tell us about it. I didn't know you were working on something new.

Yeah, it's like a thing that lints your package. So if you're gonna publish to registry, it lints the tarball, the contents of the tarball, and how \[unintelligible 00:58:11.06\] you install from that tarball. And how does it work? And is it broken? And these are typically things that tests don't catch. The idea is you run this, it will do stuff like it packs your project, installs it into a \[unintelligible 00:58:30.16\] and then runs a bunch of checks against it, to make sure that consumers can I actually use your package. So that's the idea.

Nice.

That's very cool.

That's very cool.

Is it gonna be called Shiny?

No. It's called Midnight Smoker.

Is it really called Midnight Smoker?

Mm-hm.

Wow.

That's kind of awesome.

What's the backstory behind that? That sounds like the name of a blues album more so than a JavaScript package...

No, it's like smoke tests, right?

Smoke tests, but also the Joker, right?

Right. So one of its features is basically you can run arbitrary scripts against the package as it would be installed... And so that would be a smoke test. "Okay, does this thing actually -- can I require this thing? Can I run the CLI?" And you can do stuff like that. But there's also like built-in checks if you don't want to write a custom script. So that's kind of where the name came from, smoke tests.

So that sounds as if it's from the perspective of a package publisher, but as you were describing it, I've found myself wondering if there's a security version of this that a package installer could run this against a package they're going to install in a sandbox, and see "Does this make weird network requests?" or something else.

No... I mean, I think I'm probably going to just stay away from -- there's other tools that can do things like that a lot better, I think. I'm trying to be careful not to do things like -- I don't want to necessarily be a tool that checks and makes sure all the dependencies are there, or they're all used, or something... Because there are other tools that do that, and I don't want to step on ESLint's toes either. I don't want to do things like ESLint does.

You mean you don't want to solve a solved problem?

Right. I'm trying to limit the scope, and I think security checks are better... I mean, the other thing I work on, which is LavaMoat, would maybe help more with that sort of thing.

We've gotta do a show on LavaMoat next year.

Yeah, we do.

That's super-cool. Yeah.

Anybody else? I think that's awesome, Chris. I think it sounds like a very achievable goal, since you're almost finished... Of course, the 80/20 rule and documentation... So best of luck to you still. Anybody else want to go on the line, put themselves on the line, I don't know, stay on the line with their resolutions?

For me, I've got to stay moving, like as in I have to stay unconstipated, I think, with my creativity.

Oh, gosh... \[laugh\] Well, that paints a picture...

Yeah. Whatever. Everybody uses the bathroom, including the former Queen of England, you know? And Beyonce.

Unless you're constipated. Then you don't use it.

Anyways... \[laugh\]

But that's how you think about your creativity, just gotta flush the system?

Just lush it. Keep it moving.

Yeah, I've just gotta keep it flowing and moving. Keep it regular. I think that's the --

"Got to keep on movin'..."

Yeah, yeah...

Amal and her metaphors, you know?

Yeah, I have a birthing -- I don't know, like I'm gonna birth a lot of creativity.

\[laughs\] You've got birthing on the mind.

Yeah, in 2024. No, I have some really fun projects coming up. I'm actually stepping into Node as a formal kind of contributor, and I'm going to be leading up to a very exciting project that I'm like "Oh, should I --" I wanna have a few more conversations with people before I publicly announce it, but yes... This is not my announcement, no, but I'm saying I'm excited about that. I'm gonna be doing some cool stuff with Node, and I'm gonna be writing... I'm gonna not let perfect get in the way of good... Yeah, I've got to just -- I've gotta write... So yeah, I'm excited to have a lot of creative energy, kind of, I think, released into the world a bit more this year.

\[01:02:28.01\] Got it. More creativity... More flow... More birthing... And flushing.

And flushing. Yes.

Nick, you wanted to be on more conferences in '23... I see that you're speaking at that conference in January... So how do you feel about that resolution, and are you resolved to continue that flow, or how do you feel about that? Maybe you have new ideas for this year...

Yeah, I am pretty excited about that... Kicking it off right away with that conference at the end of January, which will be a lot of fun... And I haven't submitted to any other ones, but I have ideas for talks that I think are really good, and they're things I'm really passionate about. I'm really getting into code \[unintelligible 01:03:10.27\] and manipulation, and I think that there's a lot of really cool stuff to do with that... And I'm kind of working on a project around that right now, that I hope to continue on in the new year. But yeah, I think there's a lot of changes coming up, and I'm pretty excited about it. I think -- there's a podcast that I listen to called \[unintelligible 01:03:34.10\] where they talk about a yearly theme... And I just verbatim stole the yearly theme from the host for me, and that is the year of small improvements. So I have this idea of - I'm just going to make a tiny improvement at least once a week. So that's 52 improvements over the next year. And that's going to be like overall awesome. And that's things like I'm going to actually install a proper light in my office, or... You know, just like small bug fix, things that are annoying me I'm going to fix, and not let them just be annoying.

Like your internet provider? \[laughter\]

Like my internet provider.

Too soon?

I hope not...

Yeah. I love that idea.

And I'm gonna wear sunglasses.

Kball, would you like to go on the line?

Sure. I have made and failed at physical resolutions the last two years we've done this, so I am not doing anything in that domain. So last year, the first half of the year I was purely running my own business, and in some ways because it takes a long time to ramp up a business, I was undercommitted for much of the year, and then I ended up getting a job, which has been awesome and challenging... And I'm still running my own business. So I went from undercommitted to overcommitted. So my resolution for this year is to get to a place where I feel like I'm moderately balanced. I am not so overcommitted that I feel like I'm pulled in a million different ways... Which - it was trending there towards the year, as I got more onboarded with the job, and it was less overwhelming... But also not so undercommitted that I'm looking for something new, like a new job. So I think that's the big goal. The other thing is to keep working on my coaching skills. That's what the business was around. That's also the job that I got, is director of engineering at a coaching company called Mento. There's a lot of opportunities for me to think about and learn to be a better coach, and I want to keep doing that. That is something that I enjoy tremendously, and I think is also something where I've been able to help people a lot, and it's super-fun... So I will keep working on that.

Love it, love it. Well, I'll finish up quickly, and we'll go to the big announcement and call it a show. They say the best way to predict the future is to invent it. So I will combine predictions with resolutions, and share a little bit. I think we are resolved here at JS Party to add some new voices to the pod this year... And so there we have both a prediction and a resolution. \[01:05:59.18\] We're also resolved to bring back an old podcast here at Changelog, to revitalize and bring back an old show that we used to produce, and produce it once again... And I'm also resolved to take Changelog++ to the next level in 24. So those are three things that I think are achievable, two of which are already in motion and happening... So it's easy to predict things that are 80% done, but we'll see if the last 20% gets finished in time for it to be successful. Definitely going to add some new voices around here, so stay tuned for that. Hopefully, they'll be somewhat familiar, yet new, as regulars; it's something we've been working on behind the scenes for the last couple of months. So that's exciting. Okay, Amal - big announcement. So much has been building up to this moment. Kball, b0neskull - set her up. That means Kball does something and Chris just sits there.

Thank you. Yeah, I didn't want to have to prompt Kball... So yeah, I want my --

Go ahead, Kball. Announce the announcement.

Announcements, announcements... Announcements.

\[laugh\] There you go, Amal.

Chris is shaking his head like nothing's gonna happen. He's like "Nope, nope, nope. Not doing it."

He's like "That shouldn't have happened."

Wait, I could do the nose kazoo again if you want.

Okay, do it. It sounds good.

Yeah, please. It sounds like a horn. \[nose kazoo 01:07:13.18\]

So my announcement is that I've pinged these dudes that I've worked with on JS Party a few weeks ago to say "Hey, we'd love to do a survey this year", this year being next year. "How do you all feel about it?" And they were all "Yeah, that sounds good." Okay, cool. So next steps are for me to create a repo; I want to kind of work on this in the open... But essentially, what I'd like to do is create a JS Party listener survey, an annual listener survey... And so it'd be great to work with some of you on the questions, and what you all think are useful... We'll kind of seed some initial things there, but obviously, we can discuss it... And so what I'd like to do is everything will be done in the open; the survey questions... I think we'll probably use the -- I think The State of JavaScript has this platform, the survey platform that they use, so I think we can actually technically host it there... But anyways, so we'd love to kind of like hear more from you all a bit more directly on what you want more of, less of etc. and just have a way to kind of touch base annually. And so I'd like to give us - because everyone has 17 million other things that they're working on, and I'd like to give us at least like six to eight months to kind of actually work on this, starting in mid-January. And then I'd love to launch the survey in the last three months of this year. So yeah, so I think that's kind of what I'm thinking. So again, we'll put a link in the show notes for the repo. We'll be having these discussions and working in the open. If you're interested in contributing or chipping in or watching along, please. Yeah, we would love your help, and we welcome you. And I think one thing we'll have to decide is "Oh, does it make sense to translate the survey into a different language?" Maybe not, because the show is in English...

TypeScript?

...but I don't know. You all decide.

There you go. There you have it. The link will be in your show notes. You can get involved, help shape this, help make it better than we could surely make it on our own. That would be awesome. And we'd love to hear from you all about how to make that great for everybody. Okay, this has been our New Year's party. Happy '24 to all you all out there listening. Any final words from the panel before I hit that outro song? Except for Nick. Anybody but Nick.

Oh, come on... I had a good one.

\[laughs\] Go ahead, Nick.

Did you know that if you long-press the Share button on Threads, you get the share sheet?

What?!

That's it.

For Nick Nisi... Amal, Chris, Kball... I'm Jerod, this is JS Party. Happy 24, y'all. Let's make it an awesome one. We'll see you next week.

\[01:10:12.04\]

Well, no, no, no, I have an announcement to make.

Okay, announcements. Announcements. This is part of our --

So you let me know if you want the announcement to be now, or later.

Let's save it for later. You always save the announcement for the end.

Announcements, announcements, announcements...

Yeah, Kball, you're always the best at announcing announcements, I have to say. You're always like \[01:11:29.12\] That was your job in a past life, you know?

I don't know, Chris has a literal kazoo over there. He could probably do a better \[01:11:35.28\] than Kball...

Yeah... You know what - can we do a song between Kball and Chris? Can you do "Announcements, announcements, announcements" and I'll be maestro, and he kazoos?

Can your kazoo do an announcing sound?

No. \[laughter\]

I saw that coming a mile away, and I still wanted it, too. So I allowed it. It's amazing.

Did he really mean it, or was that just like --

Oh, he means it.

Oh, no...

It's both.

Alright. Well, we'll just have to imagine it, Kball... Okay, do you wanna do the announcement?

Um, nope. Let's save it for the end. Always save the best for the end.

Okay, we'll do that. We'll do that.