Note from Erik Meijer :)
Microsoft is building a Chromium browser to replace Edge on Windows 10
91–100 of 774 posts
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#92I can see how this is creating a monoculture on the web which could have some really negative implications going forward. However, chromium is open source; so I don't really think this is comparable to the IE days. Also, as a web dev who is trying to push the limits of what is possible given current web APIs, being shackled by edge's lack of compatibility is really a hindrance and makes really cutting-edge stuff impo…
> chromium is open source
On Chromium being open source, and why that doesn't matter: https://news.ycombinator.com/item?id=18595978
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#93As 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.
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 Chrome, so they don't use your feature so as to not break for their Chrome users, and your fork is no better off.
The insidious part of a web monoculture is allowing Google to dictate the standards of the web platform. Being able to fork the codebase only gives one the power to change things that are strictly client-side.
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#94Broken shit should die. And Edge was definitely broke. Safari is next, with 5% market. Chrome is the clear winner in the end.
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 like minutiae, but, safari also doesn't pay any attention to SVG specs. This makes the pages I build for beaver [1] like, impossible. They work beautiful in chrome; but they don't work at all in safari; and because of that, I can't really explore what potential experiences pushing the limits on SVG might have for my clients. Whatever you build has to work in all clients. It's a sad state of affairs, because if safari wasn't so far dilapidated, I would have been able to build some really impressive experiences; but, without safari support it's a no-go.
(1) www.beaver.digital
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#95As 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.
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.
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#96Interesting, 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.
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.
I feel ya. I keep having to stop myself from doing things the right way so that I can support my IE11 users.
Unfortunately, even after EOL, the ghost of IE11 will be around for a very long time. Heck, my November stats show 10% WinXP users.
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#97As 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.
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…
If open web standards are to matter at all, it is more important for there to be multiple viable implementations of the same standards than it is for the lives of web developers to become easier.
Using the same engine across multiple browsers, open source or not, just doesn’t cut it.
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#98Microsoft should buy Vivaldi and make that their default browser.
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#99Interesting, 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.
There is a lot of Enterprise/Corporate stuff tied to IE. For example sharepoint stuff (which my work uses) heavily is tied to IE.
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#100Someone needs to note that Chromium is a browser and the rendering engine is called Blink. You can't build a different browser and rename it based on Chromium but you can use Blink as your rendering engine. The article says "...building a new web browser powered by Chromium, a rendering engine...".