Notice our fresh new look? π π»ππ»ββοΈ
Big thanks to DEV's Content Creator @rachelfazio for designing a new header for #DEVDiscuss!
Ok, time for the main event: Our audiences on Twitter and Mastodon selected an excellent discussion topic today, so let's get into it. π
Inspired by @jasmin's Top 7 post, tonightβs topic is...what's new in ES2023?!
If you're not familiar, updates to ECMAScript for 2023 have been finalized! (Ok, kind of β they're not final until July, but they've reached Stage Four, meaning that they're all-but-certain to be final updates). You can learn more about the updates from TC39's site.
Questions:
- Which of these updates are you most excited about?
- Did any of these updates confuse, frustrate, or disappoint you?
- Are there any updates you were hoping to see this year but didn't?
- Any triumphs, fails, or other stories you'd like to share on this topic?
Top comments (2)
These ECMAScript 2023 updates certainly have some interesting additions! As a Python and PHP developer looking to integrate more Node.js into my work, I find the "Change Array by Copy" proposal particularly appealing. The idea of handling arrays without the risk of unintentionally mutating them aligns well with practices I've appreciated in other languages.
Hashbang standardization is great! Considering JavaScript's increasing presence in server-side scripting, it's a logical step, and to me a monumental nod to JavaScript's expanding roles!
In terms of expectations, I had hopes for some enhancements around JavaScript's asynchronous behavior. As someone coming from a background of Python, PHP, and a bit of Go, this is an area I've found challenging in JavaScript. However, these improvements aren't always immediate and I'm optimistic about future updates.
As for stories, I've been learning Node.js, and to learn, I typically make things. Trouble is, I've gotten bored! I've made every type of project in two languages now. That being said, I have occasionally spent some time messing around with Node.js, making small projects with it.
To make a long story probably still long, I'm currently considering replacing a PHP backend with Node.js for a personal project I started when I was younger and found on my laptop recently, which was a minimalist code pastebin with account and comment functionality. Back then, I used a tutorial on a blog I googled to help me make it. Lately, particularly for Node.js knowledge, I've been using Dev posts as a significant source for that kind of knowledge. Big kudos for that.
Given the continuous improvements in JavaScript, like those in this update, it's becoming a more and more compelling option to many. It's an interesting journey, making small transitions between a language I know well to one that's becoming increasingly robust and versatile.
If you run babel or any polyfills, using the latest features is great. They may give you some long expected improvements.
If you try this directly in the browser, this might easily break your site, as execution may stop if it encounters unknown features. You can check out the compatibility on pages like Caniuse.
From my experience, you are relatively save to run features, that have been introduced 3-4 years ago. This will possibly run on most devices currently in use. But even common features like for...of have been adopted lately by some browsers (Opera mobile - Jan. 16, 2023), so it is always safer to use the more common features.