News for hackers. Stuff that matters.
Re:Firefox 69.0 Released by dictum on Tuesday September 03, 2019 @10:42AM (#20866927)
I use userChrome.css and userContent.css, and I get the nagging feeling that the silent end of that sentence is "...when we eventually replace the code that currently enables user customization with faster, less flexible APIs."

(I'm paranoid and FUDing because I care: there's some UX low hanging fruit before they could get rid of userChrome.css. For instance, you need userChrome.css to autohide the toolbar in full screen mode on macOS — that's not even a customization, it's a missing feature.)

Re:Firefox 69.0 Released by StavrosK on Tuesday September 03, 2019 @11:10AM (#20867229)
I mean, how slow could an "if file_exists()" check have been? This smells like deprecation to me, if the user CSS doesn't exist, don't load anything. Boom, no slowdown.
Re:Firefox 69.0 Released by bzbarsky on Tuesday September 03, 2019 @12:57PM (#20868566)
The technical answer to the question you asked is "10-20ms, if you're not on an SSD". That's not great, actually, if you're trying to shave tens of milliseconds at a time off startup performance.

For what it's worth, this change happened because people were seeing the stat() call involved in startup profiles, taking sufficient time that it seemed worthwhile to avoid it if possible, as far as I can tell.

Re:Firefox 69.0 Released by xxs on Wednesday September 04, 2019 @03:30AM (#20874817)
>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.

Re:Firefox 69.0 Released by bzbarsky on Wednesday September 04, 2019 @09:11AM (#20876826)
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-7200 rpm range, with laptops firmly in the 5400 bucket. See https://www.dell.com/en-us/shop/dell-laptops/sc/laptops?appl... for example (currently offered Dell laptops "for home" with an HDD: they're all 5400rpm). At 5400 rpm, your average latency from just the rotation is 5.5ms and your worst-case latency from the rotation is 11ms. That doesn't include other latency sources, but let's assume those are somehow scheduled away to happen during the rotation.

Keep in mind that what typically sticks in users' minds is worst-case, not average-case, behavior, so you have to bring your worst-case time budget down to whatever your target is.

Re:Firefox 69.0 Released by xxs on Thursday September 05, 2019 @11:01AM (#20887389)
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 by StavrosK on Tuesday September 03, 2019 @01:30PM (#20868894)
Are many users on HDDs these days? Weird that it would take this long, although I guess it's niche enough that you'd want to save those 20 ms for something used by a tiny fraction of users.
Re:Firefox 69.0 Released by dblohm7 on Tuesday September 03, 2019 @01:57PM (#20869214)
> Are many users on HDDs these days?

Yes, there are. They are not a niche cohort.

EDIT: In fact, we have many more users with magnetic HDDs than who use userChrome.css. That tells you everything you need to know about this decision right there.

Re:Firefox 69.0 Released by jahlove on Tuesday September 03, 2019 @03:56PM (#20870521)
Just under half of desktops use magnetic drives, according to Western Digital. [1]

[1] https://www.minitool.com/news/ssd-market-share.html

Re:Firefox 69.0 Released by kbenson on Tuesday September 03, 2019 @11:37AM (#20867594)
Given that the profile setting is under a subsection of "legacyUserProfileCustomizations", perhaps there's a whole legacy subsystem they spin up to handle it that's only needed for that now? I could see a whole subsystem causing significant enough delay and resource usage to be noticeable, if that's the case.
Re:Firefox 69.0 Released by rrix2 on Tuesday September 03, 2019 @12:15PM (#20868074)
AFAICT it's Firefox's CSS+HTML engine running the user chrome. You can even open the firefox web inspector on it (open web inspector -> settings -> enable browser chrome and add-on debugging toolboxes) which lets you fiddle with the chrome DOM and modify CSS that way.
Re:Firefox 69.0 Released by feanaro on Tuesday September 03, 2019 @11:33AM (#20867537)
Unfortunately, I think you're right. Mozilla has been fighting a slow war on all powerful UI customization. See: the recent killing of Tridactyl.
Re:Firefox 69.0 Released by bovine3dom on Tuesday September 03, 2019 @12:16PM (#20868082)
Reports of our death have been greatly exaggerated :)

You can still install Tridactyl in a normal installation of Firefox by following the instructions on our readme [1]. Admittedly, that may cease to be the case if Mozilla ever tire of us; people in locked-down corporate environments would then find it hard or impossible to install Tridactyl but we'd make it as easy as possible for everyone else.

On topic, I'd argue that Mozilla are just desperately trying to cling on to ordinary users; the "war" against power users is a war of (totally understandable) neglect rather than spite.

[1]: https://github.com/tridactyl/tridactyl/blob/master/readme.md

Re:Firefox 69.0 Released by Amezarak on Tuesday September 03, 2019 @04:47PM (#20870979)
Firefox gained the marketshare it did because power users relentlessly evangelized it to non-power users.

There was some of the same phenomenon with Google, but the real difference is that Google pushed Chrome very strongly on the biggest web properties in the world, had it packaged in some other software installers, and advertised it. That's why Chrome has the market-share it does today.

Mozilla appears to now be courting the ordinary user market without having either the passion of power users driving it, or the world's biggest web properties shilling it.

To this day, visiting google.com (#1 website) in my default browser pops up a large notification informing me I need to switch to Chrome to 'hide annoying ads and protect against malware on the web.' Visting YouTube.com (#2 website) pops up a slightly less annoying notification on the bottom that says "Google recommends using Chrome, a fast and secure browser."

I haven't been able to figure out for years now how they think this is going to work. Ordinary users are going to do what their IT administrator/IT friend says, use the OS default, or use products recommended by massive marketing campaigns.

Re:Firefox 69.0 Released by bscphil on Tuesday September 03, 2019 @07:31PM (#20872449)
This is it, exactly. No browser has ever gotten a dominant market share by convincing user Joe Average that it was better for their needs. That is an approach that is doomed to fail.

Just about every person I know that uses or used to use Firefox does so because I told them to use it or (more likely) I installed it for them. That's how most people start using Firefox.

Re:Firefox 69.0 Released by feanaro on Tuesday September 03, 2019 @05:38PM (#20871455)
I know Tridactyl is still installable, but the situation is not exactly reassuring about the viability of the extension in the future. Instead of a future in which Tridactyl asymptotically approaches the smoothness of Pentadactyl/Vimperator, I now have a vision of a future where a moderate-to-high amount of work has to be periodically invested in order to perhaps maintain the same level of functionality.

> On topic, I'd argue that Mozilla are just desperately trying to cling on to ordinary users; the "war" against power users is a war of (totally understandable) neglect rather than spite.

Perhaps, but meanwhile, as we muse about Tridactyl and the abandonment of userChrome and userContent, a thread about the possibility of Firefox removing webRequest in the future rises to #2. It's getting harder to justify Firefox and Mozilla by the moment.