Beyond Unicorn: Why I Code-Gen Instead of Emulating
Emulation is wrong when you call the same routine thousands of times. How Alicorn lifts x64 to C# and replaces Unicorn on the hot path.
Feed URL
Copy this link to your feed reader
https://corentings.dev/atom.xml Emulation is wrong when you call the same routine thousands of times. How Alicorn lifts x64 to C# and replaces Unicorn on the hot path.
A guided reading order through the Go concurrency patterns that compound: producer-consumer, generator, worker pool, pipeline, semaphore, context, and real-world examples. The shortest path to writing concurrent Go you can reason about.
Build DDD aggregates and repositories in TypeScript with TDD. Enforce invariants and test application flows with an in-memory repository.
Building a native x64-to-C# transpiler sounds simple until you meet the RFLAGS register. The question behind Alicorn, and what the gap keeps teaching me.
Go context cancellation without the fluff: timeouts, request lifecycles, errgroup fan-out, and graceful shutdown — no leaked goroutines.
Goroutines and async/await solve the same problem from opposite assumptions. A polyglot's take on primitives vs compiler-managed patterns.
Atom (Atom Syndication Format) is an XML-based standard for describing feeds and their items. With Atom, you can: