I don't think that "flickers between tasks very rapidly to simulate concurrency" is a good mental model for event loops. It's more like "runs one task at a time until it hits a suspension point," where a suspension point is something like an I/O operation. If you had an event loop that switched tasks between suspension points, then you'd still need locks for shared data.
Guess it depends on what you think is frequently, maybe once or twice a year when working in a office setting. Always happened at small companies, and usually what was sparked in the conversation had a big impact on what the company worked on.
So for the off chance that once in 6 months you have a conversation in person that "sparks something" everyone has to suffer commutes and all the other crap that comes with WFO?
No, I think people should be able to make a choice between working in a office vs working remote, which considering how many jobs are remote nowadays, you can kind of already do.
I'm not saying all companies should work in a office, I'm just sharing my viewpoint from someone who prefers in office compared to remotely.
> It seems the developer works for Tailscale in an evangelist / developer relations role. I feel that ought to have been disclosed in this article.
Note that the author of gokrazy is Michael Stapelberg (perhaps better known for writing i3), who doesn't seem to be directly affiliated with Tailscale.
the whole vtuber thing is not really for me, but i appreciate the effort that went into this presentation—did you make it all the way to <https://asahilina.net/agx-exploit/#/demoslide>?
> What drives me nuts is autocomplete, because it pops things into my vision automagically while I'm trying to focus on the code, and even effects a mode change (some keys do different things when autocomplete is active).
Totally agree! I disable "press Enter to accept suggestion" in JetBrains IDEs for this reason.