Although many of these features may not be essential for the development of your Web application, they are giving possibilities that could be achieved before with tricks or a lot of verbosity.
Yea, constant legacy worrying and xbrowser issues push me further and further away from the frontend. Nodejs is far more comfortable and user friendly environment than whatever google next patch will bring, safari wont support or client with ie11 will complain ;)
I'm PhD. in Computer Science from Málaga, Spain. Currently, I am teaching developers and degree/master computer science how to be experts in web technologies and computer science.
I hope to complete the series although ES6 has already been written enough. However, the ideal is to have a place where the news that the standard brings us annually is summarized and updated.
Yea, constant legacy worrying and xbrowser issues push me further and further away from the frontend. Nodejs is far more comfortable and user friendly environment than whatever google next patch will bring, safari wont support or client with ie11 will complain ;)
Why don't you try a transpiler?
I use transpiler. That doesnt save you from different implementations of features in different browsers.
Finally,
??. I hope with works fine just like?.in TypeScript.Can I use this in
esnext?Thanks for the write-up! Any word about browser adoption of these features?
Either way, they should be in core-js / babel soon, which will help a lot (especially a fan of using optional chaining 🥳)
I keep this compatibility table bookmarked.
Thanks for taking the time to put this together, great high level summary of some exciting upcoming features!
Thanks Calvin!
I hope to complete the series although ES6 has already been written enough. However, the ideal is to have a place where the news that the standard brings us annually is summarized and updated.
Nice article, thank you for the explanations.
I have written an in-depth blog post on the same topic
abhishekdeshmukh.com/blog/javascri...
Feel free to check it out
In Nullish section falsy examples:
const value = values.numberValue || 300; //300
I think you wrote values.numberValue instead of values.zeroValue? Because it's supposed to return 400.