embarklabs/embark
2
0
Fork 0
mirror of https://github.com/embarklabs/embark.git synced 2025-01-24 20:51:55 +00:00
Code Issues Projects Releases Wiki Activity

article: remove paragraph

Browse Source
This commit is contained in:
Pascal Precht 2020-01-07 10:51:51 +01:00
parent c8f86e55f0
commit a865bc3d6a
No known key found for this signature in database
GPG Key ID: 0EE28D8D6FD85D7D
1 changed files with 0 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
site/source/_posts/2019-11-21-nim-vs-crystal-part-2-threading-tooling.md
View File

@ -87,8 +87,6 @@ In Crystal, we can use the `Spawn` functionality in a very similar way to Gorout
`Fibers` are lightweight threads of execution that are managed by the garbage collector, so you don't *really* need to worry about managing them once you've spawned them. Because of this, you could technically spin up 100 `Fibers` to make a bunch of API requests, and then simply forget about them.
You *could* do this with OS threads, but `pthread_create` and `pthread_join` (the `libc` functions that usually back threads) are expensive system calls, so you really shouldn't.
We can utilise `Spawn` in Crystal like so:
``` crystal