13 ms·
Safari 16.4 is an admission
- lusbuab 4y agoUsers before developers. And for Apple Apple probably comes before users. Developers want a better browser on iOS, I agree. But do they also want to support multiple different browsers on iOS, each one with its own shortcomings and quirks?
- djha-skin 4y agoI do hope WebKit gets more of this attention, if only for projects like Midori. I don't want to see the browser space get monopolized, for many of the reasons that this article touches on.
- etchalon 4y agoI don't care much for this post, but I think it is fair to say that PWA support wasn't something Apple cared about. They shipped a lot of features in Safari over the years, including many that that landed before Chrome and Firefox's implementations, and in general, Safari has remained the fastest, most power-efficient browser on macOS. But PWA-specific features weren't high on the list. Users didn't want them; developers wanted them, and Apple has rarely prioritized what Developers want over what their Users want – with both being second to what Apple wants.
- lozenge 4y agoIt's meaningless to say that users didn't want them when PWA were so difficult to install and every company was forced to invest in writing a native app instead. Of course users prefer native apps but they're incredibly expensive to maintain. Developers need the option of a PWA.
- etchalon 4y agoI'm not sure that "who cares what users want" is a valid product strategy.
- olliej 4y agoI will always choose a better quality app if its available, the problem is if you have a bunch of low cost shitty applications then no one creating actually good apps can compete on price. At that point the only option is for good apps to be astronomically expensive, or every app becomes another shitty PWA that doesn't work well at all. My honest impression is that the entire "PWAs are good" are basically the crowd that make cheap apps discovering a way to sell to Mac users without having to actually make quality software. Any time I encounter a PWA or a chrome wrapper "native" app it's just another chance to experience an app that can't do basic things like "find" correctly. The entire argument for PWAs is "it's cheaper". I have not once seen a "it results in a better UX or app".
- h0l0cube 4y ago> The entire argument for PWAs is "it's cheaper". Not necessarily cheaper to make but your revenue isn’t cut by 30%. Also your app can run almost instantly by visiting a link. App Clips and Instant Apps don’t really cut the mustard unless your app is tiny
- threeseed 4y agoWe've had native wrappers with PWA style payloads for nearly 15 years. Installing to the home screen is not the reason they never took off. It's because the user experience on them is terrible compared to native. Really is as simple as that.
- justinclift 4y ago> If you're a web developer not living under a rock, you undoubtedly got word of last week's big Safari 16.4 reveal. Sorry, but some of us have actual lives outside of our jobs. :p Oh hang on, this article is only talking about the release of some Apple beta. It's not even a release. Some people have too much time on their hands I guess...
- inopinatus 4y agoIf you prefer your release notes served without a thick dollop of vituperative bickering, they're here: https://developer.apple.com/documentation/safari-release-notes/safari-16_4-release-notes https://developer.apple.com/documentation/safari-release-not...
- deleted 4y ago[deleted]
- singularity2001 4y agodollop ~ blob vituperative ~ bitter
- pocketarc 4y ago> allowing Chromium to ship responsibly while consensus was witheld in standards by Apple It's interesting how perceptions work. You could say, "Allowing Chromium to ship whatever they want with no regard for standards bodies or their consensus", and it'd be just as accurate. Chrome is shipping a browser with a well-established goal of narrowing the gap between native apps and web apps, and so it pushes all these features for web apps. Safari seems to prioritise building a solid, fast browser for -websites-, so obviously, web app features will take a back seat. Almost everything in that list of missing features shipped in 16.4 is related to web apps. And stuff like the Reporting API, which isn't web-app-specific, hasn't been released in Firefox yet either, so it's not like Safari's behind, even if you tag it with "2018"; it sounds like there's more to that story than just "they're five years behind".
- junofan 4y agoIIRC the perception of Chrome developers was that the Google promo system was incentivizing number of commits and features at one point in time, so they were perceived to be just dumping whatever out there.
- nikanj 4y agoIt rewards changes, not just inclusions. Removal of well-liked and widely used features also gets you a good performance review.
- olliej 4y agoBack when I was involved there was a distinct impression that people got bonuses for getting commit rights, etc - so we’d get people who would swing by making the requisite 10-15 patches - generally relatively low value changes (fixing formatting, tidying up comments, etc), get the commit rights and then often never been heard or seen from again. I didn’t know if that was just hearsay - it wasn’t the case when I was at Google but that was some time post blink - but the pattern of behaviour made it seem super plausible.
- h0l0cube 4y ago> Safari seems to prioritise building a solid, fast browser for -websites- Are you really that naive about Apple’s motivations here? From the article: > They argued that if developers don't like its generous offer to take only 30% of their revenue, there's always Cupertino's highly capable browser to fall back on. > The only problem, of course, is that lawyers and regulators ask follow-up questions like "is it?" and "what do developers think?" > Which they did.
- russellbeattie 4y agoThis is quite the rant from Alex. Given the context of his years of butting heads with Apple, I can understand his frustration. But it's still definitely a rant. Apple is doing what Apple has always done: Being obtuse, secretive, stubborn and difficult in order to further their own agenda and prevent competition from encroaching on any area Apple views as theirs alone. Given their history, this is also understandable.
- olliej 4y agoAlex has always demonstrated an unprofessionally intense dislike of Apple, and his attitude towards engineers at apple was one of the reasons I really did not enjoy working with chrome folk back in the day. That he is ranting about apple is pretty much par for the course from him. He demonstrated an unwillingness to accept that any opinion other than his own had merit in pretty much every part of the web ecosystem I ever had to interact with him in, and took the opinion that any problem anyone had with a proposal he wanted was made up or fundamentally invalid.
- threeseed 4y ago> Being obtuse, secretive, stubborn and difficult in order to further their own agenda and prevent competition from encroaching on any area Apple views as theirs alone No. They just put their users ahead of developers. And the huge success of the App Store model proves they were correct.
- jraph 4y ago> They just put their users ahead of developers Users can go fuck themselves the day Apple decides to stop supporting hardware they bought but still prevent other vendors to provide alternative, up-to-date browsers on it. I know, I inherited an iPad 2 that was lying around in a drawer. This machine is way less useful than what it could be because of its ancient Safari version. This is the second time I read this sentence in this thread, it sounds like a cult.
- agsnu 4y ago
- masswerk 4y agoNow I really want to see Chrome catching up on some basics, as well, like monospaced text. (Why Chrome, are Greek letters of different width?)
- paulirish 4y agoNot sure of the specifics, but if certain glyphs are not in a font, it falls through to the next font in the stack. Got a repro?
- masswerk 4y agoHere is a use case: While MathML is a web standard since 1997, there is no support for it. Still, we want to write "x = y × ε + c". And we want this to line up with another formula on the next line. Or you want to write down a simple matrix, where one of the elements is a Greek letter, but still would like numbers to line up vertically (it's a matrix!). This works with any kind of pre-formatted text (like a "pre" element with the generic monospace font-family) in every browser, as it has, since there have been browsers, but not with Chrome. For Chrome, we have to put epsilon in a span element, make it display as inline-block, assign a width (0.6em), align the character inside this box, just to write a very basic formula! (I call this "training wheels for text".) Repro: x = y × ε + c y = x × 1 + c ⎛ 1 −1 ⎞ ⎜ ⎟ ⎝ ε 1 ⎠ Writing the character "ε" for Chrome: <span style="display: inline-block; width: 0.6em; text-align: center; overflow: visible; margin: 0; padding: 0; box-sizing: border-box;">ε</span>
- brundolf 4y agoFor some kinds of apps, these might be the tipping point that allows PWA-first to finally be a real option. And if they aren't, and the momentum continues, maybe the next round could be Exciting times. I hope the pressure on Apple is kept up
- asddubs 4y ago>A number of improvements look extremely promising, but remain exclusive to macOS and iPadOS: > Fullscreen API fixes > AVIF and AV1 support I thought iPhones also support AVIF now?
- adiabatty 4y agoIn Photos, yes. I just AirDropped one onto my phone and it showed up in Photos just fine. Safari support is another matter, and runs on its own schedule. I think Safari, in some configurations, supported WebP before macOS did.
- asddubs 4y agoso can you confirm it does not work in safari? I don't actually have an ios 16 device, but it's been green on caniuse.com for a while, so I just assumed it worked.
- irrational 4y ago> If you're a web developer not living under a rock, you undoubtedly got word of last week's big Safari 16.4 reveal. TIL that I’m a web developer living under a rock.
- adiabatty 4y agoI saw the list. It was a long list. Definitely longer than most lists of things that are new in the latest WebKit beta. Long lists of improvements are better than shorter lists, but with a list this long my eyes started to glaze over since most of them weren't for things I'd been waiting for myself.
- fwlr 4y agoIt’s probably healthy to have some vitriol directed at Safari. I tried to imagine a similar piece written about Chrome to make sure I wasn’t disliking this piece just because I use Apple products, and I realized I don’t need to imagine - they exist, I’ve read them. Sure, the complaints are a little different, it’s about leading the standards body by the nose and trying to turn the browser into an operating system because then Google would have an operating system with deeply pervasive ad tracking built in and already accepted by most users. This is just what it looks like to hold the other perspective on the matter.
- baq 4y agoProbably? The thing barely works IME
- shuckles 4y agoI like the part of the post where the author cites a page with 8-9 job ads as a “hiring spree” and a bunch of posts by a single author, Jen Simmons, as evidence of a huge reallocation of talent.
- adiabatty 4y agoI've been wondering about this. 8-9 people would probably beef up the WebKit team a fair bit, judging by how fast features come out in WebKit betas. For a while, I've figured that Apple tends to feel like it's got a self-imposed software-engineer shortage, judging from the long lists of bugs that they have. I've heard some people say that it's mostly a talent-allocation issue by management that seems to have other priorities or misplaced priorities or something. However, since Radar/Feedback Assistant acts like /dev/null most of the time, I figure they just need more engineers to actually work through the list of not-absolutely-critical bugs and spend more engineer-hours getting their software right.
- shuckles 4y agoApple runs famously lean. Given they out-execute most of their competitors with a fraction of the headcount, maybe they’re onto something.
- irrational 4y ago> But what if developers see behind the veil? What if they begin to reflect and internalise Apple's abandonment of web apps after iOS 1.0 as an (eventual) exercise of monopolistic power that held the web back for more than a decade? Uh… I think I and every other developer has been saying this for many years. The number of developers who hadn’t “seen behind the veil” must be vanishingly small. Follow the Money was so obviously the reason. Don’t update Safari, reap that sweet sweet app money.
- dmitriid 4y ago> I think I and every other developer has been saying this for many years. Nope. Most developers haven't been saying this. Also, it's bullshit. I keep saying this: Android is 70% of world's market share. It has none of the "holding back the web" fully enjoying the Chrome monopoly with all its Chrome-only non-standards. And yet there are literally zero "amazing paradigm shifting world shattering on par with native" PWAs that we hear that Apple is holding back.
- irrational 4y ago> And yet there are literally zero "amazing paradigm shifting world shattering on par with native" PWAs Of course there aren’t. Nobody wants to build the same thing twice. Since PWAs are a no go on Safari, which, despite iOS being a minority compared to Android is still used by many of the wealthier coveted audiences, we would have to build it as a PWA for Android and native for iOS. We’ve consistently chosen not to do that. But, with these recent Safari changes, it might be enough for us to finally consider building PWAs.
- dmitriid 4y ago> Of course there aren’t. Indeed > we would have to build it as a PWA for Android and native for iOS. We’ve consistently chosen not to do that. Translation: PWAs and their purported advantages are a myth > But, with these recent Safari changes, it might be enough for us to finally consider building PWAs. And they will invariably suck. Edit: It looks like the only "argument" for PWAs is "but on iOS the people have more money". (They also use much more powerful devices than most Androids out there). So the "argument" for PWAs is "we can't even pretend to care about 70% of the addressable market, and even with the purported advantages we can't even begin to think of building these amazing PWAs that would open the doors to people on non-expensive devices etc. because those people have no money and those people dont have powerful phones"
- iou90 4y agoThe most attention fix: https://bugs.chromium.org/p/chromium/issues/detail?id=1231712 https://bugs.chromium.org/p/chromium/issues/detail?id=123171... A issue on iOS webview from iOS 11 (2017...)
- singularity2001 4y agoAt least on the WASM front Safari isn't lacking tooo far behind (and just added SIMD)
- cjk 4y agoThis guy's about page says: It is my professional mission to build a web that works for everyone. Judging by this article, it's also his “professional mission” to present opinion as fact with no connection to reality. I was on the Safari/WebKit team from 2012-2015, and I can say with absolute certainty that the author has no clue what he's talking about with respect to how bug tracking, feature/bug prioritization, or headcount works at Apple. I could elaborate on all of that for an hour or more, but what I will say is this: The _number one_ problem with the speed of Safari/WebKit releases has always been that they have traditionally been tied to the release of major OS versions. A few of us on the team referred to this as the “fundamental tension,” i.e. the tug-of-war between yearly OS releases and the much-faster pace of innovation of the web platform. Everyone on the team was aware of this. Many of us lobbied to change this. The holdup was _absolutely not_ due to any kind of willingness to keep Safari behind in order to push people toward native apps, it was due to the seemingly-immovable internal culture of everything being tied to a yearly OS release. The culture finally started to change with the advent of the Safari Technology Preview builds, which were explicitly meant to offer insight into the progress of new WebKit features. It seems like my former colleagues have done a great job in pushing for greater transparency and more frequent release cycles since then, and I applaud them for doing so.
- h0l0cube 4y agoI'm swayed by your internal accounting that internal politics and bureaucracy could have been the main cause behind the lagging feature set of Safari, but do you think that it could also be a downstream consequence of browser functionality being in tension with App Store dominance? i.e. why prioritize something that could eat into your bottom line?
- cjk 4y agoTo this day, I don't have any reason to believe that anyone in my management chain (at closest, I was two managers down from Craig Federighi) ever considered profit when prioritizing features or bugs.
- 4y ago