Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use performance.now() for higher accuracy #16

Open
erlingur opened this issue Nov 22, 2014 · 3 comments
Open

Use performance.now() for higher accuracy #16

erlingur opened this issue Nov 22, 2014 · 3 comments
Assignees

Comments

@erlingur
Copy link

Have you looked at using performance.now() instead of Date.now()?

http://updates.html5rocks.com/2012/08/When-milliseconds-are-not-enough-performance-now
https://developer.mozilla.org/en-US/docs/Web/API/Performance.now

@mrchimp
Copy link
Owner

mrchimp commented Jan 6, 2015

I hadn't. Hmm, looks like I should...

I'll give it a go once #21 is merged.

@mrchimp mrchimp self-assigned this Jan 6, 2015
@jneuendorf
Copy link

jneuendorf commented Oct 9, 2017

Hasn't #21 (or #22 relatively) been merged quite a while ago? 😉

There is this library you could use to still have support for older browsers without the performance API (http://caniuse.com/#feat=user-timing). This lib would additionally add support for using tock in pure node environments.

@mrchimp
Copy link
Owner

mrchimp commented Oct 9, 2017

Pull requests are accepted ;)

I'll see if I can find some time to look into this soon. Thanks for the link.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants