171–180 of 623 posts
Safari is perfectly fine. Chrome being a dominant web browser engine is the new issue at hand. Firefox and safari are seemingly second class at best now. It doesn’t help that google themselves only seem to test with chrome. Meets on Linux is broken in Firefox with the latest update as per usual with google.
Earlier quoted context omitted.
I suspect that developers are simply angry with Apple for not letting them to fiddle with the latest stuff that Google is experimenting with. Chrome is the new IE but with better manners if you consider the non standard Chrome specific stuff that makes websites to work only in Chrome. Developers hated IE for not being standart, you had to write two versions of your CSS, you had to make your code accommodate the Box m…
> I suspect that developers are simply angry with Apple for not letting them to fiddle with the latest stuff that Google is experimenting with. That is absolute bullshit. Browser push notifications have been out for years on other browsers (INCLUDING desktop Safari), and they are the one thing that Apple is dragging their feet on the most because they know it's the most important thing that prevents a dev from just d…
> Because IE was seriously outdated, lacking support for cutting-edge web APIs and technologies enabling the modern websites and web apps we use today. This is just false, or at best only half of the story to make a false equivalence. IE was cutting edge until Firefox. The biggest problem with IE was all the insanely weird shit it did, not missing features. It would “fix” missing tags, that would then be broken on ev…
The analogy is simple: back in the day devs got sick of IE because it was the one thing holding them back. You can make a site, easily, that looked beautiful on all the other major browsers, but because IE was outdated when it came to standards support, you had to basically spent all your time fighting with it. Safari serves that role today. There are tons of things I'd love to do but can't because they're not suppor…
Nowadays the Microsoft browser, Opera and others are just Chrome skins. Google is pushing various drafts and essentially dictating web standards and then even when a browser like Firefox does support those Google flavoured standards, it still gets blocked outright on new Google products or gets a limited feature set on existing ones. Or it gets hobbled by Google oopsies.
Why would anyone want to play in such a rigged game...
> Because IE was seriously outdated, lacking support for cutting-edge web APIs and technologies enabling the modern websites and web apps we use today. This is just false, or at best only half of the story to make a false equivalence. IE was cutting edge until Firefox. The biggest problem with IE was all the insanely weird shit it did, not missing features. It would “fix” missing tags, that would then be broken on ev…
The analogy is simple: back in the day devs got sick of IE because it was the one thing holding them back. You can make a site, easily, that looked beautiful on all the other major browsers, but because IE was outdated when it came to standards support, you had to basically spent all your time fighting with it. Safari serves that role today. There are tons of things I'd love to do but can't because they're not suppor…
[0] https://developer.mozilla.org/en-US/docs/Web/API/Element/scr...
Earlier quoted context omitted.
The analogy is simple: back in the day devs got sick of IE because it was the one thing holding them back. You can make a site, easily, that looked beautiful on all the other major browsers, but because IE was outdated when it came to standards support, you had to basically spent all your time fighting with it. Safari serves that role today. There are tons of things I'd love to do but can't because they're not suppor…
Back then there were many browsers and many actors involved in developing web standards. It was justified to criticise laggards. Nowadays the Microsoft browser, Opera and others are just Chrome skins. Google is pushing various drafts and essentially dictating web standards and then even when a browser like Firefox does support those Google flavoured standards, it still gets blocked outright on new Google products or…
> Because IE was seriously outdated, lacking support for cutting-edge web APIs and technologies enabling the modern websites and web apps we use today. This is just false, or at best only half of the story to make a false equivalence. IE was cutting edge until Firefox. The biggest problem with IE was all the insanely weird shit it did, not missing features. It would “fix” missing tags, that would then be broken on ev…
Like many others have started- it’s common these days for devs to create modern apps that work on modern browsers but break in weird ways on Safari. That’s enough of a similarity for the analogy to convey the idea.
Web-P / WebGL support aside- Safari often fails to render complex SVG animations for obscure reasons. It can’t even render a hex-based CSS radial-gradient that looks the same as it does on Chromium or Gecko.
It’s really bad, and Apple benefits from that. They are holding the web back as IE once did in the past.
> But at the same time, the lack of support for key web technologies and APIs has been both perplexing and annoying at the same time.
Funny that the author thinks that the two things are not connected. Lack of support for key web APIs (meaning WebRTC basically) is perhaps what's keeping Safari users' privacy.
Keeping up with the crazy pace of Web API evolution in a safe way and without introducing vulnerabilities is probably impossible even for the browsers pushing for all the craziness that's turning browsers into Operating Systems.
Apple has its own opinions about what web standards it should implement. It’s as simple as that. Google has been extremely successful in convincing developers that browsers that don’t behave like Chrome are behaving wrong. Don’t get me wrong, I wish Safari had more features, fewer bugs, and an evergreen release cycle. It’s clear Apple do not see themselves as competing with Chrome, largely because of iOS, and I do wa…
You’re talking as if the W3C or even Mozilla don’t exist. This isn’t an Apple vs Google thing. This is an Apple vs web standards thing. That’s why Safari is outdated for developers.
> Because IE was seriously outdated, lacking support for cutting-edge web APIs and technologies enabling the modern websites and web apps we use today. This is just false, or at best only half of the story to make a false equivalence. IE was cutting edge until Firefox. The biggest problem with IE was all the insanely weird shit it did, not missing features. It would “fix” missing tags, that would then be broken on ev…
== != === If every analogy was held up to this level of scrutiny, we wouldn’t have analogies. Something can be similar in nature without being an exact equivalence. Like many others have started- it’s common these days for devs to create modern apps that work on modern browsers but break in weird ways on Safari. That’s enough of a similarity for the analogy to convey the idea. Web-P / WebGL support aside- Safari ofte…
Though maybe I just proved your point about missing the forest for the trees :-P