Live data from Hacker News

Goodbye, EdgeHTML

blog.mozilla.org

341–350 of 679 posts

Re: Goodbye, EdgeHTML

#341
post #185

Earlier quoted context omitted.

Strange, it runs just as fast as Chrome on my 2013 MBP

It seems to only happen with certain Retina MBPs. Which is a shame - I really wanted to like Firefox on Mac.

Likewise. FF turns my 2012 rMBP into a frying pan for any web page with moving content (video, animated GIFs, ads) or just significant JS (Google docs). I would prefer FF, so I keep checking every couple of years, but no improvement. Unusable.

On those same pages, Chrome and Safari work just fine.

If Apple were making MBPs better each year instead of demonstrating their "courage" ("This time we're taking X away from you because as long as Windows is the only competition, whaddya gonna do about it?") I would have already bought a new one, and that would presumably have more powerful graphics and not get as hot, but I would still want to verify that FF wasn't running the battery down faster than Chrome or Safari.

Re: Goodbye, EdgeHTML

#342
I have been using FF for what seems forever, and I have no plans on stopping... unless they shut it down, finger crossed that that won't happen! I'm a web developer, and it has always been my go to browser, to me it has always felt pretty fast and I actually have never had any problems so I am always baffled how other people always have issues with it, maybe I am just an edge case. AS of now, it has been my default browser for well over 10 years, on both mac and window machines. I will continue to be a loyal user as long as it continues it's current course. I really wish Microsoft had gone with Quantum Gecko.

Re: Goodbye, EdgeHTML

#343
post #235

Earlier quoted context omitted.

To be honest, I actually really like that they added Pocket, and I don't think it takes anything away from FF.

It took away credibility. A lot of it. It also alienated too many “almost evangelist” users (like me) who had converted countless users from other browsers in high school and college. Many of them haven’t been able to reconcile with what might seem a tiny change now. Also the jarring and bizarre way Mozilla pretty much stonewalled everyone on it who wanted it to be discussed. I don’t know it would make sense to you,…

Purely from a feature development perspective, I guess I don't see how adding a read-it-later / bookmarking feature would generate so much consternation. Functionally its roughly equivalent to Reading List + Bookmarks on Safari, with some delicious-like aggregate smarts.

Would it have been better to have built it internally instead of through acquisition? I admit I'm unfamiliar with the inside baseball on it's integration, but breach of trust sounds pretty drastic. My read (as an uninformed outsider) is that they probably acquired Pocket for a song, it filled a gap in the product offering, and it offers the potential of a future optional revenue stream that aligns well with the web as a document reading medium (subscription).

There's all sorts of internal browser features you can't 'completely remove'. How is bookmarking different?

Re: Goodbye, EdgeHTML

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

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

Re: Goodbye, EdgeHTML

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

One gripe I have with FF is that their DevTools are crap... Chrome is a really unprecedented WebDev platform for me.

Re: Goodbye, EdgeHTML

#346

I really wish Mozilla would work on making their Gecko engine (or whatever backend they use now) more usable to external developers. WebKit always seems very easy for developers to integrate into their apps. Whether you think it's a good or bad move, Electron has made building cross platform desktop applications a lot easier. It's a shame it must use Chromium and V8. In fairness Mozilla used to have XUL [1] until it…

> Electron has made building cross platform desktop applications a lot easier

For people who have web development experience, yes.

Re: Goodbye, EdgeHTML

#347

Earlier quoted context omitted.

Many people won't switch because either Firefox is slow on their platform (MacOS) or stuff they use are slow on Firefox (Google ecosystem, many other webapps optimized for Chrome)

I'm on macOS and Firefox is at least as fast as Chrome. Granted, I'm on nightly with WebRender turned on, but that will be in regular Firefox soon enough.

Thanks to this comment I decided to download Firefox Nightly and turn on WebRender. (Was it on by default 2 months ago and then no longer?)

For anyone unaware, WebRender is a new compositing engine for Firefox written from the ground up in Rust that runs on the GPU.

Re: Goodbye, EdgeHTML

#348

Earlier quoted context omitted.

This is handled at the OS layer with user accounts - can’t you switch users at the OS level?

I could but this ain't a corporate scenario.

All major consumer desktop operating systems still have user accounts - you don't need a corporate system to do it.

You'll probably find that you can permanently log both users in at the same time, and then switching between them is just a shortcut and takes a fraction of a second, so it needn't be a burden. You may find it's even faster than changing the user in Firefox.

That's why it's great to do these things at the OS level - it can be done efficiently once for every app and not reimplemented lots of times badly like in Firefox.

Re: Goodbye, EdgeHTML

#349

I really wish Mozilla would work on making their Gecko engine (or whatever backend they use now) more usable to external developers. WebKit always seems very easy for developers to integrate into their apps. Whether you think it's a good or bad move, Electron has made building cross platform desktop applications a lot easier. It's a shame it must use Chromium and V8. In fairness Mozilla used to have XUL [1] until it…

I was going to say that Servo was going to include an implementation of the Chromium Embedding Framework API but apparently that feature has been dropped for lack of use: https://groups.google.com/forum/#!topic/mozilla.dev.servo/5M...

Re: Goodbye, EdgeHTML

#350
post #243
post #231

Earlier quoted context omitted.

Containers are such a great idea. My one wish is if you could set a default container. I use FF to browser Facebook primarily and want that to be default, but instead I have to load Firefox then load a container then load Facebook. Wish it were just open FF -> Facebook is homepage.

There is also a Facebook-specific container addon that limits Facebook's footprint even more than the standard container addon (and will work alongside it) https://addons.mozilla.org/en-US/firefox/addon/facebook-cont... Also with the standard container addon you can specify that sites always open only in your specified container, so you could just set Facebook to always open in its own container that way.

Thanks this is great!
Post reply on HN