It's strange hearing reports of "scroll lag" in the other comments. It's possible I'm just lucky. Or there's a misconfiguration somewhere in their setup that Chrome somehow avoids.
It's true that I still mostly use Chrome for webdev - I've become more used to it's (excellent) dev tools, even though Firefox and Firebug started that whole trend. It feels very right to separate my "user browser" from my "dev browser" in this way!
Don't forget the other possibility: someone using Firefox having internalized this lag as "normal behavior".
(Personally I'm with you in preferring Firefox dev tools - although I'm not someone who needs to use them more than a few times a month - not because I have any specific issues with Chrome dev tools, but because I prefer Firefox, and Mozilla, generally, and I've not found anything that FF can't do.)
Have some humility.
(I use firefox devtools primarily)
I find this very common with Credit Card and Banking Sites. Very often they either refuse to log me in or log me out sooner than they should on Firefox, or certain pages within the site will just not load. I'm guessing they prioritize security, and only test this stuff in Chrome ;(
Camino was originally named Chimera. It was started by Dave Hyatt, the guy who went to Apple to build Safari and WebKit, which Chrome now uses.
I've known lots of developers who thought that some broken, slow, erratic, or stupid, program or OS behavior is the normal, because that's what they've been used to. They could be great programmers too, they just didn't venture much outside the stuff they used.
As for the diatribe, I don't care for this recent trend of perceiving something somebody said as some kind of abuse of "therapy speak" (before this comment I've seen a few stories about some actor "abusing therapy speak" and such lately, so I assume it's some new fad going on). I don't read about therapy, or had any therapy speak in mind. "Internalized" has been used for decades as a term, and here just means "accepted this lag as the baseline as they don't have a frame of reference". Might not even be the right word, I probably was looking for normalized (is that therapy speak too?). So there's that.
I was sad when they discontinued Firefox for my TV (even though it was mostly an Amazon-funded workaround to get youtube on FireTV which went away when YouTube started working...).
That said, there is something to be said for modern applications just running way below the limits of the refresh rate of our screens: https://twitter.com/jmmv/status/1671670996921896960
This describes so much software that I don't see how you can fault anyone for thinking it is normal.
Reddit.com and Discord have replaced many individual forums.
I'm working on a pretty nasty (legacy and poorly optimised) but otherwise still rather "normal" website at work.
Opening the dev tools makes Firefox hang for almost a minute, I suspect this is due to some issue with source maps, thousands of source files and large (several megabytes of) minified code.
The debugger often reports _wrong_ values on hover especially in useEffects whereas console.log shows the right one.
Other than the js debugger I have 0 problems with the Firefox devtools, it often spearheads features that I use on a day-to-day basis like highlighting grid layouts. Super nice!
[0]: https://support.microsoft.com/en-us/office/which-browsers-wo...
>One other possibility is that I know what scroll lag is, don't see it in Firefox on my devices"
Yes, that's "one other" possibility.
Now, can we also entertain the possibility I suggested as something that one can't just rule out in advance, and that one would be OK in suggesting could also be the case?
I don't know you, have not met you, and I don't speak about you as a person. I made a general observation about what could be the case when someone says what you said. Another commenter also corroborated having seen this in the wild (assuming it even needs corroboration). It's hardly something that doesn't happen. And because I'm a somewhat insulted by your tone, notice how I didn't even said anything about you directly. I wrote:
"Don't forget the other possibility: someone using Firefox having internalized this lag as "normal behavior".
The rest, you brought into this. Enough is enough. Over and out.
In the next tweet he compares it to a stock Surface Go 2 (quad-core i5 processor at 2.4GHz, 8GB RAM, SSD) and seems to be surprised that it performs like crap. His 600MHz CPU is sufficient to get decent input lag from NT 3.51 which lists a 25 MHz CPU as it's minimum spec just as my machines get decent input lag from Windows/macOS which list a 1.2 GHz CPU as the minimum spec.
I know clock speed is a bad metric, but you get the point. Your hardware needs to be well above the minimum spec by an order of magnitude if you want acceptable latency