From 594e8aa28d146c755551a61c3f68ba7ad430329d Mon Sep 17 00:00:00 2001 From: Lars Kappert Date: Mon, 29 Apr 2024 08:13:17 +0200 Subject: =?UTF-8?q?it's=20=E2=86=92=20it=20is?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../lesson07_multi_target_externals/en.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'src/content/chapter5_advanced_features/lesson07_multi_target_externals') diff --git a/src/content/chapter5_advanced_features/lesson07_multi_target_externals/en.html b/src/content/chapter5_advanced_features/lesson07_multi_target_externals/en.html index c755ac7..6e02d36 100644 --- a/src/content/chapter5_advanced_features/lesson07_multi_target_externals/en.html +++ b/src/content/chapter5_advanced_features/lesson07_multi_target_externals/en.html @@ -11,10 +11,10 @@ possible due to incompatibilities in how IO and concurreny works in Erlang and JavaScript. With Erlang concurrent IO is handled transparently by the runtime, while in JavaScript concurrent IO requires the use of promises or callbacks. - If your code uses the Erlang style it's typically not possible to implement in - JavaScript, while if callbacks are used then it won't be compatible with most - Gleam and Erlang code as it forces any code that calls the function to also - use callbacks. + If your code uses the Erlang style it is typically not possible to implement + in JavaScript, while if callbacks are used then it won't be compatible with + most Gleam and Erlang code as it forces any code that calls the function to + also use callbacks.

Libraries that make use of concurrent IO will typically have to decide whether -- cgit v1.2.3