914: 5 Upcoming + Next Gen JavaScript Features

Wes and Scott talk about the latest JavaScript proposals from TC39, including features like import defer, the powerful new random namespace, Array.fromAsync, and native clamp and upsert methods. They break down what’s coming, why it matters, and how it might improve your code. Show Notes 00:00 Welcome to Syntax! 02:55 Brought to you by Sentry.io 05:37 Import Defer proposal-defer-import-eval proposal-deferred-reexports Rob Palmer 09:30 Random Functions proposal-random-functions proposal-seeded-random 18:32 Array from Async proposal-array-from-async 20:56 Upsert for Maps proposal-upsert 23:13 Clamp proposal-math-clamp 27:02 Sick Picks + Shameless Plugs Sick Picks Scott: Anker Max USB 4-Port Wes: Clarkson’s Farm Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

Speaker names marked ? are inferred from speaking time and the show’s known hosts — they are not voice-verified.

• 0:00Wes Bos?

  Welcome to SynthX. Today, we've got an episode for you on next-gen, upcoming and coming very soon JavaScript features. So TC39 has a proposal stage where people will propose ideas to add to JavaScript, and they go through the different stages. And as they move along, some of them are stage zero, they're just wacky ideas that'll never happen. And then some of them are are stage two, two, 2.7, I guess, is the stage now, three, four, and then we actually have them in the browser. So there was, last week, there's a whole bunch of new proposals that have moved forward and looking like they're going to make it. So we're going to talk a little bit about what they are and where they would help you

• 0:45Wes Bos?

  out and kind of what you can look forward to, as well as like, give you a chance to, anytime any of these new features come out, you always get these guys that are like, "Whoa, that API sucks," or "Why do we need this?" Now's your chance. You're a Y guy? Now's your chance to take part of the standards process and stop it before it's too late. So let's get on into it. I forgot to introduce you, Scott. How you doing, Scott?

• 1:14Scott Tolinski?

  Oh, I'm a Y guy. No, I'm doing, doing good, man. I've never heard of Y guy before. That's hilarious.

• 1:21Wes Bos?

  I just made that up, yeah.

• 1:22Scott Tolinski?

  Let me just tell you, folks, we did a, we did a live show in Denver, and Wes was a part of a panel, and the guy could not stop coining new terms to the point where people were buying domains in the audience as he was talking. He was just like, "We put, we put chocolate on a pizza and call it Tretza." And everybody's like, "Oh, Tretza, come on."

• 1:44Wes Bos?

  Tretza.

• 1:46Scott Tolinski?

  Fail backward.

• 1:47Wes Bos?

  Struggle backwards. People are asked like, the same question all the time is like, "Should you learn the basics before you get into deep?" And you know, and I was like, "Ah, I don't really believe that." Like, like, I learned jQuery, and then I learned JavaScript. I learned, a lot of people are React, and then they learn regular JavaScript. And a lot of people are now AI programming, vibe coding, and then they're gonna, they're gonna learn how to Actually code properly, um, once they have that and it's, it's, I, I just off the top of my head, I was like, this is called struggling backwards. Meaning like you just get into it and then you realize you hit a problem and then you have to like, struggle through it and learn how this stuff actually works. And everyone's like, and then like the rest of the panelists are like, mm-hmm, I really, I really agree that you should struggle backwards, you know?

• 2:30Wes Bos?

  And I was like, guys, they just, I just made that up. That's not like a thing that we have. And then someone bought the domain name.

• 2:37Scott Tolinski?

  Yeah, it's cra- there wasn't even another one too. I was, I was just like, I was in the audience and I was just like, God, he's doing it again. And every time you, you got called on for something, I was just like, that is a, uh, another term coin. So, Wes, your brain is fascinating to me.

• 2:53Wes Bos?

  Yes.

• 2:54Scott Tolinski?

  Yeah. Also fascinating, my website, because it doesn't work very well because I'm not checking my errors enough on sentry.io. Actually, that's not true. I do. I check it all the time and my website works absolutely fine because of that. Sentry is, it's the perfect place to, to make sure that your application is working. And it does so in a wonderful way by really giving you all of the data. There's even a neat AI feature that helps you fix the problems because you know that error logs and dumps can just be like, it can be a steamy dump. I'll tell you that. And Sentry allows you to click a button and it allows you to parse that in a nice way. It allows you to then connect it to potentially logs or see exactly what happened in a session replay.

• 3:40Scott Tolinski?

  We have an, an error on the syntax site, Wes, that has happened 12 times a day for who knows how long, because there's, uh, 20,000 events of this, or 2,000 events of this.

• 3:53Wes Bos?

  What, what's there?

• 3:55Scott Tolinski?

  Your credit balance is too low to access the Anthropic API.

• 3:59Wes Bos?

  Oh shoot, we gotta fix that.

• 4:01Scott Tolinski?

  I know.

• 4:02Wes Bos?

  Not 20,000. Oh yeah, actually, you know, we have a cron. Yeah, we have a cron. The way that that works is every five minutes it checks if there's something that needs to be. Generated like an AI summary and then it pings the Anthropic API. So it's probably happening every five minutes for it stopped working.

• 4:21Scott Tolinski?

  May 27.

• 4:23Wes Bos?

  Okay, so we probably have like eight shows that are getting pinged every five minutes. And something happened with the Anthropic API. I think we either have to update it or the the card ran out or something.

• 4:36Scott Tolinski?

  The card ran out.

• 4:37Wes Bos?

  We also decided that those AI summaries were not very good because we have Randy now. And we're just gonna stop putting the AI summaries in there because Randy's summaries are better.

• 4:48Scott Tolinski?

  There's also a new feature in here in this error, which shout out to Sentry here because you know, it's a cron job. Like, are you checking your logs to whatever to see if a cron job failed or passed? I'm sure you might notice it stopped working or something like that. But now we can see that this has happened 2000 times since May 27th and we can take care of it. There's also a new feature here called SEER, which is in beta. It allows you to find the root cause of an issue. And you just click that find root cause button and it's gonna attempt to figure out what the root. I have a feeling I know what the root cause of your credit balance is too low here. But there's some errors that I don't think I'll be able to find that. And so shout out to Sentry on that. Head on over to sentry.io forward slash syntax.

• 5:31Scott Tolinski?

  Sign up with the coupon code TASTY TREAT, all lowercase, all one more, get two months for free. All right, TC39.

• 5:38Wes Bos?

  All right, so we're gonna go through all the different proposals and kind of where they're at. The first one we have here is import module with a defer on it. This is kind of interesting. So right now with a script tag, if you pop a defer on the script tag, what will happen is the browser will download the JavaScript from that tag, but it will wait until the end to actually go ahead and execute it. And the proposal for module defer is that you can, like, I guess, like, if you're thinking about performance on a website, maybe we'll step back a bit.

• 6:20Wes Bos?

  There's a couple of things you can do to make your app more performant, right? You can not download all of the.

• 6:28Wes Bos?

  JavaScript that is needed until you actually need it. And it's like lazy loading, right? And you can dynamically require in JavaScript. But the other part of JavaScript is not just loading or downloading the actual JavaScript. It's actually executing. It's the browser needs to parse out the entire JavaScript so that it understands what the methods are and everything. And if there's any code that needs to be run right away when that thing is required then or imported, then that will run. And that execution takes up CPU and it can make your app slower. So we have immediate importing and immediate execution. That's just a regular import.

• 7:10Wes Bos?

  We have lazy loading, which is a dynamic import. And now we are going to get it at a stage 2.7, which is deferring the import, meaning that it will download it right away, but it will not execute it until you call or until you use that code inside of there. So simply just pop a defer on the import statement. So it's import defer whatever. And then you wait until it will, the browser will simply just wait or the JavaScript runtime will simply wait until you actually need to use that code before it actually executes it, which can, it can be expensive. Like I've had some, I've had some code like on a CloudFlare worker

• 7:53Wes Bos?

  that took, every time you instantiated the object, it took quite a, quite a long time, right? It turned out to be a bug. But if you have some very big code, you might not want that happening immediately on import. You might want to wait until you actually need it. And if you ever actually end up needing it. Yeah. Alongside that as well, there's another one for adding the deferred to re-exports, which is when you import and export something in a single line. There's another proposal which will allow you to add the deferred value to those. But It's not really that. It's you'll you'll need it, but it's not super interesting. So you won't spend any time on that.

• 8:33Scott Tolinski?

  Yeah. By the way, if you if you do want to keep up on a lot of this stuff, or really, if you're on Twitter, Rob Palmer, who you did mention here, Rob is great follow for this. He's always tweeting out about whatever is going on.

• 8:48Wes Bos?

  He's a co-chair of TC39. And he always, whenever anything interesting is happening at TC39, he's posting it up. He's on Blue Sky as well. So

• 8:58Scott Tolinski?

  Oh, yeah.

• 8:58Wes Bos?

  Certainly a very good follow. And his profile photo is of one of my JavaScript exercises. I just realized. So I'm very happy about that.

• 9:07Scott Tolinski?

  In Blue Sky or on Twitter?

• 9:09Wes Bos?

  On Twitter. It's the like, every single color, every single like named color in HTML. It's a screenshot from one of my exercises.

• 9:18Scott Tolinski?

  Oh, I see. His, oh, his, not his, his little, not his avatar.

• 9:22Wes Bos?

  No, no, no, no, that's not me. That's him.

• 9:25Scott Tolinski?

  I was gonna say, I, I, well, how could this possibly be about colors? It's black and white. Next one here is the random, random namespace and functions. This one is stage zero, championed by Tab Atkins. Man. So the, the general idea here is that, uh, let's even read this first paragraph. Historically, JS has offered a very simple API for randomness, math dot random, which we've all used. It's a function that returns a random value of uniform distribution from zero to one.

• 9:59Wes Bos?

  Now we know what random is.

• 10:02Scott Tolinski?

  I love that the way these things are written, um, to be so formal. I'm such an informal person in many ways.

• 10:07Wes Bos?

  This whole spec authoring thing is a, is a world of its own.

• 10:12Scott Tolinski?

  I know. I, I asked, uh, I know this is stupid, but I asked ChatGPT to write, Courtney, a thank you for my salad in a formal way. And it was like, dearest wife, thank you so much for this yummy salad. And I did say you need to use the word yummy in it. And she was like, who wrote this? You didn't write this.

• 10:29Wes Bos?

  Oh, man.

• 10:29Scott Tolinski?

  Yeah, obviously ChatGPT wrote it. It sounds the most ChatGPT thing ever. Side note, double side note. Do you have people in your life that use ChatGPT and text messages and emails? And it's like, very bad and obvious?

• 10:42Wes Bos?

  My kid's teacher just started writing her emails and

• 10:49Wes Bos?

  Like, there's double emojis at the end of every sentence, and that's a dead giveaway. You, the M dash, everyone is a dead giveaway that you're using, unfortunately, because I'm a M dash enjoyer. I probably don't use it in the right ways. But, uh, the double emoji in like a tweet or at the end of a sentence, it's a dead giveaway that you're using chat GPT to write it, and it's, it's annoying.

• 11:13Scott Tolinski?

  It's annoying, yeah, it's so odd.

• 11:15Wes Bos?

  It makes more sense because you can just like do a quick bullet list of what needs to happen. And then they, you feed it in and it makes this like flowery email, but it's just, I feel like I can smell it a hundred miles away when, when somebody's using AI to write these things.

• 11:31Scott Tolinski?

  It's weird. Uh, it's very weird. Yeah, I don't like getting them. All right, back to random. Random is a, it, it, most importantly, a new namespace for randomness within JavaScript.

• 11:44Wes Bos?

  Random dot, and there's 22 methods on there.

• 11:47Scott Tolinski?

  Twenty-two randomness things, which is, hey, that's pretty cool. So some, there, one of them is listed as random, as the random method. So are you going to say random dot random?

• 11:59Wes Bos?

  Yes. Well, random not random is going to be the like existing random that we already have. It's not very exciting, but.

• 12:05Scott Tolinski?

  I was just wondering if that's the way that.

• 12:07Wes Bos?

  Yeah, random not random, super random. But the rest of them are for doing a random number between X and Y, um, a random number with a step. So you could say like, give me a random number between two and three with a step of point one. It might give you 2.1, 2.2, 2.3. But there's also methods for random arrays. Um, so you can shuffle an array. You can grab a random item from an array. You can say, give me three items from this array and repeat them if, if you hit them multiple times or, or don't. Like, I've done, I've written that many times, right? You have a list of people's names.

• 12:45Scott Tolinski?

  Yeah.

• 12:45Wes Bos?

  You want to grab three people. You shouldn't have the same person twice, um, but then some cases you do want it, right? So it's taking that all into account. Random weighted, where you can weight certain items more than others, which is kind of cool. There's a whole thing for random distribution. It's, it seems like the ultimate random toolkit. And I hate having to write that, like, simply, even just random number between 10 and 40. That's such an annoying thing to have to. Go and grab a utility method for it or whatnot. So I'm very excited about this.

• 13:22Scott Tolinski?

  I will say even like the, even as far as like the random, the number method here, like you said, having a step. But that like allows you to, again, have a step of potentially, you know, .01 or whatever. Or like int, you can get a random int if you, if you want to specify it as being an int or a big int. I like this random dot Boolean returns.

• 13:47Wes Bos?

  Oh, yeah.

• 13:49Scott Tolinski?

  So you can get a random Boolean and it by default is weighted 50/50, but you can wait it. You can wait it so it returns true more often than.

• 13:58Wes Bos?

  70% of the time.

• 14:00Scott Tolinski?

  Right. I, that sounds great.

• 14:03Wes Bos?

  Yeah. Yeah. It's, it really has thought of everything. I went, went through it. I made examples for everything in here and it really makes sense. It is not importantly, it is not cryptographically random.

• 14:15Scott Tolinski?

  Mm hmm.

• 14:15Wes Bos?

  Meaning that you should not use this for things like generating private keys or tokens or anything like that. There are web crypto APIs for that, which use truly random algorithms that are much more computationally intensive. So if you need it for that, then, then you should. People are a little up in arms about that not being cryptographically random. But like, man, I just got an array of names I need to shuffle.

• 14:44Scott Tolinski?

  You want to be performing.

• 14:46Wes Bos?

  I'm not using this to create passwords. The thing is that people are going to use this to create random IDs or random passwords. And when you're, I don't know, putting out some new syntax token or something like that, it's going to be, you're going to get stolen from.

• 15:03Scott Tolinski?

  Yeah. Well, one, one thing that is nice about this is it does seem like it's very poly fillable.

• 15:07Wes Bos?

  Yes. Yeah. All, all of these methods are, are very poly fillable. So you could, once this moves forward, I certainly would not use it yet. But once it hits like a stage two or three or something like that, maybe we can start implementing this and bring it into your applications. Anytime you need to use a random API.

• 15:28Scott Tolinski?

  Yeah, I love it.

• 15:29Wes Bos?

  One thing that is, comes along with this proposal is another proposal for a seeding algorithm. And the idea with seeding something out as random is you want them to be. Predictably random every single time. So if you've ever used like a faker JS or any one of these APIs that creates random names or random cities and whatnot. When you're writing tests for those, you often need those values to be the same every single time. Because if there are random values every time, your test would not never pass. So by seeding something with random, you'll know that you'll get the same value every single time that you call it.

• 16:12Wes Bos?

  So if I call random not random, it's always gonna, with a certain seed, it's always gonna give me 0.4. Every single time that I call it in that instance, but then I call it again, it's gonna give me that same number. So it's predictably random, which in my case, I've only needed that for, for testing. Have you ever, ever need predictably random in anything else? I guess if you need to be able to reproduce a list.

• 16:39Scott Tolinski?

  If you need to reproduce a list.

• 16:40Wes Bos?

  Without saving it. Like, let's say you have a list of names. You could save the seed and then you could derive the random list the same way every single time. Without having to save the order of it. Yeah, it's, it's a seed that you save.

• 16:55Scott Tolinski?

  You know what would make sense about that? Every, every year we do, you know, like football squares and I have to do them like randomly. And since I'm the one doing them randomly, nobody trusts that I'm going to, a lot of people trust me because I do it every year and I'm always fair about it. But like, I want to have some verification that I didn't just pull these out of my ass. So I just take like a screenshot of them after I do it. But like, if you could share links with the seed, that seed would provide a proof that, that exists as a thing that we did.

• 17:26Wes Bos?

  Yes, you could share the seed.

• 17:29Scott Tolinski?

  Yeah.

• 17:30Wes Bos?

  So you would randomly generate a seed and then that seed would then be shareable. And then anybody else on their own accord could then derive the random values from that in the way that you're saying.

• 17:44Scott Tolinski?

  Yeah, or just load it as a parameter.

• 17:47Wes Bos?

  There's probably no way for you.

• 17:51Wes Bos?

  To generate the seed.

• 17:54Scott Tolinski?

  Because they're always long numbers. I mean, it would be tough to work backwards from a seed. Yeah, I'm sure there's ways you could do it. But like, I think about like Minecraft has seeds. So like, if you create a world that's really cool and you want somebody else to be able to then be able to create that same world on their own. So it's not like you're joining the world, but it's like recreating it. They do that via a seed.

• 18:16Wes Bos?

  Oh, yeah.

• 18:17Scott Tolinski?

  A lot of games use seeds in that way.

• 18:20Wes Bos?

  Interesting. Yeah, I guess you could just come up with seeds until you found one that was your name first and then share that seed.

• 18:28Scott Tolinski?

  Of course.

• 18:29Wes Bos?

  So the world is not, not totally solved yet. Next one we have here is array dot from a sync. So you know, array dot from will take an iterable. And let's take a sec for explaining an iterable. An iterable in JavaScript is a piece of data, a data structure that can be iterated over. It can be looped over, right? And obviously, arrays are probably the most simple or the most common one. But there's many other types of data in JavaScript that can be looped over, right? You can loop over objects with a for of. You can loop over strings and get every single character. Maps and sets can be looped over. Node lists are if you query selector or something, that's not an array, that's a node list.

• 19:13Wes Bos?

  And then probably the biggest one is, is like generators. If you have a generator function, you can loop over those. And every single time that you loop, you get the next item from the generator. So iterables can also be asynchronous, meaning that you can await inside of them. And when you have any asynchronous iterable, you sometimes want to simply just convert all of them into an array of their end values. And it's similar to how sometimes you want to simply wait for like promise dot all. And wait for all of the items to be resolved. If you want to do them all in asynchronously,

• 19:57Wes Bos?

  if you want to asynchronously run them, but you want them to run in series, then you may want to use the array dot from a sync. And what that will do is it will take an iterable, which has a sync values in it, and then it will spit out just a straight up array of all the end values in there. So that will be handy. Well, that's not something I run into all of the time, but certainly in like tree walking, a lot of times in Node.js, you're doing directory traversal. You're searching for something. You don't necessarily know how many items there will be in that iterable, because you haven't reached the end of it. That is a very handy use case for iterables and generators.

• 20:40Wes Bos?

  And this array dot from a sync will be nice. And working with streams as well, I think this will be really helpful for as well. We're like, I don't care about every single hunk. I just give me the end piece of data that comes out the other end.

• 20:55Scott Tolinski?

  Neat.

• 20:56Wes Bos?

  Up certs. We've used up certs for many, many years. When have you, when have you used an up cert?

• 21:02Scott Tolinski?

  You know what? I use an up cert mostly in database stuff.

• 21:05Wes Bos?

  Yeah, me too.

• 21:07Scott Tolinski?

  In up cert, what it does is it updates the record if it exists and it inserts it if it doesn't exist. That can save you doing a simple conditional saying, does this thing exist? If it does, then do this. Otherwise, do this. So an up cert can turn them into one line, which is typically how I'm using it. Some people don't like up certs, but I, they don't bite me. I don't, I don't know. I've never had them bite me.

• 21:31Wes Bos?

  So much of my coding is simply checking if something exists. And if it exists, then I want to update it. And if it does not exist, I want to then create it with that value. So this proposal here is for adding up cert to maps and weak maps. And the most common use case will be when you're like counting through items. And the first time that you encounter a key, like let's say you're, you're looping over a list of clothing and, and you get shirt, shirt, pants, right? The first time you hit shirt, you check. Have I, have I started counting shirts yet? No. Okay. Now create a key called shirt and set it to zero.

• 22:10Wes Bos?

  Then you hit it again. Okay. Well, now it exists. So I'll grab the value out and then I'll increment it by one and then et cetera, et cetera. Right? The method name here is called get or insert, which will basically say, get me this value. Or if it is not there, then insert it. And the first or the second argument to the method is going to be the default value. And that will be, so many times you have to check if it's there. I do all this wacky shorthand to say like, if it's there or not. So it's just another nice little one. It will not be added to arrays or probably, no, arrays doesn't make sense.

• 22:52Wes Bos?

  It's not added to objects because you should probably be using a map anytime you're doing any sort of dictionary or collection work. Maps are kind of underused and I think one of the big reasons is because it's, you can't JSON stringify it without like a custom stringify algorithm. But I'm a big fan of maps.

• 23:13Scott Tolinski?

  Yeah. Uh, the next one here is clamp. Uh, I love Wes has a note says, Scott, you love clamp in CSS. I do love clamp.

• 23:21Wes Bos?

  Scott's always clamping everything here and there.

• 23:23Scott Tolinski?

  Yeah. Insert the, uh, I love lamp, I love clamp, uh, for sure. Clamp is wonderful. And what is clamp? And honestly, uh, which is very odd. I thought clamp was already in JavaScript. And it turns out I've always just been, uh, writing an implementation of it every single time. Or, uh, no clamp, clamp is in CSS before, we got clamp in CSS before we got it in JavaScript.

• 23:46Wes Bos?

  Yeah, you're right.

• 23:47Scott Tolinski?

  It's a function that constrains a value between an upper and a lower bound. So basically, uh, typically it, it takes a number, it takes a minimum and it takes a maximum. Um, in CSS, these are in a different order, but hey, you take a number, a minimum and a maximum. And what that does is say like, all right, uh, this can be useful if you have like an animation that needs to happen from zero to 100. And you're providing it a value of 120 or some. Like that. And this is going to make sure it doesn't go above that upper bounds. And likewise, you go less than zero, it's going to return zero. So it's going to keep it in between these two bounds. Yeah, this is endlessly useful for animations, for math.

• 24:30Scott Tolinski?

  You see it a lot and they say, see the P5 JS demo. You see it a lot in stuff like P5. Again, when you're working with numbers and you need to constrain them to different times. So, uh, yeah, this, this exists everywhere. There's a ton of user land implementations, right? There's clamp inside of, uh, uh, low dash, 3JS, P5, Phaser. Like anything like that uses clamp. And, and I've written my own clamp a number of times because it's not, not that tough.

• 25:00Wes Bos?

  It's a one liner, right?

• 25:02Scott Tolinski?

  Yeah. Now we got, uh, a clamp proposal in JavaScript, which is at stage two. And I think there's no reason why this shouldn't just be, uh, just rocket shipped into JavaScript because, yeah, why do we need all these user land implementations of this when we got it even in CSS?

• 25:21Wes Bos?

  A question I often get whenever I post about these things, specifically the random one. Are people like, why do we need this? Like, why, why are we adding all this stuff to the, to the language? And like, why not just import a module? In some cases with the clamp one, people will be like, why not just write a one liner? Where it's like math max. And I hate writing one liners. You have to have like a utilities folder or you NPM install. Like I have a one liner NPM package that's installed like a hundred thousand times a week. And just because it's, it's annoying to, to have to do that. But with the like random one, if you're shuffling an array of 20,000 items.

• 25:59Scott Tolinski?

  Right.

• 25:59Wes Bos?

  And I don't want to do that in JavaScript. You know who's very fast at moving around data pointers? The lower level APIs that the browser is, is written in. So certainly is a performance thing when you get into very large functions and, and doing lots of complicated math in random land. And then simply things like clamp or it's a one liner. It's just so much simpler to have it built right in. And like it, that's, that seems like a standard, standard lib thing that everyone, every language should have.

• 26:32Scott Tolinski?

  It's a low hanging fruit. It exists everywhere. Just give it to us in JavaScript.

• 26:35Wes Bos?

  What else? CSS clamp, C sharp has clamp, C's plus plus, Rust, Kotlin, Dart, Ruby, Elm.

• 26:45Wes Bos?

  Python, does Python not have clamp? We gotta beat Python out. No, there is no Python clamp.

• 26:52Scott Tolinski?

  Oh.

• 26:54Wes Bos?

  Yeah, we beat him out. We beat him out. Take that, Python.

• 26:59Scott Tolinski?

  Take, take that.

• 27:01Wes Bos?

  Yes. Alright, let's get into some sick picks and shameless plugs. I got a sick pick for you today, and that is a TV show that me and my wife have been loving. Clarkson's Farm. Jeremy Clarkson.

• 27:11Scott Tolinski?

  Okay.

• 27:12Wes Bos?

  He's the guy from the car show with the Top Gear. The Brits are gonna kill me that I had to even think about that. That's.

• 27:20Scott Tolinski?

  The car show.

• 27:21Wes Bos?

  Yeah. I, I actually started watching Top Gear after I watched Clarkson Farm. I was like, oh, this is actually pretty funny.

• 27:26Scott Tolinski?

  Yeah, I like Top Gear.

• 27:27Wes Bos?

  But Jeremy Clarkson's the guy from Top Gear, and he bought a farm in the Coxwells of Coxwells? Of, um, the British countryside. It's beautiful. And like, he's got animals and he's starting up like a, a pub and it's super interesting. The guy is absolutely, like, not dialed, but he's a lot smarter than he leads on. And it is extremely entertaining, so I would highly recommend it. I think it's on Amazon Prime is where we watch it.

• 27:59Scott Tolinski?

  Yeah, I have not seen. Yeah, I, I, I like him in general. I liked, like I said, uh, um, Top Gear, so maybe give it a go. We've been watching just absolutely trash, trash TV lately, so trash TV as a genre, I'm gonna say.

• 28:14Wes Bos?

  Okay, like, like what?

• 28:15Scott Tolinski?

  Oh, man, like, uh, Vanderpump Villa, which I gotta say Hulu. It's on Hulu. Hulu sucks. It sucks. The apps suck. You pay for a service and then you gotta watch 10,000 shitty ads. I was, we were, we were laughing that the ads are so bad on Hulu that syntax could, they must be charging nothing for them. Because syntax could, could reasonably have a better ad on Hulu than any of the garbage that's on there. It is crazy and they make you sit through so many of them and we're paying for it. It is like, it is absolutely wild.

• 28:53Wes Bos?

  I gotta put you onto Streamio. That's, that's all I'll say is, is go check out Streamio. Cause I, I'm, I'm saying with you, I, we pay for, I don't know, probably six or seven of these. Netflix and Disney and, and Amazon Prime and Discovery. And friggin' half the time, they can't even find what they want. Or it's like covered in ads, so. Definitely check out Streamio, very good.

• 29:16Scott Tolinski?

  Okay.

• 29:17Wes Bos?

  Torrent streaming. It's like a Netflix experience with like a torrent backend. It's just instant.

• 29:22Scott Tolinski?

  I will, I will check that out because we gotta see the secret lives of Mormon wives and Vanderpump Villa and all this shit that's on Hulu. Man, I cannot believe how bad the Hulu apps, like no shade on the developers because I'm sure it is a bureaucracy thing, but like, man, Netflix comparatively on the TV app, like you can't complain that the TV's underpowered or something like that because the Netflix app smokes it in every single regard. Netflix, shout out to Netflix for actually taking their engineering seriously.

• 29:59Wes Bos?

  There was a guy at the meetup that worked on the Plex player and he was telling us about like what's built in JavaScript and what's native and it's a very interesting world and seems like a very painful world to test on all of these random TVs that are $214 at Walmart, but you gotta run a high-performance 4K stream decoder on it.

• 30:25Scott Tolinski?

  I will tell you that Plex has got a much better app than Hulu does. So shout out to Plex for doing what Hulu can't do with whatever their budget is. That's the end of the Hulu rant, folks. Sick pick for me today is I got a four-port charger. It is USB-C in all regards and one of those ports does up to, I think maybe even more of them. I think two of them might do 140 watts. So they, they have like a one, yeah, 140 watt and then 140 watt and then a 40 watt and then a USB, a normal USB on there. And this thing has, this is a charger with a screen. It's the Anker Max.

• 31:09Scott Tolinski?

  USB-C charger, four-port, multi-device, fast-charging, advanced, can power-adapted, intuitive tech controls for MacBook, iPhone 16 Series, Samsung Galaxy Pixel, and more. It's Anker. It's very nice. It has a little screen on it that shows you how much each device is drawing. It is awesome.

• 31:27Wes Bos?

  So I have, I have this one, which I sickpicked years ago. It's the Exino Pro. And whenever you're unsure if a device is charging, or if it's charging fast enough, or whatever, being able to see the actual draw on the thing, I have a couple cables that have it built in, is so, so key to tell if something is dead or not. Especially if you have like an iPad. I've fixed a few iPads in the past. And by watching the wattage spike and go down, you can tell if it's, if it's like short-circuiting. So that's so, so good to be able to see the actual pull.

• 32:04Scott Tolinski?

  Yeah.

• 32:05Wes Bos?

  That's great. You don't even need to carry around a MacBook charger anymore if you have one of these.

• 32:11Scott Tolinski?

  No.

• 32:12Wes Bos?

  And they're smaller, and they fit in your, you just put it in your bag, and you're charging for all your gear, including your laptop when you're traveling.

• 32:18Scott Tolinski?

  This is specifically why I bought it. Because when I was in Barcelona, I brought a bunch of chargers, and half my cables didn't work. And then I realized, oh, I only brought one international adapter. So therefore, I have one international adapter, and I got one thing I can plug into it, and I can charge one thing at a time. So I got this to load up my stuff for my Amsterdam trip. And yeah, shout out to Anker, always making the good stuff.

• 32:43Wes Bos?

  That's great. Are you, are you full USB-C in your whole life?

• 32:47Scott Tolinski?

  Yeah.

• 32:48Wes Bos?

  I've been lamenting it.

• 32:49Scott Tolinski?

  I have, I have one old iPad that the kids use that uses the crappy iPhone adapter.

• 32:56Wes Bos?

  I got, I got this recently, because I'm almost there. My phone is Lightning, which I'm almost, I'm waiting for the next one. And my keyboard is Lightning, which kills me, because I'm, this keyboard is gonna be around for years. So I got this little thing that just clips on top, converts USB-C to Lightning.

• 33:17Scott Tolinski?

  Yeah, that's good.

• 33:18Wes Bos?

  And then it just dangles on it. And then you always at least have one to be able to charge things.

• 33:25Scott Tolinski?

  Okay, yeah, I can get with that.

• 33:27Wes Bos?

  Beautiful. All right, that's it for today. Thank you so much for tuning in and we'll catch you later. Peace.

• 33:33Scott Tolinski?

  Peace.