this paper on the design-space of async/await (from @tonofcrates, @ShriramKMurthi and Gavin Gray) is just fantastic. such a joy to read. are there more like this? i don't care about the topic, could be rpc, ffi, gc, whatever. just this kind of vibe. https://t.co/K2clskFG2T
A Design Space Exploration of Async/Await arxiv.org
AI Weekly's analysis
→
- A new arXiv paper argues no two languages implementing 'straight-line asynchrony' fully agree on how async execution actually behaves.
- The authors articulate a design space with nine dimensions covering the full lifecycle of an asynchronous computation.
- The exploration mixes concrete examples, informal design discussion and a formal semantics, but the abstract does not list the languages surveyed.
Read full analysis →
@ShriramKMurthi an interesting read, thanks! curious to hear your thoughts on the difference between agents and compilers I wrote about here, and how (if at all) it will affect your proposal: https://t.co/MeCKZFAwhf
Coding agents are not compilers gist.github.com
AI Weekly's analysis
→
- Goldberg argues compilers are stateless while coding agents are stateful, taking previous outputs as input and modifying code the user does not observe.
- He says peer code review is 'not about function, its about structure' — a maintainability check that agent-produced code equally needs, but that no one has defined for agents.
- He suggests smaller human teams with a single person directing a team of agents, closer to a product manager over trusted developers than an engineer running a build.
Read full analysis →
good time to remind that google played with watermarking text outputs already in 2011. with kinda similar techniques. https://t.co/SHXRNz5j6o
aclanthology.org
