The optional chaining operator, “modern” browsers, and my mom

Re:The optional chaining operator, “modern” browsers, and my... by rossipedia on Tuesday January 11, 2022 @12:59PM (#29895101)

You absolutely can. The issue isn't _using_ the optional chaining operator, the issue is that it wasn't compiled down to something that older platforms can understand. Developer quality of life doesn't have to conflict with what's supported on older platforms.

[ Parent | on HN ]

Re:The optional chaining operator, “modern” browsers, and my... by teawrecks on Tuesday January 11, 2022 @01:08PM (#29895222)

And what do you do when the only way to support a new feature on a legacy system necessarily introduces a security risk? Special case it?

[ Parent | on HN ]

Re:The optional chaining operator, “modern” browsers, and my... by rossipedia on Tuesday January 11, 2022 @03:19PM (#29897236)

That's a hard problem to solve, and I don't think there are any easy answers. It depends on many factors. What kind of business, what the risk/threat model is, cost/benefit analysis, all that kind of stuff.

[ Parent | on HN ]

Re:The optional chaining operator, “modern” browsers, and my... by programmer_dude on Tuesday January 11, 2022 @01:07PM (#29895211)

Sounds like a good solution to the posted problem. But the device user should be allowed to upgrade their browser and OS too.

[ Parent | on HN ]

Re:The optional chaining operator, “modern” browsers, and my... by Bilal_io on Tuesday January 11, 2022 @03:22PM (#29897286)

Sometimes users use older browser because of ignorance, they don't know how to upgrade, or because they don't want to.

[ Parent | on HN ]