Live data from Hacker News

Goodbye, EdgeHTML

blog.mozilla.org

41–50 of 679 posts

Re: Goodbye, EdgeHTML

#41
post #15

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.

Please, do some research before judging. It was an incredible product.

Re: Goodbye, EdgeHTML

#43
post #39
post #19

Seriously, 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?

[deleted]

Re: Goodbye, EdgeHTML

#44
post #9
post #4

It 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?

Google forked Blink because how Apple and Google saw the future of browsers drastically differed. I'm going to venture a guess that Microsoft selected Chromium because their vision is closer to Google's than either Firefox or Webkit.

Re: Goodbye, EdgeHTML

#46
post #13

I still see zero benefit to me, today , to use Firefox.

For me Firefox is the one browser I feel I can really lock down. Ads are blocked, no java-script or active content is enabled by default on any site, and with some additional tweaking a minimal amount of data is sent to 3rd parties. More than once I've had to disable some feature in Firefox when there was no workaround provided in Chrome. Most recently it was this:

https://www.privateinternetaccess.com/blog/2018/11/supercook...

From a security and data privacy standpoint Firefox seems like the only option.

Re: Goodbye, EdgeHTML

#47
post #19

Seriously, 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

Same here. I have been been back on FF for a few months and have been very happy. It's fast and works great in every respect.

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

#48
post #13

I still see zero benefit to me, today , to use Firefox.

It's basically a 'dev' browser for me. Grid inspector plus a few development extensions and that's it. Everything else is in Safari.

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

#50
post #20
post #4

It 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!)

Which is odd when you realize that WebKit is older than the firefox engine. (WebKit is a direct descendant of khtml, Firefox was busing re-writing their Gecko engine when WebKit forked)
Post reply on HN