http://valerii-udodov.com/tags/javascript-runtime/ Recent content in javascript runtime on Val's Tech Blog Hugo -- gohugo.io en vudodov@gmail.com (Valerii Udodov (aka Val)) vudodov@gmail.com (Valerii Udodov (aka Val)) Tue, 19 Oct 2021 11:14:23 +1000 http://valerii-udodov.com/posts/javascript-memory/ Tue, 19 Oct 2021 11:14:23 +1000 vudodov@gmail.com (Valerii Udodov (aka Val)) Tue, 19 Oct 2021 11:14:23 +1000 http://valerii-udodov.com/posts/javascript-memory/ Don’t forget to subscribe ✉️, so you won’t miss latest news and articles. I’ll start this article with a quote that changed the way I think of memory. The way I perceive memory lifecycle in major modern languages (those that have automatic memory release aka garbage collection). Garbage collection is simulating a computer with an infinite amount of memory. – Raymond Chen This is exactly how we think of memory in JavaScript. Valerii Udodov (aka Val) featured image javascript javascript runtime browser javascript garbage collector javascript engine exploration javascript http://valerii-udodov.com/posts/run-javascript-run/ Thu, 09 Sep 2021 11:14:23 +1000 vudodov@gmail.com (Valerii Udodov (aka Val)) Thu, 09 Sep 2021 11:14:23 +1000 http://valerii-udodov.com/posts/run-javascript-run/ Don’t forget to subscribe ✉️, so you won’t miss latest news and articles. Preamble Let’s admit. JavaScript is not the most predictable language out there. It might get pretty quirky very easily. Let’s look at the following example. 1 2 3 4 5 6 7 8 setTimeout(() => console.log("1. timeout")); console.log("2. console"); Promise.resolve("3. promise").then((res) => console.log(res)); // prints // 2. console // 3. promise // 1. timeout Even if we will change the order of instructions, it won’t impact the final result 🤨 Valerii Udodov (aka Val) featured image javascript web browser javascript runtime browser javascript engine exploration javascript