Live data from Hacker News

Microsoft Edge and open source collaboration

blogs.windows.com

31–40 of 304 posts

Re: Microsoft Edge and open source collaboration

#31

Earlier quoted context omitted.

> A huge win for web developers everywhere! And a huge loss for users everywhere. Now that Chrome is becoming the main web target, Google (an adtech company) basically controls the internet.

I don’t really get this. Edge was only available to Windows users. This is only a loss to those users. On the other hand Chrome and Firefox are available on all major (for some subset of all) platforms. (Yes, I’m aware iPhone Firefox is hobbled bc of Apple policies). If you want to push competition and choice, encourage everyone to use Firefox (or Safari if they only use macOS).

> Edge was only available to Windows users.

And still, it was some competition to Chrome and Firefox.

> encourage everyone to use Firefox.

Which can be done while also lamenting the loss of a Firefox competitor, especially when said loss gains Firefox nothing.

Re: Microsoft Edge and open source collaboration

#32
I feel like I should be happy as a web dev to hear that I no longer have to support a browser engine made by Microsoft (which has been a huge pain and despite this will be a huge pain for a while due to people still using old browsers) but this feels bittersweet. It feels like we're taking the engineering out of everything because companies can make more money by not innovating.

Re: Microsoft Edge and open source collaboration

#33
post #8

EdgeHTML is also used for embedding HTML into UWP, and controls have been released for WPF and Win32. I wonder what will be the story of that. Will that be transparently changed to Chrome, can it be changed to Chrome or will EdgeHTML be used only for that?

On that note- what is the engine used by outlook, word et al.? I seem to recall outlook used something different from trident back when ie was the main browser.

Yes, and was ironically more standards compatible than WordHTML they use now. AFAIK they changed to WordHTML with or after Outlook 2007 [0]

[0]: https://www.howto-outlook.com/faq/wordhtml.htm

Re: Microsoft Edge and open source collaboration

#34

This is HUGE! Microsoft throwing away the IE engine in favor of one more or less standard rendering engine is a huge win for web developers everywhere! It's also something that would have been unimaginable in the Steve Ballmer era. Thank you!

That's an incredibly short-sighted attitude. No web developer who remembers IE6 would cheer a new browser monopoly.

Re: Microsoft Edge and open source collaboration

#36
post #22

I'm assuming I'm not the only one who's afraid of Blink becoming the new Internet Explorer; instead of people following a web standard, they'll follow what's Chrome-compatible. It's still better because Chromium is open-source, but I do worry that we're going to have a problem in the future with a lot of broken sites (YTMND-style).

> instead of people following a web standard, they'll follow what's Chrome-compatible

The browser vendors taking the lead over standards committees is how we got this far into HTML5, especially including Apple's/Safari's decision to ditch flash, and the WHATWG actually moving us forward vs the W3C.

Unless Blink has a history or an expectation of deprecating serious functionality in the future, is it really so bad if websites follow what's Chrome-compatible instead of 'a web standard'?

Re: Microsoft Edge and open source collaboration

#38
post #8

EdgeHTML is also used for embedding HTML into UWP, and controls have been released for WPF and Win32. I wonder what will be the story of that. Will that be transparently changed to Chrome, can it be changed to Chrome or will EdgeHTML be used only for that?

I suspect the rise of Electron apps, including Microsoft's own applications like Visual Studio Code, are actually driving this decision. Effectively within Microsoft, Chromium has already won over EdgeHTML for desktop applications.

Re: Microsoft Edge and open source collaboration

#39

What I find a bit curious is that's a fully Chromium based browser, it's not simply based on the Blink rendering engine. So, it will be much closer (probably) to Chromium/Chrome than other blink-based browsers like Brave or Opera. I'd really like to understand the rationale behind this choice. What they'd like to leverage from Chromium that Blink alone wouldn't have?

[deleted]
Post reply on HN