DEV Community

Discussion on: What is the JavaScript runtime?

Collapse
 
snickdx profile image
Nicholas Mendez

From my understanding, I don't really relate hoisting with var to the event loop. I think its more an unintended consequence in the interpreter implementation.

twitter.com/BrendanEich/status/522...

Collapse
 
moose profile image
moose

without the pulling off the stack the event loop wouldn’t be necessary. From what I could read it still looks like there is still callback being made from the setTimeouts wrote to handle it. I dunno, i still see it as a huge characteristic as to why things are done a certain way. As far as single threaded concurrency goes, it looks like a “async await” rebranding. It’s an interesting concept, but putting all that work in to manage sleep states in thread specific operation look to give no real gainz. Interesting read, but it look like they just slapped a stick on an old implementation instead of doing something really useful. That just my hot take. The single threaded and non blocking nature gets lost which is some big reasons peopl like JS in the first place