5 ms·

Because the rest of the commentors in this thread seem to not be reading the article, there's a performance issue in Firefox due to the following unresolved bug

Because the rest of the commentors in this thread seem to not be reading the article, there's a performance issue in Firefox due to the following unresolved bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1190398 https://bugzilla.mozilla.org/show_bug.cgi?id=1190398

mmanfrin 6y ago
The link to the demo comes before the warning to firefox, don't shame commenters who chose to see the content at discussion first before reading below the fold.
- lbj 6y ago
  Who's shaming anyone?
  - m4r35n357 6y ago
    Guess . . . . "Because the rest of the commentors in this thread seem to not be reading the article"
    - naikrovek 6y ago
      We'll, they're not reading the article, yet they're expecting people to read their comment. And if not, why comment at all? I think some selective derision is warranted.
      - _Microft 6y ago
        While it says that "[...] you need to use a Chromium or Webkit browser to enjoy MONOSPACE live." (emphasis mine), it does not say "DO NOT USE FIREFOX UNDER ANY CIRCUMSTANCES, it will mess up your device for minutes" anywhere. We saw so many (warranted or unwarranted) "Best viewed with Chrome"-statements on the web already that we became desensitized to it years ago.
      - dang 6y ago
        No, please don't add derision to HN threads. When someone else is wrong, it's enough to supply correct information. That enhances the thread without damaging the commons. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
        naikrovek 6y ago
        Are you saying everything everyone says is above critique, or that derision specifically is not welcome?
        dang 6y ago
        The latter. It's never needed and does more harm than good.
        naikrovek 6y ago
        Ok. Thanks for answering.
mdoms 6y ago
5 years old and not a peep. That sounds about right.
- qalmakka 6y ago
  5 years? That's nice. https://bugzilla.mozilla.org/show_bug.cgi?id=70315 https://bugzilla.mozilla.org/show_bug.cgi?id=70315 took 18 years to get solved.
watt 6y ago
I wonder what exactly is Firefox dev team spending all that time saved by not fixing peformance issues such as the bug linked above. Chrome seems to be doing some things right and Firefox is just adrift...

mmanfrin 6y ago

The link to the demo comes before the warning to firefox, don't shame commenters who chose to see the content at discussion first before reading below the fold.

lbj 6y ago
Who's shaming anyone?
- m4r35n357 6y ago
  Guess . . . . "Because the rest of the commentors in this thread seem to not be reading the article"
  - naikrovek 6y ago
    We'll, they're not reading the article, yet they're expecting people to read their comment. And if not, why comment at all? I think some selective derision is warranted.
    - _Microft 6y ago
      While it says that "[...] you need to use a Chromium or Webkit browser to enjoy MONOSPACE live." (emphasis mine), it does not say "DO NOT USE FIREFOX UNDER ANY CIRCUMSTANCES, it will mess up your device for minutes" anywhere. We saw so many (warranted or unwarranted) "Best viewed with Chrome"-statements on the web already that we became desensitized to it years ago.
    - dang 6y ago
      No, please don't add derision to HN threads. When someone else is wrong, it's enough to supply correct information. That enhances the thread without damaging the commons. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
      - naikrovek 6y ago
        Are you saying everything everyone says is above critique, or that derision specifically is not welcome?
        dang 6y ago
        The latter. It's never needed and does more harm than good.
        naikrovek 6y ago
        Ok. Thanks for answering.

mdoms 6y ago

5 years old and not a peep. That sounds about right.

qalmakka 6y ago
5 years? That's nice. https://bugzilla.mozilla.org/show_bug.cgi?id=70315 https://bugzilla.mozilla.org/show_bug.cgi?id=70315 took 18 years to get solved.

watt 6y ago

I wonder what exactly is Firefox dev team spending all that time saved by not fixing peformance issues such as the bug linked above. Chrome seems to be doing some things right and Firefox is just adrift...