Web workers, which we already took a look at in a previous post, are very useful for parallelizing long-running CPU-bound work client-side so it doesn't freeze up a website while it's running. If you're using Webpack, you have the option of compiling your worker script as a separate bundle using the worker loader.
Read more →Most of the time, JavaScript developers don't need to worry about CPU-intensive tasks. Every once in a while, though, some long-running, CPU-heavy work needs to be done client-side (for example, plotting an equation on a graph). If you try to do that sort of work in plain-old JavaScript client-side, it will block and cause the website to freeze up and become unresponsive until it's done, which isn't very good UX.
Read more →I'm a full-stack developer with more than a decade of experience designing, building, deploying, and monitoring web applications and APIs. My specialties are AWS, JavaScript, and .NET. You can read more about me on the about me page.
