undefined | Better HN

0 pointsraverbashing7y ago0 comments

Interesting. Works fine here

1st step to trying to debug would be removing your old profile completely, maybe try to disable extensions and HW rendering acceleration

0 comments

2 comments · 1 top-level

kossTKR7y ago· 1 in thread

Thanks but check out the other comments, or their subreddit, or any other HN FF thread. Many people have this problem.

Also i am a dev - i have tried all possible options to remedy this issue. I even wrote that i talked to FF devs directly. Wouldn't it be weird if i hadn't tried basic techniques?

It's like there is this weird tribal thing going on where there is this passive aggressive attitude towards the people having problems like "you guys must be idiots" even though there is dozens of comments with anecdata about no one using FF at their companies because of performance issues.

A lot of people have issues, some don't - doesn't make the ones that do have them complete imbeciles.

raverbashingOP7y ago

It's definitely frustrating, and sometimes even advanced devs don't know (or forget) about some detail that might be helpful.

Sometimes "why someone hasn't tried that" is less about being clueless and more about not assuming how much people know about things.

I can imagine someone at Mozilla going "how do we debug this" and failing to reproduce the problem (I run FF on two different Macs/OSX versions and it runs ok on both)

Maybe FF can add some telemetry or have a special debug version for those with the issue, but I see how it can be frustrating

j / k navigate · click thread line to collapse