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

651–660 of 679 posts

Re: Goodbye, EdgeHTML

#651

Post by jhall1468 »

pcwalton wrote: post #356
jhall1468 wrote: post #44

Earlier quoted context omitted.

Google forked Blink because how Apple and Google saw the future of browsers drastically differed. I'm going to venture a guess that Microsoft selected Chromium because their vision is closer to Google's than either Firefox or Webkit.

> Google forked Blink because how Apple and Google saw the future of browsers drastically differed. That's not accurate. Google forked Blink for many reasons (WebKit2, dev tools policies, etc.) that collectively added up to a dysfunctional relationship.

How is that any different than what I suggested? They both wanted to go in very different directions.

Re: Goodbye, EdgeHTML

#652

Post by inferiorhuman »

torben-friis wrote: post #570
inferiorhuman wrote: post #533

Earlier quoted context omitted.

> I don't know why you're trying to deffend the idea that this bug is not a (relevant) thing. I'm not OP btw. Why? Hand waving and tantrums don't mean that what OP is experiencing is representative of the state of Firefox on OSX. OP is positing that it's this ancient bug that Mozilla developers have just ignored because they're so awful/incompetent/lazy/whatever, but there's no way it would be problematic on hardware…

This is again anecdotal, but last time I reformatted my mac I tried to install firefox first to see if the bug was still there with no other software or config installed. Literally the only thing I had done before installing was setting up the basic settings (wallpaper, resolution, keyboard language, etc). The bug was still there. It's a 2013 macbook pro with no config attached, so there's nothing quirky in the hardw…

> before installing was setting up the basic settings (wallpaper, resolution, keyboard language, etc)

Plenty of things there could be edge cases. In fact the very first thing I thought of was resolution. Running a non-scaled retina display could definitely cause all sorts of problems as all of a sudden the browser is rendering a much bigger canvas.

> I'm not making a judgement on Mozilla devs and their competency or work ethics, and I don't think OP is either

OP is absolutely judging Mozilla employees and if that carried through to the bug reports I'm sure OP filed, well, that could definitely color the response from Mozilla.

Re: Goodbye, EdgeHTML

#653

Post by lucideer »

AlexCoventry wrote: post #444
rb666 wrote: post #431

Earlier quoted context omitted.

Sorry but this is a bit clueless, what are you trying to secure exactly, if it's not your own data? You can't honestly thing that data is safer in Chrome than Firefox.

I doubt google engineers rank high in his threat model. :-)

Firstly, why just Google engineers? Many Google employees and any 3rd parties Google share data with would be included.

Secondly, that's a single step in the threat model; it's not just about what a Google engineer would do with your data, it's about attack surface area when any Googlers (or Google infra, or Google partner infra) that is compromised automatically exposes you.

The simple act of transmitting and storing your data to anyone, no matter how secure their systems are, is still by definition less secure than simply not transmitting that data.

Re: Goodbye, EdgeHTML

#654

Post by derefr »

baroffoos wrote: post #418
derefr wrote: post #364

Earlier quoted context omitted.

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.

Safari is a huge pain in the ass to test on because you have to own apple hardware to do it. Firefox and chrome can be installed on anything and microsoft gave you a VM to test IE and Edge in.

I didn't say "why should it die", I said "why would it die." Unless you mean that you find it likely that some appreciable fraction of developers will stop owning Apple hardware at some point.

Re: Goodbye, EdgeHTML

#655

Post by jasin »

retSava wrote: post #577
jasin wrote: post #525

Earlier quoted context omitted.

Me too, and as it happens, I'm running on retina with "more space" enabled. Firefox is unusably slow, to the point where I'm probably abandoning it after a few weeks of really trying to get into it. Which is a shame, because I love the idea of multi-account containers and other privacy features.

So if you disable the "more space" configuration, does it work better? If this is the primo hypothesis, it sounds easy enough to check.

It certainly does seem to work better with default resolution.

Re: Goodbye, EdgeHTML

#656

Post by christophilus »

Yoric wrote: post #628
kossTKR wrote: post #468

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 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.

I’m seeing the same behavior on my Mac. Linux is fine. I’d be happy to help / run profiling / whatever. Contact should be in my profile.

Re: Goodbye, EdgeHTML

#657

Post by ziftface »

pmarreck wrote: post #347
ziftface wrote: post #77

Earlier quoted context omitted.

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.

Hey I'm glad you gave it a try! I think it was turned on for Windows 10 nightly users with Nvidia cards. Not sure if they added more users since then.

What do you think if you don't mind me asking?

Re: Goodbye, EdgeHTML

#658

Post by pmarreck »

ziftface wrote: post #657
pmarreck wrote: post #347

Earlier quoted context omitted.

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.

Hey I'm glad you gave it a try! I think it was turned on for Windows 10 nightly users with Nvidia cards. Not sure if they added more users since then. What do you think if you don't mind me asking?

Don’t really see that many differences from Chrome yet

Re: Goodbye, EdgeHTML

#659

Post by sneakernets »

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

Firefox 57 is why I switched to Chrome in the first place. If I'm going to use a butchered UI, I might as well use the original from whom everyone copied. And on top of that accessibility was a nightmare.

My grandmother had glaucoma and could not use Firefox 57 in any capacity because the feature to have large chunky Netscape/Mosaic buttons was removed completely. I had to switch all her stuff over to SeaMonkey, which still had the ability to have large buttons, so she could use a web browser.

Re: Goodbye, EdgeHTML

#660

Post by ilrwbwrkhv »

sobani wrote: post #620
ilrwbwrkhv wrote: post #492

Earlier quoted context omitted.

I would switch in a heartbeat if the audio issue for sped up videos is solved...

Which audio issues do you experience? I regularly watch videos sped up on YouTube and InfoQ and never noticed any problems.

This one: https://bugzilla.mozilla.org/show_bug.cgi?id=1383363
Post reply on HN