3 ms·
I get what you’re saying, but you kicked off this thread like an expert — even though you knew you were talking to someone who helped build the very thing you’r
by LatencyKills 7mo ago
I get what you’re saying, but you kicked off this thread like an expert — even though you knew you were talking to someone who helped build the very thing you’re critiquing.
It’s pretty clear you’ve never built a production-grade async state machine.
C++ is designed to provide the plumbing, not the kitchen sink. It’s a language for building abstractions, not handing them to you — though in practice, there’s a rich ecosystem if you’d rather reuse than reinvent.
That flexibility comes at the cost of convenience, which is why most new engineers don’t start with C++.
What you call “intimidating,” I call powerful. If coroutines throw you off, you’re probably using the wrong language.
Last thought — when you run into someone who’s built the tools you rely on, ask them questions instead of trying to lecture them. I would have been more than happy to work through a pedagogical solution with you.
/ignored
- HarHarVeryFunny 7mo ago> It’s pretty clear you’ve never built a production-grade async state machine. Haha .. you have no idea. FWIW I've built frameworks exactly for that, and it's highly likely that you've unwittingly used one of them.
- LatencyKills 7mo agoUh huh. The person who gets confused by how co_wait() actually works and thinks that coroutines are "intimidating" wrote frameworks that I would have used to build our C++ compiler. Do you not understand that cl.exe doesn't use external frameworks? lmfao
- HarHarVeryFunny 7mo agoI said used, as in used in your everyday life, by interacting with computer systems whose backend implementations you are blissfully ignorant of. But yeah, if you want to win arguments then arguing against yourself and your own hallucinations, is in your case the best way to go.
- LatencyKills 7mo agoUm... you might want to look at my profile. In addition to working at MS and Apple for two decades (where I touched everything from firmware, ring-0, and ring-3), I was on the team that created SoftICE [0]: the first commercial ring-0 debugger for Windows. I also created the automated deadlock detector for BoundsChecker [1], which requires an in-depth understanding of operating system internals. > computer systems whose backend implementations you are blissfully ignorant of I am extremely confident in my "backend" knowledge (of course, an actual systems engineer would never refer to their work as "backend"). You wrote a "C++ framework" that runs in the "backend" of a "computer system"? Do I have that right? Please let me know what it is so that I can decompile it and see how it was implemented! [0]: https://en.wikipedia.org/wiki/SoftICE https://en.wikipedia.org/wiki/SoftICE [1]: https://en.wikipedia.org/wiki/BoundsChecker https://en.wikipedia.org/wiki/BoundsChecker
- HarHarVeryFunny 7mo ago> You wrote a "C++ framework" that runs in the "backend" of a "computer system"? Do I have that right? Probably not. You seem to be struggling with technical language.
- LatencyKills 7mo agoSee? I have no problem sharing/discussing what I've built. Throughout this entire thread they only thing you've done is bullshit. And again, remember that this started because you thought coroutines were "intimidating" while trying to mansplain how they worked to someone who literally built that functionality. But sure... let's keep going while you do nothing but whine without displaying any technical acumen. This is fun! Why don't you hop into the discussion of the early Windows ring-3-to-ring-0 transition issues [0] we had in the 90s? You know... since I am "blissfully ignorant" about internals. I can't wait to learn from your "backend" expertise!! [0]: https://news.ycombinator.com/item?id=47611921#47612953 https://news.ycombinator.com/item?id=47611921#47612953
- HarHarVeryFunny 7mo ago