lixiasky

5 ms·

1. 1.▲
   by lixiasky 7mo ago

   Thanks for the catch! You’re spot on about the missed wakeups. It's still a very early prototype—mainly just wanted to see if this whole architecture holds water. I'll definitely be adding the #StoreLoad fence and tightening up th
2. 2.▲
   by lixiasky 7mo ago

   I didn't realize the mods had un-killed this post yesterday, so my apologies for the late replies. I'm very grateful to them for doing that—I just only now saw that it was live.
3. 3.▲
   Show HN: I made a zero-copy coroutine tracer to find my scheduler's lost wakeups(github.com)

   49 points by lixiasky 7mo ago|3 comments
4. 4.▲
   by lixiasky 8mo ago

   Haha, point taken! I will try to dial down the "customer service mode" :) Re: GitHub: Yeah, thankfully I had the local git history, so the code was safe. Just lost the community interactions (stars/issues), which was a bumme
5. 5.▲
   by lixiasky 8mo ago

   Haha, you have a really sharp eye! 1. The Baby Wireshark: Unfortunately, my previous GitHub account got flagged/shadowbanned (still not sure why, and the appeal didn't work), so I lost access to that repo. I had to start fresh wi
6. 6.▲
   by lixiasky 8mo ago

   The legendary "Coroutines in C" article! Thanks for the reference—I learned a lot from his work. His use of macros to hide the switch statement is basically the spiritual ancestor of co_await. It is wild to think that C++20 essen
7. 7.▲
   by lixiasky 8mo ago

   You are absolutely right about the history (Conway coined the term in '63!). The assembly stack-switching you mentioned is the classic "Stackful" approach (like Fibers or Boost.Context). C++20 went the "Stackless"
8. 8.▲
   by lixiasky 8mo ago

   Oh absolutely! Adam Dunkels' work is legendary. It's kind of poetic that Protothreads achieved stackless concurrency via C preprocessor macros and Duff's device tricks, and now years later, C++20 finally baked that exact sam
9. 9.▲
   by lixiasky 8mo ago

   You are spot on about the distinction. C++ chose the stackless path for "zero-overhead" efficiency, but it definitely shifts the burden of safety and usability onto the library developers. Regarding safety and data sharing: You&#
10. 10.▲
    by lixiasky 8mo ago

    That is a fascinating comparison! History really does rhyme. What you described—suspending with a flag and resuming with new values—is surprisingly similar to how the C++20 compiler transforms coroutines into a state machine under the hood
11. 11.▲
    by lixiasky 8mo ago

    You hit the nail on the head. C++20 coroutines are indeed complex and the barrier to entry is high. However, that complexity actually forced me to start from first principles. It drove me to tackle the essential problems from the ground up
12. 12.▲
    Show HN: Writing a C++20M:N Scheduler from Scratch (EBR, Work-Stealing)(github.com)

    18 points by lixiasky 8mo ago|20 comments
13. 13.▲
    Show HN: Graphtune – A tiny AI-assisted graph algorithm scheduler (with a story)

    1 points by lixiasky 1y ago|0 comments
14. 14.▲
    Requesting ArXiv cs.PL endorsement for Py2C (Python-to-C compiler)

    4 points by lixiasky 1y ago|0 comments
15. 15.▲
    Show HN: Angle – An open-source alpha-stage Matlab alternative (student project)

    1 points by lixiasky 1y ago|0 comments
16. 16.▲
    by lixiasky 1y ago

    Whoa, that sounds really cool — I like the idea.
17. 17.▲
    by lixiasky 1y ago

    Thanks for the question! Yes, Vanta currently relies on gopacket for packet capture and parsing. As a student, my main goal was to build something clear, functional, and real — rather than reinvent everything from scratch. I'm actively
18. 18.▲
    by lixiasky 1y ago

    Haha, true to tradition, right?I’ll make sure to add an “Enable Historical CVEs” flag in the next release
19. 19.▲
    by lixiasky 1y ago

    Totally fair! I really appreciate the honesty. English isn't my native language, and most of the expressions I know come from TED talks, open source READMEs, and honestly... the kind of news clips our teachers play in class So yeah, th
20. 20.▲
    by lixiasky 1y ago

    Thanks a lot for sharing this — it's super helpful! Yeah, I’m currently using gopacket mainly to get something working fast, but I’ve been thinking about writing my own parsers from scratch to understand the protocols better. Your Hdr
21. 21.▲
    by lixiasky 1y ago

    Great question! I chose Go mainly because it's simple, efficient, and widely used — and honestly, it's the language I'm most comfortable with right now. I'm still a student, and I don’t have super big ambitions yet — I j
22. 22.▲
    by lixiasky 1y ago

    Thanks! I actually didn’t think that far ahead — I just wanted to build something within my ability, something that works and feels meaningful to me. If it happens to fill a niche, that’s a lucky bonus
23. 23.▲
    by lixiasky 1y ago

    Thanks for sharing your experience! Go really does shine here—I felt that even as a student building Vanta while learning, things came together surprisingly well. The features you mentioned sound awesome. I might give it a try later on—supp
24. 24.▲
    by lixiasky 1y ago

    Thank you for this — I had read Linus' first post before and never imagined my tiny tool would be compared to something with that kind of legacy. I'm just an undergrad student in China (not even CS major, unfortunately), and this
25. 25.▲
    Show HN: A toy version of Wireshark (student project)(github.com)

    265 points by lixiasky 1y ago|72 comments