News for hackers. Stuff that matters.
Re:The optional chaining operator, “modern” browsers, and my... by elondaits on Tuesday January 11, 2022 @12:57PM (#29895048)
Not even. JS developers should know to transpile their code to support users that for whatever reasons (from a long list) cannot run the latest JS version... or stick to truly standard things.

The ?. operator was included in Edge, Safari, Chrome and Firefox early 2020. According to caniuse.com, only 90% of users have browsers that support it... but depending on who your audience is, it might be much less (e.g. if you target schools, or government, there might be computers locked in older OSs or browser versions... at least that's the case in my country).

Re:The optional chaining operator, “modern” browsers, and my... by tgv on Tuesday January 11, 2022 @01:16PM (#29895354)
It is lazy, indeed, but the whole ecosystem enables it. You install some yarn based framework installer, create a project, and before you know it, it sets something like "browser-support" at 95%. That number is estimated from dubious sources, and quickly eliminates older versions, and every update discards more versions.
Re:The optional chaining operator, “modern” browsers, and my... by Zardoz84 on Tuesday January 11, 2022 @02:16PM (#29896307)
what I do it's generé a bundle for modern browsers, and another for IE11 (and by extension ancient versions of Firefox and Chrome) with the necessary polyfills