Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

So, because of one poorly designed shitty website you're moaning about FF being bad? You should be moaning about Twitter with its bliveted 8 tons of javascript in a 5 pount sack.

You can add espn.com, washingtonpost.com and nytimes.com to that list as well.

Blivetware.



It's a fair complaint when this doesn't happen on other browsers.

Your website doesn't have to have "shitty poor design" for it to lag FF. Compare scrubbing in this React player in Chrome and Firefox: https://hsreplay.net/replay/WpWzqzkCHTGdEmbguHUoiC

It comes down to issues in the Firefox JS/DOM engines.


The websites I called Blivetware are shitty on all the browsers I've tried. I guess it's truly YMMV...

In my experience, Twitter and ESPN can bring any browser to its knees


I'd rather a browser that can handle shitty websites than hoping every website will somehow magically be written efficiently. Especially since FF is the only browser I know of that can't handle multiple active javascript sessions. It's completely absurd if you think about it, I mean it's a browser, for browsing websites, which use javascript.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: