1,791 karma · joined October 29, 2013
Even just checking for the existence of a file can take a really long time depending on the disk speed and other on going IO.
https://blog.pyston.org/2017/01/31/pyston-0-6-1-released-and...
https://opensource.googleblog.com/2017/01/grumpy-go-running-...
This pull request has timings with this changed: https://github.com/atilaneves/pythagoras/pull/1#issuecomment...
Also the page they link to is not just measuring parse time but also compilation time.
2) My display options are set to "more space"
3) I loaded this hackernews thread.
4) Firefox and it's child processes are using <1% cpu.
If I aggressively scroll this page I can push the cpu usage up. We have a variety of fixes in the pipeline that will help with this (https://bugzilla.mozilla.org/show_bug.cgi?id=1429522, https://bugzilla.mozilla.org/show_bug.cgi?id=1265824). That being said, only 4.7% of our users are on MacOS so it's more difficult to justify prioritizing work specific to that platform.
If you're actually experiencing 100% cpu usage, post a profile using https://perf-html.io/ and I can try tell you why.
Linux users are about 2.7% of Firefox users
Windows users are 93.2% of Firefox users
27.7% of Windows users don't have Direct2D
That means 25.8% of users "run windows on hardware without decent graphics hardware". So it's entirely reasonable to prioritize these 25.8% of users over the 2.7% on Linux.
It brings back the option of writing one graphics backend, having it work everywhere, and as a bonus not having to deal with terrible API that is OpenGL.
https://www.intel.com/content/www/us/en/support/articles/000...