- Should you use web workers? I think you should. https://medium.com/thron-tech/web-workers-to-improve-ui-performance-a409a0714d92 3 comments webdev
Linked pages
- IE11 end of support countdown https://death-to-ie11.com/ 150 comments
- GitHub - neomjs/neo: The application worker driven frontend framework https://github.com/neomjs/neo 135 comments
- GitHub - developit/greenlet: 🦎 Move an async function into its own thread. https://github.com/developit/greenlet 45 comments
- Service Worker API - Web APIs | MDN https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API 14 comments
- The structured clone algorithm - Web APIs | MDN https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm 8 comments
- Swagger UI https://petstore.swagger.io/ 6 comments
- Remove shared workers? · Issue #315 · whatwg/html · GitHub https://github.com/whatwg/html/issues/315#issuecomment-244903762 1 comment
- GitHub - GoogleChromeLabs/comlink: Comlink makes WebWorkers enjoyable. https://github.com/GoogleChromeLabs/comlink 0 comments
- When should you be using Web Workers? — surma.dev https://surma.dev/things/when-workers/ 0 comments
- GitHub - OAI/OpenAPI-Specification: The OpenAPI Specification Repository https://github.com/OAI/OpenAPI-Specification 0 comments
Would you like to stay up to date with Web Development? Checkout Web Development
Weekly.
Related searches:
Search whole site: site:medium.com
Search title: Web Workers to improve UI performance | by Alberto De Agostini | THRON tech blog | Medium
See how to search.