Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft is building a Chromium browser to replace Edge on Windows 10

windowscentral.com

Post reply on HN
Print view View original

111–120 of 774 posts

Re: Microsoft is building a Chromium browser to replace Edge on Windows 10

#111

Post by lvh »

mushu999 wrote: post #103
jccalhoun wrote: post #23

As a firefox fax, I hope this isn't true. The dominance of chrome isn't good for anyone. This will lead to (even more) sites not bothering to be made compatible with Firefox. We are headed back to the "designed for IE" days.

WTF do you mean "lead to sites not bothering to be made compatible with Firefox"?? If Firefox follows the published HTML standards then there wouldn't need to be any special compatibility effort made by us web devs! That is exactly what made I.E. (and Edge) so cr@ppy in the first place!! /facepalm

That’s only true if Chromium does everything correctly, and even then it ignores the chilling effect where nobody cares unless Chrome does it.

Right now I have perfectly valid SVG and HTML5 that straight up does not work correctly in Chrome.

Re: Microsoft is building a Chromium browser to replace Edge on Windows 10

#112

Post by sureaboutthis »

c-smile wrote: post #19

That's just the disaster. And the end of W3C standard development process. AFAIR it should be 3 independent implementations of the feature in order for Draft to reach Recommendation status. So technically all that means that web standards will be written by WebKit team alone. Sic transit Gloria mundi, sigh.

It is two, not three.

Re: Microsoft is building a Chromium browser to replace Edge on Windows 10

#113

Post by taf2 »

nl wrote: post #95
samspenc wrote: post #90

Earlier quoted context omitted.

My understanding is that they'll be using the Chromium engine underneath, but still their own Edge "browser" and UI on top. IMHO, I personally think it's a good thing to consolidate on one engine to render HTML cross-platform for these two reasons: 1. Web developers no longer need to worry about supporting CSS and other edge-cases across various browser engines. 2. The Chromium engine itself is open source. There are…

Web developers no longer need to worry about supporting CSS and other edge-cases across various browser engines. So, as the OP said - back to the bad old days of IE6 dominance.

Not even close. IE6 was a browser that was set in stone. It only ran on Windows. It's legacy that we live with today is the ActiveX controls that are basically parts of Windows. MS stopped innovating on the browser part of IE6 and focused on ActiveX e.g. native Windows components that you could use in the browser. You can't talk about IE6 and not mention how embedded it was with Windows. That is what made IE6 bad. You could not use your Mac or Linux environments to browser the internet. Lots of great ideas came out of IE6 XMLHTTPRequest. Access to the native desktop devices. Storage APIs, realtime communication anything you can do on the desktop you should be able to do through the Web. That is what we see happening today with Chromium and Mozilla. These two teams and now with MS being more involved as well. There is a huge amount of collaboration it's nothing at all like IE6 days.

Re: Microsoft is building a Chromium browser to replace Edge on Windows 10

#114

Post by sureaboutthis »

chrisseaton wrote: post #74
c-smile wrote: post #19

That's just the disaster. And the end of W3C standard development process. AFAIR it should be 3 independent implementations of the feature in order for Draft to reach Recommendation status. So technically all that means that web standards will be written by WebKit team alone. Sic transit Gloria mundi, sigh.

Who cares what the W3C think is a draft or a recommendation?

The entire internet and web development community, that's who. While WHATWG has taken over the HTML part, it's the W3C that still gets all the action everywhere else.

Re: Microsoft is building a Chromium browser to replace Edge on Windows 10

#115

Post by kibwen »

Osiris wrote: post #86
h1d wrote: post #13

Earlier quoted context omitted.

No, there's now more reason for gecko to survive. Can't have single engine dominate the web.

But if that engine is open source, isn't that a good thing? There's a single standard but anyone can contribute patches for increased performance, new features, etc?

All commits to the Chrome codebase are gated through Google, an ad company whose driving motivation is in delivering value to shareholders, not to improving the web. Once the web becomes a Google monoculture, I won't be holding my breath to see any features land on the web that could threaten Google's bottom line.

Re: Microsoft is building a Chromium browser to replace Edge on Windows 10

#116

Post by sureaboutthis »

vbezhenar wrote: post #69
c-smile wrote: post #19

That's just the disaster. And the end of W3C standard development process. AFAIR it should be 3 independent implementations of the feature in order for Draft to reach Recommendation status. So technically all that means that web standards will be written by WebKit team alone. Sic transit Gloria mundi, sigh.

Is IE dead?

IE has been dead for years. Some still have to put pity on IE11 or even IE10 but we're all hoping for a rapid death.

Re: Microsoft is building a Chromium browser to replace Edge on Windows 10

#117

Post by joesb »

kibwen wrote: post #93
samspenc wrote: post #90

Earlier quoted context omitted.

My understanding is that they'll be using the Chromium engine underneath, but still their own Edge "browser" and UI on top. IMHO, I personally think it's a good thing to consolidate on one engine to render HTML cross-platform for these two reasons: 1. Web developers no longer need to worry about supporting CSS and other edge-cases across various browser engines. 2. The Chromium engine itself is open source. There are…

> The Chromium engine itself is open source Being open source is a red herring in this instance. Say that Chrome implements a web feature you don't like. You fork the browser and remove that feature. But websites expect Chrome, and they use that feature, so your fork doesn't work with those websites. Say that Chrome refuses to add a feature you want. You fork the browser and add the feature. But websites expect Chrom…

Your examples have nothing to do with whether you use Chrominum engine, though.

Say that Chrome implements a web feature you don't like. MS use their own MSengine for their Edge browser that doesn't have that feature. But websites expect Chrome, and they use that feature, so MS Edge doesn't work with those websites.

Say that Chrome refuses to add a feature you want. MS use their own MSengine for their Edge browser that has that feature. But websites expect Chrome, so they don't use MS Edge feature so as to not break for their Chrome users, and MS Edge browser is no better off.

Re: Microsoft is building a Chromium browser to replace Edge on Windows 10

#119

Post by fourthark »

nikkwong wrote: post #94
fourthark wrote: post #49

Earlier quoted context omitted.

How was it broken? I only tested visualization stuff on it but it seemed to work pretty well. Honestly asking...

It just depends on how far you're trying to push these browsers. Chrome has a lot of crazy cutting edge APIs which allow amazing developer and therefore user experiences. For example, IntersectionObserver, which allows developers to know when a part of a page is active, and respond accordingly; Safari doesn't even implement IntersectionObserver, even though it's been a standardized spec since like 2013. It might seem…

Oh sure, I know. Often wondering if I should even try with Safari. I was trying to ask how Edge was broken.

Re: Microsoft is building a Chromium browser to replace Edge on Windows 10

#120

Post by h1d »

Osiris wrote: post #86
h1d wrote: post #13

Earlier quoted context omitted.

No, there's now more reason for gecko to survive. Can't have single engine dominate the web.

But if that engine is open source, isn't that a good thing? There's a single standard but anyone can contribute patches for increased performance, new features, etc?

You don't want 1 hidden hard to fix bug to wreck the entire internet. It's obvious wide use of a tool need multiple implementations.
Post reply on HN