This week, we’ve got a TS/JS family reunion, an extended metaphor for React 18 involving a scary kids movie from the ’90s, and a
So, come crawling back, eh?
TypeScript comes crawling back
Why tho? TypeScript is great, but it still requires a build step to remove those pesky types so that JS engines can actually run the code.
The Bottom Line: I haven’t seen this many opinions on something since my Crossfit loving, vegan Uncle came over for Thanksgiving.
The jank is… inevitable [sponsored]
Clerk.dev — user management, now with less pain!
There’s only one lesson I hope my kids learn from me: “the best code is the code that you don’t have to write/maintain.” (“Be a good person” was a close second place.)
So if any of my offspring ever builds an app, they better use Clerk.dev for all their user management stuff.
It also integrates super smoothly with React, Expo, Next, and Gatsby to save you even more time.
Your users don’t care how your user management system works — they just want it to work, so they can get busy losing money on NFTs, gambling on virtual horses, or whatever your app does.
👉 Check out Clerk.dev’s free tier and stop worrying about the boring code nobody cares about.
I’m not afraid of you anymore!
Facing the React Rhino
Here’s a hot take for all the ’90s kids who were raised on creepy Tim Burton movies: React 18 has basically become the giant rhino from James and the Giant Peach.
Let’s take a look at the evidence:
But after months of waiting, it’s almost time for us to face the beast. The first React 18 RC came out last week, which means we’re only (checks notes) “at least several weeks away” from the general release.
What to expect:
But there’s good news: the React 18 upgrade shouldn’t actually be that scary, even with all the big new features. That’s because the React team has smartly chosen to avoid an all-or-nothing Concurrent “Mode” approach. Instead, they’ve gone with a gradual, opt-in adoption process for Concurrent “Features.”
This means you can upgrade your apps to React 18 with minimal or no breaking changes, then start introducing the fancy new features whenever you want — eating the
Botton Line: Lots of frameworks and libraries fall into the trap of thinking that good developer experience simply means, “add more features as fast as possible” (*cough* Vue *cough*). But it’s cool to see the React team being just as thoughtful about how they introduce new features as they were with the creation of the features themselves.
Has it taken a long time? Yes. Will it be worth it? I wasn’t totally sure at first — but then I saw that React 18 is also killing support for IE, and now I’m 100% on board.
🔬 Spot the Bug — Sponsored by WorkOS
_WorkOS gives you Lego bricks for adding enterprise features to your app. You can use their modern API’s to add stuff like Single Sign-On (SAML) and SCIM user provisioning in a few minutes, instead of a few months.
🔬 Spot the Bug Solution — Sponsored by WorkOS
When you call
There are two ways to fix this. One option is to call
The second option appends the item to a new array with
Delivered to 112,202 developers every Monday
This is the first ever newsletter that I open a music playlist for and maximize my browser window just to read it in peace. Kudos to @uidotdev for great weekly content.
The Bytes newsletter is a work of art! It's the only dev newsletter I'm subscribed too. They somehow take semi boring stuff and infuse it with just the right amount of comedy to make you chuckle.
Bytes has been my favorite newsletter since its inception. It's my favorite thing I look forward to on Mondays. Goes great with a hot cup of coffee!
I subscribe to A LOT of dev (especially JS/TS/Node) newsletters and Bytes by @uidotdev is always such a welcomed, enjoyable change of pace to most (funny, lighthearted, etc) but still comprehensive/useful.
Literally the only newsletter I’m waiting for every week.
Bytes is the developer newsletter I most look forward to each week. Great balance of content and context! Thanks @uidotdev.
The sense of humor and structure of the Bytes Newsletter is first class and the information that comes with it is enough to make a mini course.
Very few newsletters manage to be useful and not very boring. @uidotdev manages to achieve these pretty effortlessly. You can almost see Tyler chuckle as he writes them.