4 ms·

> Forced to use Safari. That's a huge issue actually. See the story the other day about Optional Chaining operator breaking iOS 12 Safari[1] and there's nothin

by rekoil 5y ago

> Forced to use Safari. That's a huge issue actually. See the story the other day about Optional Chaining operator breaking iOS 12 Safari[1] and there's nothing users can do about it even if the hardware is perfectly capable of handling Optional Chaining operators. If I could just install another browser then that issue disappears. But I can't do that, because Apple will never allow any other web renderers on the App Store. [1]: https://news.ycombinator.com/item?id=29894300 https://news.ycombinator.com/item?id=29894300

HWR_14 5y ago
The day Apple allows other browsers is the day you can put a countdown clock on the entire web only working with Chromium in a way that Microsoft could only dream of during their IE on the desktop period. Not because Chrome is better, but because Google has been very effective at using its dominant web position to force people to "upgrade" to Chrome. Even Microsoft, which invested huge amounts of money in Edge, packed it in when Google kept telling people that Edge was going to kill their firstborn (or whatever other tactics they use, like allegedly making YouTube not work properly.) So, yeah, I'm fine with allowing other browsers - a few years after we've seen Google successfully broken up. Meanwhile, I'm fine with websites just not using Optional Chaining operators. It's syntactical sugar. And frankly, rapid iterations on JavaScript, adding optional features only supported on Chrome and then making people think the web is broken without them, is a huge source of Google's ability to bully people into using Chrome.
- rekoil 5y ago
  I agree it's a stupid problem to have when simple solutions exist (use cool features while developing, babel them into old boring code that runs on your smart fridge from 2002), but it's a problem nonetheless and a problem we wouldn't have if it was possible to install a new non-Safari/WebKit browser on iOS 12.

by rekoil 5y ago

HWR_14 5y ago

The day Apple allows other browsers is the day you can put a countdown clock on the entire web only working with Chromium in a way that Microsoft could only dream of during their IE on the desktop period. Not because Chrome is better, but because Google has been very effective at using its dominant web position to force people to "upgrade" to Chrome. Even Microsoft, which invested huge amounts of money in Edge, packed it in when Google kept telling people that Edge was going to kill their firstborn (or whatever other tactics they use, like allegedly making YouTube not work properly.) So, yeah, I'm fine with allowing other browsers - a few years after we've seen Google successfully broken up. Meanwhile, I'm fine with websites just not using Optional Chaining operators. It's syntactical sugar. And frankly, rapid iterations on JavaScript, adding optional features only supported on Chrome and then making people think the web is broken without them, is a huge source of Google's ability to bully people into using Chrome.

rekoil 5y ago
I agree it's a stupid problem to have when simple solutions exist (use cool features while developing, babel them into old boring code that runs on your smart fridge from 2002), but it's a problem nonetheless and a problem we wouldn't have if it was possible to install a new non-Safari/WebKit browser on iOS 12.