3 ms·

Sigh. This is really the perfect storm, because the “this has happened because Apple is evil” blog posts really write themselves after this change dropped. But

Sigh. This is really the perfect storm, because the “this has happened because Apple is evil” blog posts really write themselves after this change dropped. But really, let’s not forget that this is beta software. Apple routinely ships betas with features half-complete. The people that regularly use Apple betas know that. Drive-by drama bloggers don’t. If the final version ships with this change, I’ll be right there next to presumably everyone else railing against the ridiculousness of the change. For now though, I’m not, and I see absolutely zero point in anyone else doing so.

zamadatix 3y ago
I think it's reasonable to expect something like a communication be made on the intent to fix before shipping and that no commentary is an implicit denial of that. After all, if you only stand in the outrage line after it breaks in GA then you're essentially agreeing it's fine for it to be broken for a while and not everyone will see it that way. Bloggers could be less sensational about it for sure though.
- zamadatix 3y ago
  And it seems that warning applied directly in this case: https://news.ycombinator.com/item?id=39388218 https://news.ycombinator.com/item?id=39388218 Had Apple not been pressured into a communication update on the matter the conversation would be starting at 0 a month from now.
veeti 3y ago
Maybe if Apple gave a damn about PWA developers or users they could just communicate with them? Maybe journalists wouldn't have to make such a big stink (i.e. doing their jobs) about breaking functionality if Apple simply acknowledged it was a "known issue" in the beta release notes [1]? You are simply giving far too much credit to a company known for its vague communications and underhanded tactics. Also note that the exceedingly detailed documentation for building "alternative browser engines" [2] has literally zero mention of progressive web apps. All the signs are in the air: it's busted and going to stay that way. [1] https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-17_4-release-notes https://developer.apple.com/documentation/ios-ipados-release... [2] https://developer.apple.com/support/alternative-browser-engines/ https://developer.apple.com/support/alternative-browser-engi...
spywaregorilla 3y ago
> If the final version ships with this change, I’ll be right there next to presumably everyone else railing against the ridiculousness of the change. For now though, I’m not, and I see absolutely zero point in anyone else doing so. Sounds like the comfy position of someone with nothing to lose from such a thing shipping in a finished build.
gschizas 3y ago
It seems it's not "this happened because it's beta": https://twitter.com/mysk_co/status/1758196103470628983 https://twitter.com/mysk_co/status/1758196103470628983

zamadatix 3y ago

I think it's reasonable to expect something like a communication be made on the intent to fix before shipping and that no commentary is an implicit denial of that. After all, if you only stand in the outrage line after it breaks in GA then you're essentially agreeing it's fine for it to be broken for a while and not everyone will see it that way. Bloggers could be less sensational about it for sure though.

zamadatix 3y ago
And it seems that warning applied directly in this case: https://news.ycombinator.com/item?id=39388218 https://news.ycombinator.com/item?id=39388218 Had Apple not been pressured into a communication update on the matter the conversation would be starting at 0 a month from now.

veeti 3y ago

Maybe if Apple gave a damn about PWA developers or users they could just communicate with them? Maybe journalists wouldn't have to make such a big stink (i.e. doing their jobs) about breaking functionality if Apple simply acknowledged it was a "known issue" in the beta release notes [1]? You are simply giving far too much credit to a company known for its vague communications and underhanded tactics. Also note that the exceedingly detailed documentation for building "alternative browser engines" [2] has literally zero mention of progressive web apps. All the signs are in the air: it's busted and going to stay that way. [1] https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-17_4-release-notes https://developer.apple.com/documentation/ios-ipados-release... [2] https://developer.apple.com/support/alternative-browser-engines/ https://developer.apple.com/support/alternative-browser-engi...

spywaregorilla 3y ago

> If the final version ships with this change, I’ll be right there next to presumably everyone else railing against the ridiculousness of the change. For now though, I’m not, and I see absolutely zero point in anyone else doing so. Sounds like the comfy position of someone with nothing to lose from such a thing shipping in a finished build.

gschizas 3y ago

It seems it's not "this happened because it's beta": https://twitter.com/mysk_co/status/1758196103470628983 https://twitter.com/mysk_co/status/1758196103470628983