News for hackers. Stuff that matters.
Re:The optional chaining operator, “modern” browsers, and my... by null_object on Tuesday January 11, 2022 @01:51PM (#29895910)
> iOS also doesn't allow the browser to be updated after the hardware has reached end-of-support.

Just simply not true. Plenty of browsers are still updated for iOS12 and 8-year old hardware like the 2013 iPad Air (which I still use every day)

Edit: getting downvoted - while writing this post on iCab Mobile browser which was updated less than a month ago...

Follow-up: Well I tested the language ‘feature’ in this browser - and though it didn’t crash, it didn’t run the function either. I’d forgotten what a sh*tshow of crappy and unnecessary garbage modern front end JavaScript development was.

Re:The optional chaining operator, “modern” browsers, and my... by modeless on Tuesday January 11, 2022 @01:55PM (#29895958)
Apple has fooled you. Those aren't complete browsers. Those are simply UI shells around the system version of WebKit which cannot be updated or bypassed or replaced. No new web platform features will be added, no bugs fixed, and security holes are not guaranteed to be addressed.
Re:The optional chaining operator, “modern” browsers, and my... by heresaPizza on Tuesday January 11, 2022 @02:18PM (#29896350)
While what you said is true, iOS 12 still received some security fixes, so the total support for the iphone 5s is 9 years and 8 for the 6. Critical bugs shouldn’t be that big of a threat (considering that even up to date phones are colanders.
Re:The optional chaining operator, “modern” browsers, and my... by ksec on Tuesday January 11, 2022 @03:42PM (#29897544)
>Edit: getting downvoted

You are getting downvoted because Webkit Engine is not updated with the browser. In this case iCab Mobile Browser. As noted in other reply it is merely a shell or skin on top of the OS Webkit Engine. Hence you are objectively wrong.

Re:The optional chaining operator, “modern” browsers, and my... by mcguire on Tuesday January 11, 2022 @04:09PM (#29897931)
Technically, I downvoted because

"I’d forgotten what a shtshow of crappy and unnecessary garbage modern front end JavaScript development was.*"

while essentially true, has nothing to do with the question at hand.