Feds may target Google's Chrome browser for breakup

Re:Feds may target Google's Chrome browser for breakup by cageface on Sunday October 11, 2020 @11:58PM (#24751252)

I don't think IE6 really compares to Chrome. IE6 froze the web in time and made impossible for standards to evolve. Chrome may be in danger of becoming synonymous with the web but it's hardly standing still. In fact the most common complaint is that it's adding features too quickly and trying to do too much.

[ Parent | on HN ]

Re:Feds may target Google's Chrome browser for breakup by wyattpeak on Monday October 12, 2020 @12:43AM (#24751463)

IE6 was the most innovative browser of all until it won the race. I don't think we're at the stage yet where we can say if Chrome can be compared or not.

[ Parent | on HN ]

Re:Feds may target Google's Chrome browser for breakup by nwienert on Monday October 12, 2020 @12:44AM (#24751466)

The features they are adding are often unnecessary and designed to help them further lock down the web, prevent ad blocking, etc.

I’m surprised no ones even noticed that Portals are basically AMP Supercharged to where you’d never leave Google. Truly dystopian future they’re trying to slowly cement.

[ Parent | on HN ]

Re:Feds may target Google's Chrome browser for breakup by saithound on Monday October 12, 2020 @07:06AM (#24753222)

> The features they are adding are often unnecessary and designed to help them further lock down the web

Reminds me of the Browser Wars of yesteryear, when Microsoft and Netscape invented their own unnecessary, easily abused, proprietary HTML tags, such as blink and marquee.

[1] https://thehistoryoftheweb.com/blink-marquis-tag/

[ Parent | on HN ]

Re:Feds may target Google's Chrome browser for breakup by ethbr0 on Monday October 12, 2020 @08:05AM (#24753543)

It's easy to look backwards, with the benefit of more robust and fast (relatively!) standards bodies, and shake a finger.

But my memory at the time is that there were essentially no effective, consensus-based evolutions of web standards, because everything was so new.

Even the idea of running executable code in a browser at all was "That's weird. Is this a thing we want to do?" and resulted in 10+ variations (of which javascript ultimately triumphed).

It was certainly a worse time for the consumer, and web developer, as essentially everything was broken on every platform but your target w/ your target plugin installs.

[ Parent | on HN ]

Re:Feds may target Google's Chrome browser for breakup by cageface on Monday October 12, 2020 @02:34AM (#24751958)

A lot of people noticed and I thought the gave a reasonable counter argument as to why this was not the case.

[ Parent | on HN ]

Re:Feds may target Google's Chrome browser for breakup by koalaman on Monday October 12, 2020 @08:08AM (#24753560)

examples?

[ Parent | on HN ]