This presentation gives an overview of cutting-edge JavaScript development techniques to build modern web and Node.js apps. Discover which features to expect in Chrome and Node.js soon, how the V8 engine optimizes for them, and how to improve real-world performance and stability on the Web and in Node.js.
Speakers:
• Mathias Bynens https://twitter.com/mathias
• Sathya Gunasekaran https://twitter.com/_gsathya
More info:
• https://v8.dev/
• https://twitter.com/v8js
Watch more #io19 here:
Web at Google I/O 2019 Playlist → https://goo.gle/io19web
Google I/O 2019 All Sessions Playlist → https://goo.gle/io19allsessions
Learn more on the I/O Website → https://google.com/io
Subscribe to the Chrome Developers Channel → https://goo.gle/ChromeDevs
Get started at → https://www.google.com/chrome/dev/
T60250
Original source
27 responses to “What’s new in JavaScript (Google I/O ’19)”
What about jQuery? Do think we have to forget completely this script language to the native JavaScript. I believe the jQuery is the best way for those who have more difficulty with the native language JS. Your feedbacks are welcome.
❤️❤️
Wherever you go there's an Indian ..Proud
Linux and google love node.js
Class is messing
Finally weak reference, make my life so much easier, like I can finally trivially log CSP reports in memory without worrying about memory leaks.
The weak ref proposal doesn’t seem very clean.
23:23 தமிழ் மொழி. glad to see my native language. new flatmap method quite good
Imo, it's actually really unfortunate private class fields were implemented. Now there will be some cases where you can't inspect the content of objects used by some other websites, which seems like both a security hazard and also just bad manners imo… Anyway, what was the problem with using _ to dictate private variables? Finally what's with the screwed up syntax? idk… Not happy about this feature personally.
Things move so fast and get more complicated, so have to learn all time to keep up and even then I always feel like I’m behind..
Stable sort is the best change. Couldn't care less about private class vars.
We implemented something like Promise.allSettled before. We called it Promse.allMost 😂🤣
82 DISLIKES FROM IE
Private class fields and global this <3
Allways top notch quality! kudos
private class fields 6:57
Regex matchAll 9:16
Numeric literals 10:19
BigInt formatting 11:50
flat & flatmap 13:23
fromEntries 15:28
Map to Object conversion 16:47
globalThis 19:18
Stable sort 20:00
Intl.RelativeTimeFormat 22:45
Intl.ListFormat 24:29
Intl.DateTimeFormat -> formatRange 26:32
Intl.Locale 27:10
Top-Level await 28:12
Promise.allSettled/Promise.any 31:13
WeakRef 32:30
I love how IE's compatibility is not even considered! 😂
God that hash private field class annotation is ugly. Why could they not just use typescripts implementation? Just add private in the front of it
This comment is just for fun… for all others, polyfill is available… 😉
this is sick
I want to be Professional React developer.
Promise.allSettled will be really helpful.
All the features doesn't support Internet Explorer…😂😂
Cool, it is worth sharing.
Thanks, TC39
I will expect that new APIs and new virtual parsing engine for universal byte code
Safari is the new IE 😂