3 ms·

> Several times a day, Firefox goes unresponsive for a few seconds. This is caused by concurrency?

• hollerith 12y ago
  That is my best guess. I could be wrong. Should people refrain from publishing their guesses on HN? None of the programs I have used that lack threads, including lynx, have this kind of glitchiness. (Also, I think early versions of X lacked threads and at least when paired with certain video cards, were free of glitchiness -- or more precisely, a user could learn to operate X in such a way as to avoid glitchiness.) In particular, my guess is that although it is theoretically possible to write huge multi-threaded programs that do not exhibit glitchiness, in reality it is too hard for even very skilled human programmers to do it, and that is why Firefox has the glitchiness property. I am willing to listen to arguments to the contrary. P.S. I would have supposed that those who disagree with my conclusion would simply deny that Firefox is glitchier than Emacs or would simply conclude that the difference in glitchiness is irrelevant. Do you agree with me that it is glitchier and that the glitchiness matters? (Again, I realize the glitches are rare -- maybe only a few a day. They do affect my experience of the app, though.)