I tend to think of client first. UX is more important than writing one word less. for a developer. between users having slow internet speeds, limited networks and not the greatest machines bringing one poly-fill here and there vs zero can make a huge difference. If you are making something just for you or limited public then why not but the difference in code between the statement I used vs using ||= is not that big that it would justify using a poly-fill on my end. If we were talking about a promise polyfill for example that would be a different matter.
But in the end everyone codes differently. So whatever suits your coding style then use it.
One that I love is this:
The or operator works the same as an elvis operator.
This is useful if you want to display a default value when you can't get data from an api or if some data is null for a key.
This can be chained with objects
With ES2021 we have
||=
:)Which makes the syntax even cooler
I made a video about new features here:
youtu.be/hxmFYToenxE
True but not fully supported yet
With the right babelJS version it is ;)
And then you're bringing big pieces of extra code for not much đ good way to slow websites.
I would say that developer convenience is more than a lot. Also, few bytes of code for polyfill, definitely will not slow down the website.
I tend to think of client first. UX is more important than writing one word less. for a developer. between users having slow internet speeds, limited networks and not the greatest machines bringing one poly-fill here and there vs zero can make a huge difference. If you are making something just for you or limited public then why not but the difference in code between the statement I used vs using
||=
is not that big that it would justify using a poly-fill on my end. If we were talking about a promise polyfill for example that would be a different matter.But in the end everyone codes differently. So whatever suits your coding style then use it.
Love this one too, it's also useful to prevent errors when destructuring something that could be undefined:
This can prevent errors such as "Cannot read foo of undefined".