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

Firefox 69.0 Released

mozilla.org

Post reply on HN
Print view View original

321–330 of 331 posts

Re: Firefox 69.0 Released

#321

Post by jdashg »

GeekyBear wrote: post #160
kilroy123 wrote: post #110

Earlier quoted context omitted.

This was the single thing I was hoping to see here. Upgrading now.

Firefox 70 will be the first version where enough of the changes that they have been working towards will land to yield really substantial power savings, with more changes yet to land beyond that. The next version will drop OpenGL and use Core Animation instead. I know a lot of people have become impatient, but they have been doing a huge amount of work behind the scenes.

Technically it'll still be using OpenGL, it'll just have system compositor integration via CoreAnimation for scrolling, and possibly some elements in the page like video.

Re: Firefox 69.0 Released

#322

Post by RenRav »

slater wrote: post #206
Aardwolf wrote: post #82

> For our users in the US or using the en-US browser, we are shipping a new “New Tab” page experience that connects you to the best of Pocket’s content. With all due respect, if you have to call it an "experience" you know it's something nobody asked for :p

I just wish they'd once and for all drop Pocket. At what point do they understand that it's a failed experiment if they constantly have to re-enable and/or "ship" an "experience"?

Pocket should be an official addon that you can uninstall. It seems unfair to all the other addons.

Re: Firefox 69.0 Released

#323

Post by rhizome »

acdha wrote: post #275
rhizome wrote: post #268

Earlier quoted context omitted.

Of course they're going to come up with new and exciting forms of interruption, but "shift spending" is extremely malleable, and agencies will still provide the feature for a price. Also, it's my understanding that there are no "returns" per se on brand advertising (vs. product advertising), regardless of medium.

No “returns” in directly measurable sales but all but the most unconcerned companies are going to look at interactions and ask whether they’re getting enough versus the cost, especially since the Facebook measurement scandal got a lot of attention.

The word "enough" is doing a lot of work there.

Re: Firefox 69.0 Released

#324

Post by bzbarsky »

gregknicholson wrote: post #320
bzbarsky wrote: post #152

Earlier quoted context omitted.

Not just that, but in an earlier release code was shipped to set the pref for users who already had the file, so that anyone who already had one of these files would not observe any behavior regressions. And yes, file I/O was the issue.

Thank you for doing this!

I can't claim credit for it; I hadn't even realized it had happened until I dug a little bit into the history while reading this thread. All I knew was that my userChrome.css was still working fine... ;)

Re: Firefox 69.0 Released

#325

Post by hutattedonmyarm »

seppel wrote: post #283
hutattedonmyarm wrote: post #66

Earlier quoted context omitted.

My MBP doesn’t have a dedicated card and yet firefox manages to eat my battery as a snack

For me (MBP from early 2015 w/o dedicated card) the upcoming FF 70 made a huge difference. I installed the beta today and I finally can go to youtube, facebook and reddit (the new design!) without the fan spinning up.

Sounds like I'll give FF another try on the Mac. I do love it on Windows

Re: Firefox 69.0 Released

#326

Post by HLFH »

jchook wrote: post #77
veidr wrote: post #8

Earlier quoted context omitted.

I'm even OK with this feature, just not with the we're shipping a new “New Tab” page experience that connects you to the best of... drone-speak T_T

Also they promised to open source Pocket in 2017, but seem to have zero intention of doing it. Instead, they prioritize controversial integration into the browser itself.

I had enough to wait for Pocket to be released in open source.

Re: Firefox 69.0 Released

#327

Post by xxs »

bzbarsky wrote: post #309
xxs wrote: post #305

Earlier quoted context omitted.

>The technical answer to the question you asked is "10-20ms, if you're not on an SSD C'mon the directory structure would be cached already, even if it was not - the seek times for HDD are 3-4ms.

The directory structure may or may not be cached already: these files are in a separate directory from everything else Firefox needs at startup. If your HDD has a seek time of 3-4ms on average, that means it needs to rotate completely in at most 6-8ms, which gives you a rotation speed of 7500-10,000 rpm. HDDs in data centers do that, sure. Consumer HDDs just don't do that, last I checked; they're mostly in the 5400-7…

I will comment on the paragraph and the way directories are stored in b-trees, being a separate directiry doesn't have a lot if bearing unless talking about FAT.

Re: Firefox 69.0 Released

#329

Post by c0vfefe »

fnord123 wrote: post #133
Carpetsmoker wrote: post #130

Earlier quoted context omitted.

> 5KB news article On what site do you find "5KB news articles"? Pretty much all news sites that I know of load a gigantic amount of useless and obnoxious JavaScript, CSS, images, etc. with or without video.

NPR + rejecting cookies under their GDPR scheme makes the page a dream.

Also note https://text.npr.org/

Re: Firefox 69.0 Released

#330

Post by kup0 »

canada_dry wrote: post #314
kup0 wrote: post #313

Hope this release somehow magically fixes an ongoing issue in Windows 10 I've had with Firefox. The gist of it is that Firefox, and only Firefox, will cause my Windows 10 system to completely hard freeze (no mouse movement, no response period) for about 30-60 seconds at a time, multiple times daily. It's so frustrating that it makes FF unusable for me. It's odd because it seems to be a rare issue that has to do with…

> only Firefox will cause my Windows 10 system to completely hard freeze Whenever I experience this type of thing I can't help but speculate that issues like this are not serendipity at work. I recollect reading an article years back from a Microsoft developer who spoke about how it was quite common for Windows code to take specific actions based on which app was running - ostensibly to 'improve the user experience'.…

Seems somewhat unlikely in this instance, because apparently the issue I'm running into is pretty rare. There are millions of people using FF on W10 daily without any issues. Heck, even I have other W10 machines where it doesn't happen.
Post reply on HN