"outdated article" the commit tested is 3 months old.

This is a standard V community tactic: all negative feedback is "bashing", anything older than a week is "outdated", anything up to date shouldn't have been written and posted on the issue tracker to be ignored instead.

Stop trying to control everyone else's speech and just work on fixing the long list of issues folks already took the time to report.

> it will process events while waiting for syscall

How does that work?

According to the source code quoted in the article, there is a separate "coroutine-safe version of time.sleep", which seems like it shouldn't be needed if V has a general solution for unblocking blocking syscalls.

> 1. what exactly does not works? This is so unhelpful 2. then report an issue on GitHub 3. exactly for that purpose `-skip-unused` exists, but Rust generates large binaries too 4. please read how coroutines work under hood, it will process events while waiting for syscall. 5. we welcome folks that aren't bashing on V using outdated "articles aganist V"

The GP was merely summarizing the article. They are not making any claims themselves.