Runtime code generation and execution in Go: Part 1 ok just published the very first part of my blog series on the weird world of runtime code gen/exec in pure Go. Check it out and hope you enjoy it!.

Global warming got certainly accelerated because of parsing OpenAI request body happening everywhere now.

See you all in Atlanta (I got two talks accepted for Envoy Con) 👋

メンション忘れてた. @knqyf263 さんがDowntown LAに遊びに来てたのでグランドセントラルマーケットでビール🍺.

🇺🇸LAX🛫🛬TPE🇹🇼👋.

i think this is partly why i believe it's incredible valuable for anyone to work on a compiler internal at least once in their career. Not necessarily need to actually build one from scratch, but deeply understanding, or contributing to a famous one should also be helpful enough.

the more Go code i review, the more i realize how hard it is to internalize how the Go runtime behaves, especially allocator. Being able to mentally visualize where each variable lives in memory space and how they would move is really powerful but hard to teach or acquire.

Finally

🇯🇵NRT🛫🛬LAX🇺🇸👋👋

Verified that the company exists

👋👋

all i want is Model Y with Frost Blue, not X.

This weather alone really makes me want to go back to LA.

see you next year KubeCon Japan (hopefully)👋👋.

an interesting discussion going on in my PR: the idea is that it would be really cool project to write Rust-async runtime using Envoy's event loop. It wouldn't be that hard but not easy either but if anyone wants to take on, feel free to reach out to me.

i will be at the project pavilion tomorrow at KubeCon Japan with @zhaohuabing as one of the maintainers of Envoy. Feel free to drop by and let's chat about anything related to Envoy.