Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Goodbye, EdgeHTML

blog.mozilla.org

Post reply on HN
Print view View original

621–630 of 679 posts

Re: Goodbye, EdgeHTML

#621

Post by pookeh »

daveFNbuck wrote: post #457
Someone1234 wrote: post #76

Earlier quoted context omitted.

The best thing about Firefox is Mozilla's Multi-Account Container tabs[0]. Essentially it allows you to put different tabs into different light-weight profiles, with their own session, cookies, and state. That means if you want to log into Facebook but don't want Facebook following you online, just give Facebook its own container. Mozilla has anti-tracking already baked in, but Multi-Account Containers are a whole ot…

They're quite practical even if you don't care about tracking. I have different containers for my work and personal Google accounts and they make things much easier than relying on Google's support for multiple accounts. They're also great for development. I have different containers for each user I use while working on logged-in flows. I can just go from tab to tab to test different user experiences or switch betwee…

I use this extension called SessionBox on Chrome to do exactly this. It gives me different sessions side by side in the same window.

Re: Goodbye, EdgeHTML

#622

Post by pookeh »

Someone1234 wrote: post #277
asavadatti wrote: post #138

Earlier quoted context omitted.

Chrome has this too. I doubt its effectiveness as there are ways to fingerprint your browser without using cookies/sessions

Chrome doesn't have this. You cannot run tabs in different contexts in Chrome side by side. Both additional profiles and incognito browsing open a different window, with its own settings.

I use SessionBox ext in chrome to achieve this.

Re: Goodbye, EdgeHTML

#623

Post by PunchTornado »

derefr wrote: post #364
PunchTornado wrote: post #103

Earlier quoted context omitted.

as a frontender I'm not sad. A lot of bugs coming in from Edge. And Edge has a pretty shit debugger too. So no tears for me. Waiting for Safari to die. Firefox and Chrome are good.

Why would Safari [i.e. Webkit] die? Looking at desktop + mobile market shares, if anyone would be "the next to die", it'd be Firefox.

I said I wish it would die. Really slow in keeping up with the standards.

Re: Goodbye, EdgeHTML

#624

Post by mkl »

efreak wrote: post #455
blattimwind wrote: post #366

Earlier quoted context omitted.

Firefox has also supported multiple profiles since forever.

Firefox hasn't supported running multiple profiles simultaneously forever, though I understand that it's possible now. That's actually party oh what got me on chrome originally--I could have my school profile open at the same time as my goofing-off profile and pretend to be researching while I played flash games, yet not showing any of that in my history.

Firefox has supported running multiple profiles simultaneously since before Chrome ever existed - I used them. Chrome was first released in 2008, and here's an article about Firefox's multiple instances from 2007: http://turbulentsky.com/how-to-run-multiple-firefox-profiles....

Re: Goodbye, EdgeHTML

#625

Post by Manishearth »

kossTKR wrote: post #468
davidp wrote: 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…

Does setting gfx.compositor.glcontext.opaque to true in about:config fix the problem?

Re: Goodbye, EdgeHTML

#626

Post by nashashmi »

gchucky wrote: post #273
nashashmi wrote: post #31

So much wasted energy: https://github.com/Microsoft/ChakraCore RIP!

Apparently ChakraCore will continue development for "various non-Edge uses".[1] Curious what that actually means.. [1] https://twitter.com/bterlson/status/1070754781822574592

Funny, reminds me of the Trident engine (IE on Windows) and the Tarzan Engine (IE on Mac). Long after IE on Mac was abandoned, Tarzan continued to be developed for some reason. And then it actually had a use again when MS office on Mac was created.

Re: Goodbye, EdgeHTML

#627

Post by Yoric »

gear54rus wrote: post #507
dingaling wrote: post #307

Earlier quoted context omitted.

Sadly there are also 'secret prefs' that are considered so potent that they're not exposed by default in about:config If you know about them, for example from reading the code, you can create them. So at present about:config is a strange sort of place with lots of knobs but not all of them.

is there a good list of those prefs? or perhaps I can scan source code for some string

Frankly, these secret prefs are basically either:

- prefs that a developer was too lazy to add to the list of pref; or - prefs that serve only during automated tests.

You could scan source code for `Services.prefs` and `nsIPreferenceService` if you really want to find them.

Re: Goodbye, EdgeHTML

#628

Post by Yoric »

kossTKR wrote: post #468
davidp wrote: 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 know about ~100 Firefox developers with Macbooks and none of them experiences the issue, so that's probably harder to reproduce.

Would you be interested in help to profile the issue and file a detailed bug? This would help fix it.

Re: Goodbye, EdgeHTML

#629

Post by jakoblorz »

What if the narrative behind Microsoft's decision is not to build a better browser but to hurt Google from a regulatory view? I mean they maneuvered Google into an obvious and significant monopoly position, similar to the one Microsoft found itself before the uprise of Google.
Post reply on HN