Xichom2k's comments

Go is a perfect information game. RTS are not.

And the micro advantage is not all that relevant since APM and latency restrictions can be imposed on the AI to force them to play under conditions comparable to human players.

You can yield back to the UI event loop in an async function through

   await new Promise((resolve) => setImmediate(resolve))

or similar constructs using setTimeout or requestAnimationFrame

Sure, it's incremental, but static site layouts, especially the old float-based ones will have had their headers and sidebars loaded from the start and the main content would not jump around.

Modern pages with ads and widgets popping in potentially anywhere main remain unusable and unreadable because the main content keeps jumping around.

Not in strict mode

To put it bluntly I only see radical shouting on twitter from both sides (look at the latest tweets from the CoC author and the reactionary responses). I have not really experienced it in real life.

So the debate itself seems to be like an alien war fought above my head with the occasional fallout dropping on projects I care about. I would very much prefer both sides to do more coding and less clawing at each other.

Due to javascript's funky notion of object methods. If you just pass the function reference itself invoking it will execute it with a |this| set to undefined.

Put differently, a property access x = foo.bar followed by x() is not the same as foo.bar()

link: https://lkml.org/lkml/2018/9/19/234

Some of the replies are worth a read too. I like the one on cultural differences because it resonates with me that the whole CoC thing seems to be a very american thing.

I don't think scroll gestures or incrementally-loaded content with layout reflows were a thing back then, so that might need re-evaluating.