Ciro Santilli @cirosantilli 40

 Articles (13k) Discussions (29) Comments (66) Follows  Received likes Files

New Updated  Top  Announced  A-Z  Liked  Followed

B-tree Updated 2025-07-16

 View more

Like Binary search tree, but each node can have multiple objects and more than two children.

 Read the full article

Epyc Updated 2025-07-16

 Read the full article

webpack/sass Updated 2025-07-16

 View more

This example shows how to use Sass.

To make things simple, it generates a completely separate dist/index.js and dist/main.css which are manually included from index.html, and does not do any type of injection (neither Js into HTML nor CSS in Js).

 Read the full article

GNU Assembler Updated 2025-07-16

 Read the full article

How to convert async to sync in JavaScript Updated 2025-07-16

 View more

God, it's impossible! You just have to convert the entire fucking call stack all the way up to async functions. It could mean refactoring hundreds of functions.

To be fair, there is a logic to this, if you put yourself within the crappiness of the JavaScript threading model. And Python is not that much better with its Global Interpreter Lock.

The problem is that async was introduced relatively late, previously we just had to use infinitely deep callback trees, which was worse:

myAsync().then(ret => myAsync2(ret).then(ret2 => myAsync3(re3)))

compared to the new infinitely more readable:

ret = await myAsync()
ret2 = await myAsync2(ret)
ret3 = await myAsync3(ret3)

But now we are in an endless period of transition between both worlds.

It is also worth mentioning that callbacks are still inescapable if you really want to fan out into a non-linear dependency graph, usually with Promise.all:

await Promise.all([
  myAsync(1).then(ret => myAsync2(ret)),
  myAsync(2).then(ret => myAsync2(ret)),
])

Bibliography:

And then, after many many hours of this work, you might notice that the new code is way, way way slower than before, because making small functions async has a large performance impact: madelinemiller.dev/blog/javascript-promise-overhead/. Real world case with a 4x slowdown: github.com/ourbigbook/ourbigbook/tree/async-slow.

Anyways, since you Googled here, you might as well learn the standard pattern to convert callbacks functions into async functions using a promise: stackoverflow.com/questions/4708787/get-password-from-input-using-node-js/71868483#71868483