471–480 of 623 posts
I say this every time a post like this comes up... Google is the web. Chrome is the web. It shouldn't be true, but it is.... almost. Safari, or more specifically Apple's requirement that all web rendering on iOS be done using WebKit, is THE ONLY thing standing in the way of Chrome's market share being functionally 100%. If you care about the web, and one would presume that web developers would care deeply about the w…
I say this every time a post like this comes up... Google is the web. Chrome is the web. It shouldn't be true, but it is.... almost. Safari, or more specifically Apple's requirement that all web rendering on iOS be done using WebKit, is THE ONLY thing standing in the way of Chrome's market share being functionally 100%. If you care about the web, and one would presume that web developers would care deeply about the w…
It doesn't follow that you should support Safari blindly, without criticism, simply because they offer some competition.
It's reasonable to want competition to Chrome, but to believe that Safari is doing so very poorly.
Previous HN: https://news.ycombinator.com/item?id=27019077
For the overwhelming majority of users, life on iOS is peachy.
Earlier quoted context omitted.
No. Google's are aligned with the web being useful to Google . This is not the same as "the web being useful". And these days more often than not Mozilla (which has no stakes in either apps or online advertisement) sides with Apple: https://webapicontroversy.com
I don't buy Mozilla's/Apple's concerns for those APIs. Sure if seems sketch to access USB from the web, but as a user if I'm trying to achieve something and I can't do it on the web, I'll end up installing a native app which has way more access to my system. As a developer I would much rather be able to just deploy cool things on the web instead of having to package up native apps for every platform just to do things…
Mozilla considers the periodic sync API "harmful" because you could use it to track users IP and consumer resources when it's not clear they're interacting with the site
Their stated position:
> We're concerned that this feature would allow users to be tracked across networks (leaking private information about location and IP address and how they change over time), and that it would allow script execution and resource consumption when it isn't clear to the user that they're interacting with the site. We might reconsider this position given evidence that these concerns can be safely addressed, however, addressing them for periodic background sync appears substantially harder than doing so for one-off background sync.
But you could achieve very similar behaviour by using Web Push (which they _have_ implemented) and just sending periodic push message. So now as an honest web developer if I want nice background sync behaviour I have to implement some Rube Goldberg system of periodic push messages from a backend rather than just asking the system to wake me up every now and then.
Earlier quoted context omitted.
You’re holding on too tight to an argument for the sake of analogy. It’s cute and evocative but it’s blinding you to the bigger picture. The issues with Google monopolising the direction of standards development are the major issue facing browsers, users and developers on the web, today. I get that you’re disappointed Safari doesn’t support the same stuff, the same way as Chrome. Tough. You’re attempting to develop a…
That's absurd. I'm not targetting Lynx, Haiku, or 8 year old shitty phones. Nor are most web developers. And the attitude that you must support those things is detrimental to the web. It makes people feel like they're doing it wrong of they don't spend all their time chasing those rare edge cases. Which if you're trying to start something new, can kill your productivity. I'd rather have web developers target the comm…
I'm on an older MacOS version with Safari 12 (too lazy to update, but that's on me), and there are sites that work just fine one day and then break the next because they changed how they want to load random content for their forever scrolling.
I'm sure there's a business case for the development team, but as a user, all I see is that what worked just fine for users before is now broken. The same happens with Firefox too because of Chrome-focused optimizations that a lot of sites seem to make don't always work with Firefox.
For me as a user, I don't see it as Safari/FF holding developers back, I see that because of some unknown benefit, I'm being corralled into using Chrome. I make my peace and just don't visit sites that decide on such changes, but the benefit for me as a user for these changes is completely non-apparent. It's very tempting to write it off as "it's convenient for the devs" due to lack of any relevant information on why such changes are made.
Earlier quoted context omitted.
Discord in particular, is an example of Electron done right. It's super performant and low impact on resources. MS Teams, made by a vastly richer company, is an example of the opposite. It's not Electron that's eating your RAM.
Visual Studio Code was also done right but it seems to get worse with patches.
Earlier quoted context omitted.
What does that mean?
It means Brendan Eich is opposed to same sex marriage: Brendan doesn't believe that same sex couples should have equal rights as opposite sex couples. There's something about equality that deeply disturbs and confuses Brendan, so much that he donated a large amount of money to the cause of tearing apart families by destroying legally married loving couple's existing same sex marriages in California, while Brendan and…
Your idea of equality are skewed by popular mainstream media. We should not strive for equality because life is not equal, but we should strive for fairness. If you want equality between me and an NBA basketball player you'll have to break their legs or something because I can't play basketball if my life depended on it, so there, that's an example of life's natural inequality, which is fair.
Fairness means equality of opportunity, not the equality of outcome. Arguing for the equality of outcome is tyrannical and pure evil.
I say this every time a post like this comes up... Google is the web. Chrome is the web. It shouldn't be true, but it is.... almost. Safari, or more specifically Apple's requirement that all web rendering on iOS be done using WebKit, is THE ONLY thing standing in the way of Chrome's market share being functionally 100%. If you care about the web, and one would presume that web developers would care deeply about the w…
* for e-commerce all customers matter
The problem isn't Safari as much, which pioneered HTML5, and is the most power-efficient browser on any platform I've seen. The problem is web devs. Web developers have increasingly the attitude of "I don't want to learn how to make apps, I want to use HTML/CSS/JS for all apps I make", and this plays directly into Google's interests, which benefits from everything being web, because it has its tentacles all over the…