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

71–80 of 774 posts

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

#71

Post by taf2 »

fourthark wrote: post #37

Very sad. I'm not a Microsoft fan but I thought this was one of the things they were doing right. The performance was really good, compatibility with standards was actually the best IMHO. Every thing (SVG) I tried that got past Firefox and Chrome worked on Edge without modification. And yeah, we need the competition. It's not like Microsoft is running out of money. Guess they need their most talented people doing som…

It's a good thing more talented people can focus on development of an open source browser. That means more people can share in a consistent and reliable way. It also means much like Mozilla has been innovating with Servo we're seeing amazing things from that and it doesn't have to be X vs Y. MS vs Google. It can be a collective working towards a better common platform for everyone.

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

#72

Post by leeoniya »

nerdbaggy wrote: post #22
mcny wrote: post #9

Earlier quoted context omitted.

On the front page, I saw another headline that said Firefox desktop market share is below nine percent.

And nobody knows how that’s calculated. If the implementation is done via JS we can assume a good portion of all the browsers usage % is incorrect.

here are some actual metrics from our ecommerce site (US, home remodeling / DIY):

if you look at desktop traffic only:

  Nov 2015: 16.01%
  Nov 2016: 13.27%
  Nov 2017: 10.33%
  Nov 2018:  8.14%
Desktop IE in Nov 2018 was 11.37%, Edge 15.65%, Chrome 52.74% and Safari 11.65%.

if you include mobile traffic (where Firefox is basically non-existent), then Nov 2018 is closer to 3.5%.

talk about bleak :(

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

#73

Post by ivankolev »

chipperyman573 wrote: post #53
talawahdotnet wrote: post #28

Interesting, but what I really, really want them to do is EOL IE 11 so that the web can move forward without feeling guilty about the X% of users still on it. IE 11 has unfortunately become the new IE 6. As it is right now I believe the IE 11 EOL is tied to the Windows 10 EOL...which is not happening anytime soon. Many frameworks are dropping support for it anyway so I guess it will end up being defacto desupported.

As someone who has (luckily) only had to support Firefox/Edge/Chrome, can you go into why IE11 is so bad? In the very small amount of testing I've done, everything seems to render just fine (especially compared to IE6/7/8)

For one it does not support css grid, which is really the best way to do layout atm.

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

#74

Post by chrisseaton »

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?

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

#75

Post by c-smile »

saagarjha wrote: post #51
c-smile wrote: post #44

Earlier quoted context omitted.

Blink and WebKit cannot be considered as separate implementations - their codebase is in sync AFAIK.

Blink was forked a long time ago–do they still share patches?

Patches is not the only mechanism to keep code in sync.

For two engines forked from the same source (same architecture and even same code tree structure) it is relatively easy to copy/paste feature implementation, no?

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

#77

Post by fabrice_d »

nerdbaggy wrote: post #22
mcny wrote: post #9

Earlier quoted context omitted.

On the front page, I saw another headline that said Firefox desktop market share is below nine percent.

And nobody knows how that’s calculated. If the implementation is done via JS we can assume a good portion of all the browsers usage % is incorrect.

The absolute number is not that important, the trend is. That's clear even in Mozilla's own data: https://data.firefox.com/dashboard/user-activity shows they went from 303M monthly active users at the end of Nov. 2017 to 277M this year. This is a serious drop.

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

#78

Post by walterbell »

RcouF1uZ4gsC wrote: post #25

If Microsoft really does this and makes the Chromium based browser the default in Windows, what is the value proposition of installing Chrome? Presumably all the websites will work exactly as they do in Chrome and it will be no faster or slower?

Also: Data collection by Microsoft instead of Google. Since Microsoft is already collecting data from the Windows OS, they are already part of your trust chain.

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

#79

Post by TheCoelacanth »

vtesucks wrote: post #6

On the one hand developers have one less engine to worry about. On the other if it becomes a chromium monoculture then Firefox loses.

Except that we will probably have to support Edge for another 5 years for the people who refuse to upgrade, so in reality, it will be one extra unsupported browser that we have to write hacky workarounds for.

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

#80

Post by thrower123 »

ravenstine wrote: post #59
thrower123 wrote: post #32

Broken shit should die. And Edge was definitely broke. Safari is next, with 5% market. Chrome is the clear winner in the end.

Safari is broken on purpose in a lot of ways when it comes to security, for better or for worse. I've had to do a lot of workarounds for Safari to compensate for the restrictions on cross-origin frames even though the host allows for the origin in its CSP, just as an example. Then of course there's the lack of support for WebRTC and virtually no support for PWAs. As Apple doesn't really view itself as a software comp…

Safari is broken in ways that don't make sense if you don't live in apple land, so I can't bother with their mess for 5 or 6% of the total browser market

Moreover, it's irrelevant to non apple people

Post reply on HN