Skip to content

Commit 5c56e0d

Browse files
committed
minor
1 parent 36bf2af commit 5c56e0d

File tree

7 files changed

+11
-1
lines changed

7 files changed

+11
-1
lines changed
Loading

Diff for: 2-ui/1-document/11-coordinates/[email protected]

-9.18 KB
Loading
Loading

Diff for: 2-ui/1-document/11-coordinates/[email protected]

-4.09 KB
Loading

Diff for: 2-ui/4-forms-controls/3-events-change-input/article.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Events: change, input, cut, copy, paste
22

3-
Let's discuss various events that accompany data updates.
3+
Let's cover various events that accompany data updates.
44

55
## Event: change
66

Diff for: 2-ui/99-ui-misc/03-event-loop/article.md

+10
Original file line numberDiff line numberDiff line change
@@ -337,3 +337,13 @@ To schedule a new microtask:
337337
There's no UI or network event handling between microtasks: they run immediately one after another.
338338

339339
So one may want to `queueMicrotask` to execute a function asynchronously, but also with the same application state.
340+
341+
```smart header="Web Workers"
342+
For long heavy calculations that shouldn't block the event loop, we can use [Web Workers](https://html.spec.whatwg.org/multipage/workers.html).
343+
344+
That's a way to run code in another, parallel thread.
345+
346+
Web Workers can exchange messages with the main process, but they have their own variables, and their own event loop.
347+
348+
Web Workers do not have access to DOM, so they are useful, mainly, for calculations, to use multiplle CPU cores simultaneously.
349+
```

Diff for: figures.sketch

376 KB
Binary file not shown.

0 commit comments

Comments
 (0)