Opisek

The commenter implies your coil whine comes from "dirty power" from your power strip (not a perfect sine wave). This may or may not be the case, so it's at least one thing you can try out.

I see you're a person of culture. I too get flashbanged every morning by all my lights.

We move onto the next issue. How to precisely measure the length of the wire?

Your cat must be in on the conspiracy. Perhaps even part of the deep state.

What if you're the person yourself?

VSCode is not even a true IDE like, for example, VS itself.

Great details! I know the difference personally, but this is a really nice explanation for other readers.

About the last point though: I'm not sure Go always uses the maximum amount of kernel threads it is allowed to use. I read it spawns one on blocking syscalls, but I can't confirm that. I could imagine it would make sense for it to spawn them lazily and then keep around to lessen the overhead of creating it in case it's needed later again, but that is speculation.

Edit: I dove a bit deeper. It seems that nowadays it spawns as many kernel threads as CPU cores available plus additional ones for blocking syscalls. https://go.dev/doc/go1.5 https://docs.google.com/document/u/0/d/1At2Ls5_fhJQ59kDK2DFVhFu3g5mATSXqqV5QrxinasI/mobilebasic

But what if I wanted to be adopted. I need friends.

Well, they're userspace threads. That's still concurrency just like kernel threads.

Also, it still uses kernel threads, just not for every single goroutine.

I absolutely love how easy multi threading and communication between threads is made in Go. Easily one of the biggest selling points.

Perhaps I do belong isolated in the deep dark sea.

Three to not lose the _!