Live data from Hacker News

Goodbye, EdgeHTML

blog.mozilla.org

541–550 of 679 posts

Re: Goodbye, EdgeHTML

#541
I don't mind being downvoted for this, but Google Chrome is an amazing browser. It's great as a web developer and also as a user. We've come a long way from the browser wars in the 1990s. Things have stabilized and become much better since then, and you don't have to worry about Chrome turning into the next IE6. Sure, some sites only work in Chrome, but the main problem with IE6 is that it sucked and caused a lot of frustration for web developers. I just haven't had that experience with Chrome.

Chromium is open source. It's not like Google and Microsoft are conspiring in secret to build a browser and destroy the competition. It's an open source project, and there's the W3C and WHATWG. Even if Chrome had 100% market share, there's nothing stopping people from contributing new suggestions, features and improvements to Chromium, or getting involved with the W3C.

I used to be a huge fan of open-source software and the Free Software Foundation, and thought that this anarchist/communist style of project management was the best way forward. Now I've realized that most open source projects are poorly organized, suffer from lack of leadership, and have bad UX and design. The developers are underpaid (or unpaid), unmotivated, and sometimes end up burning out.

Some of the most successful open source projects are backed by large companies who can pay the salaries of full-time engineers (Rails, Chromium, React, Red Hat, etc.) Anyway, I think it's great that Microsoft has decided to adopt Chromium, and that many Microsoft engineers will be contributing new features and improvements to the open source engine.

Check out Brave [1] if you want a Chromium-based browser with a focus on privacy. Or use Firefox. Anyway, I don't think it's the end of the world.

[1] https://brave.com

Re: Goodbye, EdgeHTML

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

Too bad it completely kills your CPU on a Mac. I tried switching completely a month ago for the third time. Sadly absolutely nothing has happened in a 5 year time-span. The performance on my high-spec i7 Macbook Pro is abysmal. ( same across several company Macbooks ) The fans speed up constantly like they have done it for years. It's completely unusable for "professional" work or just regular multi tab browsing and…

I’ve had the same problem for years, a few months ago someone suggested it might be because I don’t use my screen at the default resolution. I have a slightly lower resolution setting on my retina MacBook Pro. And that somehow this causes firefox to go insane and have a nervous breakdown. Is it possible that you are also not using the default display resolution? If everyone who has the problems shares this particular setting, that might point to something.

Re: Goodbye, EdgeHTML

#543
Offtopic, but the on Chrome 67.0.3396.62 the whole first screen of that web page is one third massive header, and two thirds white space with just "moz://a" in it. You have to scroll to see any content.

You'd expect a slightly more usable design.

Re: Goodbye, EdgeHTML

#544
post #498

Earlier quoted context omitted.

Too bad it completely kills your CPU on a Mac. I tried switching completely a month ago for the third time. Sadly absolutely nothing has happened in a 5 year time-span. The performance on my high-spec i7 Macbook Pro is abysmal. ( same across several company Macbooks ) The fans speed up constantly like they have done it for years. It's completely unusable for "professional" work or just regular multi tab browsing and…

I have no idea what you people are doing. I use FF with my mid spec, 4th generation i5 with 500+ tabs and haven't experienced any of your problems.

I’m curious, how is it manageable to have a browser open with 500 tabs? How do you even navigate between the tabs or know what’s on those tabs?

Re: Goodbye, EdgeHTML

#545

Earlier quoted context omitted.

The Edge team is a fraction of the size of the Chrome team.

Are these numbers publicly available?

No. Even from git history, it's hard to actually quantify for Chromium, as most Google contributors use chromium.org emails, which obscures affiliation. The MS numbers are even less public.

Re: Goodbye, EdgeHTML

#546
post #498

Earlier quoted context omitted.

I have no idea what you people are doing. I use FF with my mid spec, 4th generation i5 with 500+ tabs and haven't experienced any of your problems.

I had the exact same experience as the grand parent comment. Seriously wanted to switch to Firefox after the browser-sign-in "feature" but the performance on my high-end 2018 macbook pro with 16gb ram was just abysmal (20 tabs open tops).

Do you use your Mac with the default screen resolution setting, or have you tweaked that setting?

Re: Goodbye, EdgeHTML

#547

Earlier quoted context omitted.

The Edge team is a fraction of the size of the Chrome team.

I think that the number of people in Google contributing to Chromium is much smaller, than the number of people in MS working on Edge. Many Chromium contributors are enthusiasts, who don't get paid for it. They would not mind working on Microsoft's fork instead of Google's fork.

Almost all the commit volume in Chromium is from Google engineers; even the largest external contributors (Opera and Samsung, last I knew) were a tiny percentage of commits. Individual volunteers practically don't exist: they're well under 1% of commits.

Re: Goodbye, EdgeHTML

#548
post #486

Earlier quoted context omitted.

Which doesn't change anything since the Macbook Pro has been sold with Retina displays for what, the last 6 years? The fact that Firefox works exclusively on ancient laptops or edge cases doesn't make anything better. All Apple devices today are sold with Retina screens and the Pro Lineup, and therefore most devs has had Retina screens for 6+ years.

I have a colleague whose Mac has the same issue as you (2015 MBP 15" Retina). Chrome runs awesome for him, Firefox crawls. However, I have the same model and for me Firefox is as snappy as anything. You're right that this needs to be fixed, but its lame to assume that Firefox devs do not test on Macs. You're simply experiencing a bug that is hard to reproduce, that is all.

Firefox is snappy at the beginning, but starts getting really slow and clunky after about 8 hours, or sometimes 2-3 days of the laptop being suspended and then turned on again. I can make it fast again if I close the browser and re-open it. But it's not slow right out of the gate.

Also slow is relative. If someone hasn't had an experience with a faster browser, then "slow" just feels normal. I had that after using Firefox for ~9 months. It just felt normal, and then got a bit slow and unusable after a while. After switching back to Chrome on Mac, it was like a breath of fresh air. I forgot what a responsive UI felt like.

Re: Goodbye, EdgeHTML

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

Too bad it completely kills your CPU on a Mac. I tried switching completely a month ago for the third time. Sadly absolutely nothing has happened in a 5 year time-span. The performance on my high-spec i7 Macbook Pro is abysmal. ( same across several company Macbooks ) The fans speed up constantly like they have done it for years. It's completely unusable for "professional" work or just regular multi tab browsing and…

> Why hasn't "the bug"

As a frequent /r/firefox visitor - while I do agree that Fx team should spend more time investigating this, I still have to note that this is not a bug or something ssimilar that can be easily reproduced.

I have late 2013 MPBr and 2014 iMac and never had any issues of a sort ever since quantum release. The only problem (performance wise) were videos on Youtube, but it seems to be fixed already. So it is there for some people and it is not for the others. With dfferent Macbooks\software\setups etc.

Re: Goodbye, EdgeHTML

#550

Earlier quoted context omitted.

Well, I think it's actually two different things: I don't feel bad at all seeing IE/Edge coming to an end. It was a closed, non free, single-platform browser, who gave a lot of people a lot of headaches during the last 20 years. On the other hand, I'm worried by the fact that Google browser market share continues to grow.

Honest question, what has Edge/IE actually contributed to the web in the past decade? I understand that having one less engine is not preferable, but realistically, it always felt like they were dragging behind struggling to keep up, while Apple, Google and Mozilla kept forging ahead. By using Blink, maybe they can spend more time actually contributing to the spec and having an independent voice elsewhere?

> Honest question, what has Edge/IE actually contributed to the web in the past decade?

Ajax

Post reply on HN