nuko-suke-dev

4 ms·

1. 1.▲
   by nuko-suke-dev 3y ago

   Thanks for the feedback! I have been convinced that people can’t understand what the site is like and how to use it intuitively. This site needs to be more user-friendly.
2. 2.▲
   Show HN: Dandori – Visualize Your Tasks(dandori-web.com)

   5 points by nuko-suke-dev 3y ago|2 comments
3. 3.▲
   Show HN: You don't need to fetch with request url in JavaScript(github.com)

   3 points by nuko-suke-dev 4y ago|0 comments
4. 4.▲
   by nuko-suke-dev 4y ago

   I agree with you. It is difficult to measure how to improve the site performance concretely by using idle-task, but I will do this with my application.
5. 5.▲
   by nuko-suke-dev 4y ago

   Certainly.
6. 6.▲
   by nuko-suke-dev 4y ago

   Thank you for your good code review! In most cases, I agree with you. I will improve the code as you said gradually.
7. 7.▲
   by nuko-suke-dev 4y ago

   Sorry for the confusion. >this is a convenience wrapper around “requestIdleCallback” That's right. I changed README. https://github.com/hiroki0525/idle-task#features
8. 8.▲
   by nuko-suke-dev 4y ago

   `idle-task` has shim as below . https://github.com/hiroki0525/idle-task/blob/main/src/index.... References - https://developer.chrome.com/blog/using-requestidlecallback/...
9. 9.▲
   by nuko-suke-dev 4y ago

   >The README file presents it like an alternative to `requestIdleCallback`, while, in fact, it is a convenience wrapper around `requestIdleCallback`. It is a nice idea, but the description makes it confusing. That's right. I changed
10. 10.▲
    Show HN: Speed up your site by running JavaScript when the browser is idle(npmjs.com)

    94 points by nuko-suke-dev 4y ago|87 comments