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.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
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.