@fvsch @sunfish @freddy @baldur A friend of mine as tried out AI in VisualStudio and it's only marginally better to classic code completion. Any actual hard problem he has to resolve himself anyway.AI can only suggest things that have frequently been solved before. It cannot solve new problems.

@freddy @sunfish My son is a CS student, and he said that most of his classmates use AI to finish assignments. He doesn't, because he wants to understand what's happening.I wouldn't be surprised if he's lying to me, not because he has a history of lying but because, frankly, if ChatGPT existed when I took programming courses 30 years ago I would have used it.But if he's telling the truth, I expect him to run circles around most other engineers with similar experience within years.

Introducing: Lime, a new series of CPUs.Virtual CPUs, that is. Or rather, Virtual CPU feature sets .So far, LLVM only has one Wasm CPU defined which is stable, "mvp". The "generic" and "bleeding-edge" CPUs evolve (carefully) over time, which works well for many users, but not all. "lime1" is a new CPU tools like LLVM can target which is an update to "mvp", and which is intended to be stable.https://github.com/WebAssembly/tool-conventions/blob/main/Lime.md#the-lime-seriesA patch adding lime1 to LLVM is here: https://github.com/llvm/llvm-project/pull/112035#Wasm

[wasi-messaging] was just voted to advance to [phase 2]!It's useful in practice on its own, but I'm also interested in how this is a milestone for the broader [wasi-cloud-core]'s `service` world, which has the potential to become an important new world, along side the POSIX-oriented `command` world and the HTTP-oriented `proxy` world.[wasi-messaging]: https://github.com/WebAssembly/wasi-messaging[phase 2]: https://github.com/WebAssembly/WASI/blob/main/Contributing.md#2-feature-description-available-wasi-subgroup[wasi-cloud-core]: https://github.com/WebAssembly/wasi-cloud-core#WASI #Wasm