From 7c8523c6bbcef204377de5404f0231c856ec3358 Mon Sep 17 00:00:00 2001 From: Walter van der Giessen Date: Wed, 20 Dec 2023 00:18:49 +0100 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index bd415e4..3f9e3bf 100755 --- a/README.md +++ b/README.md @@ -20,7 +20,7 @@ Depending on the environment, it uses [Worker Threads](https://nodejs.org/api/wo ### The State of Multithreading in JavaScript -JavaScript's single-threaded nature means that tasks are executed one after the other, leading to potential performance bottlenecks and underutilized CPU resources. While Web Workers and Worker Threads offer a way to offload tasks to separate threads, managing the communication between these threads and their state is often complex and error-prone. +JavaScript's single-threaded nature means that tasks are executed one after the other, leading to potential performance bottlenecks and underutilized CPU resources. While [Web Workers](https://developer.mozilla.org/en-US/docs/Web/API/Worker) and [Worker Threads](https://nodejs.org/api/worker_threads.html) offer a way to offload tasks to separate threads, managing the communication between these threads and their state is often complex and error-prone. This project aims to solve these challenges by providing an intuitive Web Worker abstraction that mirrors the behavior of regular JavaScript functions. This way it feels like you're executing a regular function, but in reality, it's running in parallel on a separate threads.