Live data from Hacker News

Goodbye, EdgeHTML

blog.mozilla.org

671–679 of 679 posts

Re: Goodbye, EdgeHTML

#671
Having a competitor is a big value for Google, they are smart enought to understand they need Firefox. Think about first WebRTC connection or also WebGL2.

Re: Goodbye, EdgeHTML

#672
post #666

Earlier quoted context omitted.

Off course. I would really like to ditch Chrome once and for all. What i don't get is that it's an unknown problem, many people have already filed bug reports on the tracker: https://news.ycombinator.com/item?id=18626325 (also see several blog posts like: https://www.kamshin.com/2018/07/firefox-on-macos-insane-batt... ) I think it has to do with running the Macbook Pro at scaled resolution which is pretty much standa…

Ah, thanks for the links, very useful. Do I understand correctly that you're checking CPU usage immediately after having scrolled up/down, or while scrolling up/down, right? Apparently, there are already people working on that bug. If I understand things correctly, Firefox uses transparent windows, but transparent windows use lots of CPU on some macOS configurations, and this somehow wasn't detected during testing (I…

Thank you! Testing nightly the next couple of days and will report in the bug tracker if i still have problems.

Re: Goodbye, EdgeHTML

#673
post #115
post #67

Earlier quoted context omitted.

Well lets not act like Firefox is not known. Its been pioneering browser for years and it's in no way inferior to chrome. It's also indepedent and you dont have to send all your data to google when you use it.

It is slower than Chrome. That's enough to me not to consider Firefox, given that speed is everything I care about.

I wish people would try current version of Firefox.

Re: Goodbye, EdgeHTML

#674
post #614

Earlier quoted context omitted.

The reason this is outrageous is because they weren't doing this kind of thing before. The reason this isn't outrageous when Chrome does it is that Chrome always does this. Using this as a reason to distrust Firefox and instead trust Chrome is insane. It's valid criticism but seeing this presented in arguments about why Firefox is bad (and you should be using Chrome instead) is absurd.

Distrust of Firefox does not imply trust of Chrome.

Context matters.

Firefox is significantly more trustworthy than Chrome (the outrage over Mozilla's occasional screw-ups exists because that behaviour is decidedly not the established norm for Mozilla whereas the same behaviour from Google surprises no-one).

The context in this thread was "Switch to Firefox. It prioritizes privacy, unlike Chrome". In other words, "Firefox is more privacy-focused than Chrome".

Piling on Mozilla for past screw-ups creates the impression that this statement is wrong and that both browsers are equally bad at privacy because neither of them is consistently perfect.

Even if the criticism is technically correct, piling it on like this creates a skewed impression that if you care about privacy you might as well use Chrome because even if you switch to Firefox your privacy will be invaded anyway.

This normalises the level of invasiveness of Chrome and equivocates its consistent and intentional behavior with a series of exceptional missteps.

In case you think "But I never mentioned Chrome", well, Chrome and Firefox were the only options in the original post so anything negative about Firefox implies a positive about Chrome and vice versa. If you wanted to call out specific behavior, either present an alternative (Brave? Ice Weasel?) or clarify that you're addressing the behavior categorically and not just that instance of it specifically.

If someone says "Don't use A. B is better because it doesn't do $thing" and then you respond by "I've seen B do $thing" that implies equivalence between A and B even if B did $thing only a few times out of carelessness whereas A intentionally does $thing all the time because its business model depends on it. It doesn't matter that you didn't mean it that way, it doesn't matter that it's true and it doesn't matter that this is a mistake on part of the audience. Humans are flawed and communication requires you to take those flaws into account -- unless you just want to express yourself.

Re: Goodbye, EdgeHTML

#675

Earlier quoted context omitted.

I use Firefox on MacOS. It is easily as fast as Chrome for me (and I have tons of tabs open in multiple windows). And I use Google Docs/Sheets/etc. all day long with zero slowdowns.

On Mac usually Firefox is compared also with Safari, if not only.

The only time I've ever used Safari is to download Firefox ;-)

Re: Goodbye, EdgeHTML

#676
post #635

Earlier quoted context omitted.

That sounds more like incognito mode, no? Containers keep the cookies and other data, yes, so you don't need to re-login every time you start the browser.

I don't know how edge does incognito but in other browsers, incognito kills the tab history, so if you accidentally close a tab you can't trivially restore it with ctrl+shift+t or whatever.

This is the case in Chrome but not in Firefox (private mode)

Re: Goodbye, EdgeHTML

#677
post #635

Earlier quoted context omitted.

This is one of the things I used to like IE for - perhaps the only thing it got better than the competition: File | New Session ... and then you have a fresh session context that doesn't share cookies with the others so you can log into services as different users. As a developer this is very handy for testing multi-user workflows, and had numerous uses as a more general user too, and it was easy to do ad-hoc without…

That sounds more like incognito mode, no? Containers keep the cookies and other data, yes, so you don't need to re-login every time you start the browser.

> That sounds more like incognito mode, no?

Yes, but you can have as many active sessions as you need instead of just two.

Incognito/InPrivate/whet-ever-other-browsers-call-the-feature tabs/windows share the same session so that gives you at most two active sessions: normal and incognito.

The "new session" option in IE can have many more. For a lot of workflows two is enough, but sometimes I want something like "a couple of distinct base users, a manager, and an admin" for testing more complex user workflows.

Re: Goodbye, EdgeHTML

#678
post #575

Earlier quoted context omitted.

> and it's built on Chromium That's a negative to me - again, too much browser engine consolidation. :/

Inclined to agree. I see the fact that Microsoft is abandoning Edge in favour of a Chromium-based browser as a fundamentally bad thing for the web due to the loss of competition amongst browser engines (me of 10 - 15 years ago would probably be appalled by this sentiment, but times change). Brave, as yet another Chromium based-browser doesn't feel like it's helping. That, and the name "Brave" absolutely grates on me.…

The name is not about the company, rather the user who takes control of their own Web economics. This requires facing down some anti-ad/tracker-blocking, and supporting favorite sites and creators (easily done from grants, no need to pay; but still requires courage compared to false security of taking ads and tracking).

I always thought "Opera" was pretentious, personally! But I'm friends with long-time CTO, who does go to Bayreuth every year for Wagner, so I mean this is best possible way ;-).

Re: Goodbye, EdgeHTML

#679
post #575

Earlier quoted context omitted.

Brave browser is solid as well, built in ad blocking and Tor support. CEO is brandon eich and it's built on Chromium

> and it's built on Chromium That's a negative to me - again, too much browser engine consolidation. :/

As only big companies can underwrite development and then support ongoing/backlog compatibility quirks-mode work for a new engine, you are effectively saying "no" to other, higher-order values offered by new browsers than the engine.

Yes, I include Mozilla in "big companies" (2017 big revenue, which won't recur from what I can tell; big pay to chair too). Nevertheless, Mozilla has mismanaged Servo into an AR/XR only position where it won't go big, and Mozilla (for same reasons as MS) faces pressure to bail on Gecko.

Blaming little browsers for using chromium/Blink is blaming them for surviving.

Successful genes (e.g. for adaptive auto-immunity) tend to sweep. Think of WebKit and now (on desktop) chromium/Blink as such alleles. We may not like it but it happens whatever we may wish. I've chosen to fight for user rights at a higher domain of discourse: private ads, anonymous donations, ad and tracking protection by default. The time for a more radical new engine will come; it isn't now.

Post reply on HN