Live data from Hacker News

Goodbye, EdgeHTML

blog.mozilla.org

171–180 of 679 posts

Re: Goodbye, EdgeHTML

#171
post #50

Earlier quoted context omitted.

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)

How much of a rewrite was it? IIRC they fixed a lot of bloat issues and called it a rewrite, but it wasn't a full rewrite.

It wasn't much of a rewrite (at least of the underpinnings) and embedding was always fragile even when it worked. A lot of this is XPCOM overhead which can't be completely eliminated.

I think the lack of embedding has hurt Gecko showing up in more projects. Their solution was XULRunner which inverts the model by embedding your app in Gecko instead of the other way around, and they don't even support that anymore.

I'm hoping GeckoView takes off on Android and makes its way back to desktop, but I'm afraid that will happen too late for people to care about it anymore.

Re: Goodbye, EdgeHTML

#172
It is not good news, but I don't think it is that bad. Microsoft is big enough to assert influence over the direction in ways other contributors cannot. It might even make Microsoft more relevant in the web space, and for the future of the web it could be a good thing (while certainly it was very bad in the Balmer era)

Re: Goodbye, EdgeHTML

#173
Doesn't Mozilla get the lion's share of its funding from Google? I'm a bit puzzled as to how they can avoid a conflict of interest if this remains true.

Re: Goodbye, EdgeHTML

#176
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

I moved away due to the battery drain issues on OSX, has that been addressed? Based on this bug and some of the related ones, the answer seems to be no. https://bugzilla.mozilla.org/show_bug.cgi?id=1404042 Until then I'm stuck with Opera/Safari/Chrome, mostly in that order.

Try viewing Imgur.com on Safari. Just scroll a bit until you get a couple gifs displayed and check the CPU usage on the imgur.com tab. Just insane that a few gifs destroy an i7. Is it bad video compression? I notice imgur attempts to make gifs from mp4 files and vice versa but damn. A 5 year old iPhone has no problem with this task.

It'd be nice if you could throttle processor usage. I'd rather have a choppy experience on the occasionally website than constant fans and having my Mac turn into a heater.

Re: Goodbye, EdgeHTML

#177
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.

Firefox is also undergoing a large rewrite with the quantum stuff with more of an emphasis on rust. Chromium is c++ and already has decent tooling for embedding. Honestly, Firefox is trying to be where the puck is going. Chromium is great but stagnating.

Re: Goodbye, EdgeHTML

#178
post #116

Earlier quoted context omitted.

Firefox added Pocket, and kind of nobody wanted it. So it happens in FF too.

Plenty of people don't want it, but Pocket is actually quite popular. It's an essential part of my browsing experience.

[deleted]

Re: Goodbye, EdgeHTML

#179
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

I moved away due to the battery drain issues on OSX, has that been addressed? Based on this bug and some of the related ones, the answer seems to be no. https://bugzilla.mozilla.org/show_bug.cgi?id=1404042 Until then I'm stuck with Opera/Safari/Chrome, mostly in that order.

It was unusable for me too, afaik it had to do with scaling more than anything else, so if you toy around with scaling factors it might help.

Re: Goodbye, EdgeHTML

#180
post #50
post #20

Earlier quoted context omitted.

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)

I don't buy that argument. Getting a facelift doesn't change the year you were born.

https://www.theguardian.com/world/2018/dec/03/dutch-court-re...

Post reply on HN