Why code in Python+C if you can code in Lisp+Zig?

on YouTube ↗27m

" summary

Argues for replacing Python+C with Guile+Zig, demonstrating a working Guile–Zig binding via the C ABI and a February proof‑of‑concept that compiles and calls Guile C headers from Zig. Notes Guix contains 92,599 lines of Scheme that must build quickly, shows Zig examples (manual allocators, strict casting, error returns) and emphasizes no garbage collector in Zig for safer cross‑language linking. Recommends using a dynamic Lisp for development and Zig for hot, low‑level code.

AI-written summary · about

" chapters (11)

1. 0:00Biomatic challenges
2. 1:55Growth in functional programming
3. 4:32Guile and Andy Wingo
4. 5:52Introduction to Zig
5. 9:21Zig language features
6. 11:08Language selection criteria
7. 14:22Software quality and C++
8. 16:27Rust and technical history
9. 18:53Language choices and packaging
10. 20:48Conclusion and acknowledgements
11. 23:36Q&A session