“Safari's buggy” is valid criticism, “Safari's behind Chrome in features” is not

Re:“Safari's buggy” is valid criticism, “Safari's behind Chr... by maxxxxxx on Friday July 30, 2021 @07:40PM (#28013764)

I can’t believe we’re still in this postion. 20 years ago, a fresh new browser entered the market that blew the competition away: Internet Explorer 6. It’s hard to overemphasize what a crapfest the browser scene had been up to that point. Netscape was a buggy mess (remember Netscape Gold?)

5 years later, everyone hated IE 6. It was the new browser to hate. It was a buggy non-compliant mess, much as Safari is now. And again a new browser shook up the scene: Phoenix (which would later become Firefox).

Later, Chrome entered the market. It’s the superior browser now.

Browsers come and go.

[ Parent | on HN ]

Re:“Safari's buggy” is valid criticism, “Safari's behind Chr... by dmitriid on Saturday July 31, 2021 @03:21AM (#28016110)

> Browsers come and go.

Here's what one of the main authors of KHTML has to say about this: https://twitter.com/LarsKnoll/status/1421121639845187585

20 years ago you needed a fraction of what is in a modern browser today. And it's getting worse. Chrome ships 40 to 70 new Web APIs every 40 days or so: https://web-confluence.appspot.com/#!/confluence

[ Parent | on HN ]

Re:“Safari's buggy” is valid criticism, “Safari's behind Chr... by mrweasel on Saturday July 31, 2021 @05:27AM (#28016660)

It’s somewhat terrifying that a single person or a small team can develop an operating system, with a GUI, but won’t be able to create a modern web browser to run on the same OS.

[ Parent | on HN ]

Re:“Safari's buggy” is valid criticism, “Safari's behind Chr... by dmitriid on Saturday July 31, 2021 @07:38AM (#28017205)

The Web seems to be in an unenviable position of needing both:

- an insurmountable amount of work for backwards compatibility, and

- an insurmountable amount of work to keep up with the torrent of new features added to it

[ Parent | on HN ]