3 ms·
1. If you're going to say you don't like spec because of issues, you should explicitly describe what those issues are OR offer up an alternative spec. Simply n
by mtomweb 4y ago
1. If you're going to say you don't like spec because of issues, you should explicitly describe what those issues are OR offer up an alternative spec. Simply not engaging on the spec doesn't present as engineers trying to solve a problem.
2. Neither Apple or Mozilla have described in detail what they think the harms are and why the specs do not cover those harms. But Mozilla is not a gatekeeper and doesn't ban the competition from 50% of mobile devices, so IMO they should be free to decide to do whatever they want even if I disagree with their decision.
Apple on the other hand not only doesn't describe the security issues in ANY detail, or outline why the specs don't cover them, it bans the competition from bringing any solution to the problem while at the same time providing a significantly insecure solution on native which is widely used to track and surveil users and for 9 years didn't even require a permission prompt.
As for resorting to insults about mindless list of things, have you even attempted to build a web app for iOS?
In every single case of the most ardent Safari defenders the answer is no. Unsurprisingly the people that care about the issues in Safari are the ones with the most knowledge that have to work with it daily.
- dmitriid 4y ago> If you're going to say you don't like spec because of issues, you should explicitly describe what those issues are They did > Neither Apple or Mozilla have described in detail what they think the harms are They did > As for resorting to insults about mindless list of things, have you even attempted to build a web app for iOS Doesn't explain why you keep dumping these lists without thinking and parroting Google's talking points