sir talks-a-lot
I know, dear reader: of course you have already seen all my talks this year. Your attentions are really too kind and I thank you. But those other people, maybe you share one talk with them, and then they ask you for more, and you have to go stalking back through the archives to slake their nerd-thirst. This happens all the time, right?
I was thinking of you this morning and I said to myself, why don’t I put together a post linking to all of my talks in 2023, so that you can just send them a link; here we are. You are very welcome, it is really my pleasure.
2023 talks
Scheme + Wasm + GC = MVP: Hoot Scheme-to-Wasm compiler update. Wasm standards group, Munich, 11 Oct 2023. slides
Scheme to Wasm: Use and misuse of the GC proposal. Wasm GC subgroup, 18 Apr 2023. slides
A world to win: WebAssembly for the rest of us. BOB, Berlin, 17 Mar 2023. blog slides youtube
Cross-platform mobile UI: “Compilers, compilers everywhere”. EOSS, Prague, 27 June 2023. slides youtube blog blog blog blog blog blog
CPS Soup: A functional intermediate language. Spritely, remote, 10 May 2023. blog slides
Whippet: A new GC for Guile. FOSDEM, Brussels, 4 Feb 2023. blog event slides
but wait, there’s more
Still here? The full talks archive will surely fill your cup.
One response
Comments are closed.
Thanks! That should keep me busy for a while (eh-eh-eh).
I’ve had a burning question about guile for some time now. You’ve managed to speed it up by (approx.) 15x between versions 1.7 and 3.0, for tak and mazefun benchmarks, which is outstanding. Guile’s performance in now between that of interpreted Petite Chez and compiled Gambit Scheme on those codes (last I checked, couple years back). The continuation-based ctak on the other hand does not seem to have seen a similar performance uplift. I find this puzzling because guile is now a produce of (yummy) CPS soup, from which I (naively?) would assume that continuation-based code would enjoy a most tasty spike in performance. Is enhancing call/cc perf on the TOD list of guile development, or is there something more fundamental (a design decision? something to do with fibers? or FFI?) that might be at play in this?