@cfbolz@mastodon.social
PyPy/RPython contributor. Half time teaching at Uni Düsseldorf. Works on dynamic language implementations. Vegan. Love street art and art in public spaces, hiking, reading.
they/them
I want to offset all my recent compiler-posting somehow, so here's a thread about my recent small bike tour through Duisburg (where I live).
The plan for the bike tour was to find a sculpture in the industrial north of Duisburg. One of my hobbies is to try to keep the Wikipedia list "artworks in public space in Duisburg" up to date: http://kunst-in-duisburg.de/
On Twitter I had a thread going this year in which I tried to reflect on bugs that I found throughout the year, how to avoid this kind of bug, what can be learned, etc. I will port this idea over to here and see how it goes in the future (I'm still both here and on Twitter, we'll see how that goes).
The article about Clang's bytecode interpreter (for constexpr evaluation etc) is super interesting, but I'm still incredibly amused by C++ compiler authors having to care about interpreter performance
https://developers.redhat.com/articles/2025/10/15/clang-bytecode-interpreter-update
Anyway, this just is another fun example interpreters and compilers being intermingled in silly ways. We put a (bytecode) compiler into your compiler so you can compile (and then interpret) while you compile
Elk is a nimble Mastodon web client. You can login to your Mastodon account and use it to interact with the fediverse.
Expect some bugs and missing features here and there. Elk is Open Source and we're actively improving it as a community project. Join us and let's build it together!
If you'd like to report a bug, help us testing, give feedback, or contribute, reach out to us on GitHub and get involved.
To boost development, you can sponsor the Team through GitHub Sponsors. We hope you enjoy Elk!
