Day 24 of #JavaScriptChallenge by @ChaiCodeHQ @Hiteshdotcom • Learned about Execution Context & Call Stack • JS starts with Global Execution Context • Each function creates its own context • Two phases: Memory & Execution • Managed by Call Stack (LIFO)

codeXninjaDev's tweet image. Day 24 of #JavaScriptChallenge by @ChaiCodeHQ @Hiteshdotcom 
• Learned about Execution Context & Call Stack
• JS starts with Global Execution Context
• Each function creates its own context
• Two phases: Memory & Execution
• Managed by Call Stack (LIFO)
codeXninjaDev's tweet image. Day 24 of #JavaScriptChallenge by @ChaiCodeHQ @Hiteshdotcom 
• Learned about Execution Context & Call Stack
• JS starts with Global Execution Context
• Each function creates its own context
• Two phases: Memory & Execution
• Managed by Call Stack (LIFO)
codeXninjaDev's tweet image. Day 24 of #JavaScriptChallenge by @ChaiCodeHQ @Hiteshdotcom 
• Learned about Execution Context & Call Stack
• JS starts with Global Execution Context
• Each function creates its own context
• Two phases: Memory & Execution
• Managed by Call Stack (LIFO)
codeXninjaDev's tweet image. Day 24 of #JavaScriptChallenge by @ChaiCodeHQ @Hiteshdotcom 
• Learned about Execution Context & Call Stack
• JS starts with Global Execution Context
• Each function creates its own context
• Two phases: Memory & Execution
• Managed by Call Stack (LIFO)

United States Trends
Loading...

Something went wrong.


Something went wrong.