11–20 of 623 posts
Earlier quoted context omitted.
So true. I have this uneasy reliance on Chrome for supporting PWA's properly since Mozilla lost interest. It's a life/routine manager for people with horrible memories. Chrome stands alone in supporting web push notifications :S
Safari supports web push notifications. I have never wanted them.
Earlier quoted context omitted.
So true. I have this uneasy reliance on Chrome for supporting PWA's properly since Mozilla lost interest. It's a life/routine manager for people with horrible memories. Chrome stands alone in supporting web push notifications :S
Safari supports web push notifications. I have never wanted them.
From my perspective, Apple's conservative attitude is a positive. There are all sorts of web techs that enable the possibility of increased tracking, of websites being generally malicious, of all sorts of things that I don't want.
Historically Apple has been on my side and I will continue to appreciate that until demonstrated otherwise.
I take the points about not supporting CSS features and some of the other web standards, and the issues around Apple's 30% cut, and I'd add that some of Apple's censorship (eg. banning Parler for a while, asking Telegram and Tumblr to not allow access to certain content) is troubling, but I don't think the way around that is letting any cowboy with a web app send notifications and access bluetooth willy nilly.
> Apple dragged their feet in adding support for PWAs in Safari, and when they finally did, limited the capabilities of a PWA so that native-like app functionality wouldn’t be possible, like notifications or a home screen icon shortcut Websites can get Home Screen shortcuts; this has been a thing since the original iPhone.
This is just false, or at best only half of the story to make a false equivalence. IE was cutting edge until Firefox. The biggest problem with IE was all the insanely weird shit it did, not missing features. It would “fix” missing tags, that would then be broken on every standards compliant browser, had active x, and had an absolutely insane amount of security bugs.
Mobile safari ain’t the IE of the modern day. It’s just fucking not. I’m sorry. Chrome is closer to IE than Safari because of market share AND developers developing exclusively for it forgetting anything and everything else.
Does mobile safari still suck? Sure. But we don’t need to call it IE or constantly drone on with comparisons to IE. Let something suck in its own unique and shitty way, please.
1. they can be abused (PWAs)
2. are complex to implement (WebRTC – for the longest time the recommendation in the WebRTC community if you wanted to build a C++ app was to bundle a good chunk of Chrome's libraries)
3. or could be bad for battery (web workers)
So yeah, it makes some developers' jobs harder but generally there's a good reason for punting features.
>Why did developers and software engineers hate IE so much? Because IE was seriously outdated, lacking support for cutting-edge web APIs and technologies enabling the modern websites and web apps we use today.
This meant you could guarantee that any website you designed and that you ensured followed web standards and rendered perfectly on every browser known to man would either break or display completely differently on IE. So you had to then pollute your lovely clean code with countless ugly hacks and conditionals just to ensure your site rendered the same on IE as it did everywhere else.
That was why every web developer not working in a Microsoft bubble loathed that browser.