4 ms·
The issue is you are focusing on the specific APIs as a strawman argument which would require us to argue each and every API on its individual merits something
by mtomweb 4y ago
The issue is you are focusing on the specific APIs as a strawman argument which would require us to argue each and every API on its individual merits something neither of us has time for.
Instead let’s focus on the core issues:
1. Severe underfunding of Safari
2. Bugs
3. Install Prompts/Banners
4. Push API
1. Apple has no incentive to fund their browser while they are not at any risk of losing market share to the competition on their primary OS.
2. Because of the underfunding and the fact users/developers can’t shift to other browsers, bugs that are either impossible to work around (or require a very high level of skills) have not been fixed. Some which were reported 7 years ago.
3. Users do not know web apps exist. They have no way to install them.
4. Notifications arrived for native apps in 2009, in 2022 they still are not available for web apps even though they are essential for many different types of apps. Apple has promised them in 2023 likely as a result of our advocacy work.
Without a viable web ecosystem on iOS mobile web apps are dead and the entire ecosystem gets shifted to native apps and webkit applies no competitive pressure on chrome/edge or Firefox. The status quo is the worse case scenario.
The fix for this scenario is competition. With a 60% market share on MacOS (the on my comparable market where Safari is the default), as long as apple meets developer needs then I can’t see them losing a majority market share on iOS.
A highly funded Webkit be able to contribute to the web ecosystem instead of holding it back.
- dmitriid 4y ago> The issue is you are focusing on the specific APIs as a strawman argument I focused on some APIs I know about. There's nothing strawman about facts that you misrepresented in your diatribe. How can I be sure that you represented everything else correctly? Oh. I can't. Because I also saw your section on "Edge differentiation". Should I go through everyting else and discover same misrepresentation and falseness? I think I won't, these two are quite enough, thank you. > Instead let’s focus on the core issues You keep skipping from goal post to goal post, and each next argument you make isn't made in good faith. > 1. 2. I'm not even going to dignify this speculation with an answer > 3. 4. And again and again all comes down to literally one or two standards. That's it. That's all you really have. Well, sometimes you have more, but then it's just a random dump of random standards that you are absolutely sure are actual standards (and not "Draft comunity reports" by Google) and that everyone must implement them now. > Without a viable web ecosystem on iOS mobile Please define a "viable web ecosystem". So far it looks like to you "a viable ecosystem" is "anything that Google implements, others be damned". > web apps are dead Yes, they are dead. For many reasons that have nothing to do with notifications. > The fix for this scenario is competition. With a 60% market share on MacOS Yes. Let's talk about competition. There is none, it's fully dominated by Google: https://news.ycombinator.com/item?id=31905404 https://news.ycombinator.com/item?id=31905404 Oh wait. You don't really care about that. > A highly funded Webkit be able to contribute to the web ecosystem instead of holding it back. Webkit is contributing to the web ecosystem, and isn't holding it back. For the obvious reason that your definition of a viable web is taken straight out of Google propaganda, and has nothing to do with making the web viable.
- mtomweb 4y agoPointless discussing if you can’t agree on any of the basic factual points.
- dmitriid 4y ago> if you can’t agree on any of the basic factual points. Factual points I started with: - Both Firefox and Safari are against most hardware APIs for many reasons including technical ones. - The section "Edge differentiates from Chrome because it removed a few Google-specific things like Google Pay" is laughable Your "response" is, "oh, you don't believe in web apps" and "Our group was initially formed by a group of people who develop for iOS Safari on daily basis". These are not factual points. These are attempts to dodge a conversation. And when the conversation seemingly starts happening, it's "the facts you provided are not facts, they are strawmen". Yes. It truly is pointless discussing this. There are many, many, many issues we can discuss about Safari. With people who have done their research and don't willingly assume the role of Google's propaganda amplifier. Thankfully, as the comments to the original link show, more and more people are starting have a more sober outlook on what's happening.
- ImPostingOnHN 4y agoas an observer, most of your responses to valid, good faith points (e.g. "I'm not even going to dignify that with a response") seem to indicate that you are arguing to argue, rather than to come to clarity with the other person. Also, they are pretty rude (for reasons beyond the above one), and seem to me to be against the spirit of HN commenting. tl;dr if you think your dignity is above responding to someone, don't.
- dmitriid 4y agoSibling comment: https://news.ycombinator.com/item?id=31907602 https://news.ycombinator.com/item?id=31907602
- ImPostingOnHN 4y ago