Earlier quoted context omitted.
Edge is a completely different product based on a new rendering engine which is as spec compliant as Firefox.
i don't believe that for a second - edge being as spec compliant as firefox, that is.
Goodbye, EdgeHTML
41–50 of 679 posts
Re: Goodbye, EdgeHTML
#42Re: Goodbye, EdgeHTML
#43Seriously, switch to Firefox. It's good again, and prioritizes privacy.[0] After Chrome's forced-sign-in debacle [1] I switched away from Chrome on all my platforms (Windows, Linux, Android) and haven't missed a thing. [0]: https://hacks.mozilla.org/2018/11/firefox-sync-privacy/ [1]: https://news.ycombinator.com/item?id=18055161
What about Chromium?
Re: Goodbye, EdgeHTML
#44It makes me wonder if at any point in the process Microsoft approached Firefox over integrating their rendering engine vs. Chromium and if so, what the factors were in making their final decision. I also wonder if instead of "ceding" control to Google, Microsoft intends to start being a major contributor to Chromium, so much so that it almost becomes a joint effort vs. Google dominance.
I'm wondering the same, and naively, it seems likely. But on the other hand, Google forked Blink away from Webkit specifically so it wouldn't have to share control of the codebase with Apple. Do you think Google is willing to share control over Blink with Microsoft?
Re: Goodbye, EdgeHTML
#45I still see zero benefit to me, today , to use Firefox.
Re: Goodbye, EdgeHTML
#46I still see zero benefit to me, today , to use Firefox.
https://www.privateinternetaccess.com/blog/2018/11/supercook...
From a security and data privacy standpoint Firefox seems like the only option.
Re: Goodbye, EdgeHTML
#47Seriously, switch to Firefox. It's good again, and prioritizes privacy.[0] After Chrome's forced-sign-in debacle [1] I switched away from Chrome on all my platforms (Windows, Linux, Android) and haven't missed a thing. [0]: https://hacks.mozilla.org/2018/11/firefox-sync-privacy/ [1]: https://news.ycombinator.com/item?id=18055161
I did experience a glitch the other day in dev tools where a pane blanked out on me. I may have had a crash too, but that's it.
Re: Goodbye, EdgeHTML
#48I still see zero benefit to me, today , to use Firefox.
Although, I'm considering moving more to Chrome because of how Apple is breaking old extensions in Safari 12.
Who asked for more native apps? Because I sure didn't. Make no mistake, it's about security, but they still chose the wrong path. If they just made people sign their .safariextz bundles, we wouldn't have to go through this dance.
Re: Goodbye, EdgeHTML
#49Re: Goodbye, EdgeHTML
#50It makes me wonder if at any point in the process Microsoft approached Firefox over integrating their rendering engine vs. Chromium and if so, what the factors were in making their final decision. I also wonder if instead of "ceding" control to Google, Microsoft intends to start being a major contributor to Chromium, so much so that it almost becomes a joint effort vs. Google dominance.
As I understand things, the Mozilla codebase is a much older, vastly more complex and significantly less embedding-friendly environment than WebKit and derivatives. At least from here, it is easy to see why the choice may have in part been technically driven. (I'm a diehard Firefox user but not gonna lie, side-by-side, I'd prefer surfing through WebKit's repos by a long shot!)