It is very sad that is apparently planning to reduce performance.now() resolution to 2ms, making it effectively useless and no different to Date.now(). No other browsers are doing this.
Conversation
This makes writing in-browser performance measurement for JS execution impractical, which will in turn make our apps slower. Not to mention other usecases:
2
3
6
Replying to
Isn't this for Spectre/Meltdown mitigation? blog.mozilla.org/security/2018/ - it sucks, but it's necessary.
Replying to
The other browsers are doing 20µs resolution, which is still usable for perf measurement usecases. 2ms on the other hand is a whole different kettle of fish. If it is truly necessary to completely destroy this API then I would like to see more public communication about why.
1
2
Right, gotcha. Have you talked to any of the SpiderMonkey devs? On Bugzilla or IRC? Seems like valuable input to have. cc.
1
Show replies