You stay away from something you don't understand after 10 years of working with it? What kind of logic is that? Channels aren't magic.
Subtle bugs in what? Have you considered that maybe you have bugs because you aren't writing tests?
If you aren't unit testing that stuff, then how are you able to fix/change things and know it is resolved?
My experience is that I built a binary that had to run perfectly on 30,000+ servers across 7 data centers. It was full of concurrency. Without a litany of automated tests, there is no way that I would have trusted this to work... and it worked perfectly. The entire deployment cycle was fully automated. If it passed CI, I knew that it would work.
It wasn't easy, it took a lot of effort to build that level of testing. But it was also totally bug free in production, even over years of use and development.
Perhaps a less defensive posture might invite more discussion.
Whether it's an extension or "AI first", the impact of AI on IDE's will be massive and an IDE that doesn't do it well will be barely used.
I use mosh and gnu screen for flaky connections. Works wonders even if you disconnect every 10 seconds.
It's not about whether people can choose not to buy an iPhone, really at all. It's about once they do choose iPhone, is Apple unfairly using their control of the platform to influence whether they choose Apple's product vs a competitor for future things they buy.
What is the difference? Using polite words to communicate?