Live data from Hacker News

Goodbye, EdgeHTML

blog.mozilla.org

471–480 of 679 posts

Re: Goodbye, EdgeHTML

#471
Firefox is important for internet democracy. I use FF as I prefer that my explicit browsing habits wouldn't also be affiliated with Google that already got enough data on me...

It is improving.. Yet, pure performance, both EdgeHTML and Chromium outperform on many of my devices.

Re: Goodbye, EdgeHTML

#472
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 use the nightly builds and I definitely do not have that problem with around 750 tabs open on my non-retina MacBook Pro. It does suck down memory though.

Re: Goodbye, EdgeHTML

#473
Some thoughts..

Chrome Dev tools are way better

Firefox Ui looks like 2008.

Firefox would win more if it continuesd to support unity.

Problem with Firefox is that it sticks to standards too much whereas others experiment and get cool features which then become part of standards and then finally Firefox gets them.. meaning in last.

Bookmark manager sucks

File menu and other menus are clunky

They need to redo their logo it also looks like 2008

If Firefox made their motto "get all chrome features 6 months before chrome" I'll uninstall chrome right now

Re: Goodbye, EdgeHTML

#474

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 use the nightly builds and I definitely do not have that problem with around 750 tabs open on my non-retina MacBook Pro. It does suck down memory though.

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.

Re: Goodbye, EdgeHTML

#475
post #333

Earlier quoted context omitted.

Those two features combined end up sending keystrokes to third parties in a way that is not transparent to users, and they haven’t consented to it, either. I prefer Firefox’s defaults on both counts.

Fair enough, but there is no way to change to that even if I consent to send my keystrokes for auto completion. Also, Firefox has auto completion on by default on its default search engine, which is Google no less. So I'm not sure why this topic is about privacy other than purely technical.

Firefox doesn't have auto completion on Google. Rather, there's one of two other things going on:

- Google has auto completion on Google through a bit of JavaScript.

- Firefox has auto completion on all text input fields that don't specifically disable it and aren't password fields.

As a portal to the internet, I'm quite happy that Firefox doesn't modify specific individual websites, even if they are Google (the anti tracking features are/should not be hardcoded values, but rather behavioral).

Re: Goodbye, EdgeHTML

#476
post #283

Earlier quoted context omitted.

Chrome massacres my 2012 MBA, the fan spins up within 30 seconds of launch. Firefox runs smooth as butter, mucho tabs and no fan. It seems people have widely different experiences, very weird. I wonder if it's a graphics card thing.

From some researching I’ve done on the internet, it seems like it’s a Retina issue. When I switch the resolution to default, the spinning goes away.

Maybe, but on my non-retina 2012 MBP I have the exact opposite experience of that described by hnzix..

Re: Goodbye, EdgeHTML

#477
post #430

Earlier quoted context omitted.

I'm afraid our hopes of Servo resurrecting Mozilla were short lived. From what I understand, work on Servo for Desktop has been phased out considerably. See https://blog.servo.org/2018/03/09/servo-and-mixed-reality/

Ah crap. I totally missed that this happens. It's a damn shame really, what exists of Servo at this point was rather amazing in terms of speed.

I will admit I was secretly hoping that Servo would become a new, minimalistic, privacy-focused browser that would also blow Chrome out the water with performance.

Its a shame they just plugged some parts into Firefox and called it a day. Instead of getting us a new shiny browser that could compete with Chrome, Mozilla focuses efforts on dubious Pocket/Cliqz/VPN integrations and a bunch of progressive outreach programs.

Unless something changes drastically, Firefox will descend into irrelevancy very soon (if not already). And that's bad for all of us.

Re: Goodbye, EdgeHTML

#478

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…

It would be nice if there were a Node flavor that used SpiderMonkey as a choice to V8. Until that happens most of us are forced to use Chrome related technology no matter how much more we may prefer Mozilla tech.

The problem with that is to make a node.js compatible engine you need to write and maintain a compatibility layer that mirrors the V8 API which I can completely understand a Dev team not wanting to undergo.

Re: Goodbye, EdgeHTML

#479
post #463

Earlier quoted context omitted.

I don't understand why the slack app exists. Why would I want to run another browser for a chat application?

I've noticed most people in my organisation hate the idea of having work chat in a browser tab. They really liked having a separate app.

It doesn't help that the Windows default (not sure about Macintosh) is to group icons in the task bar, so your separate Browser window for chat makes you two-click to switch between browsing and chat.

Re: Goodbye, EdgeHTML

#480

Some thoughts.. Chrome Dev tools are way better Firefox Ui looks like 2008. Firefox would win more if it continuesd to support unity. Problem with Firefox is that it sticks to standards too much whereas others experiment and get cool features which then become part of standards and then finally Firefox gets them.. meaning in last. Bookmark manager sucks File menu and other menus are clunky They need to redo their log…

Firefox Dev tools are better for some things. Things like debugging webgl (you can live edit shaders!) But I find the UI and icon design difficult to use.
Post reply on HN