@freddy It's not about the hardness of the puzzle. I don't think I'm even that skilled at solving hard puzzles.
I like things like "if-else" constructs. I like how when I see one, I know what it does.
@freddy It's not about the hardness of the puzzle. I don't think I'm even that skilled at solving hard puzzles.
I like things like "if-else" constructs. I like how when I see one, I know what it does.
On a personal level.
I got curious about computers because they are things I'm able to be curious about. That's it. That's the spark. I can explore them and learn how they work.
Computers are hard sometimes. Sometimes we can figure out ways to make them easier. But if we instead automate doing hard things, using AI to make doing hard things less effort, it doesn't lead to a place I'm excited about.
3/N
It's not just about how the story of how AI will make us all so much more "productive" that we'll all have much more free time, which has been told many times in modern history and has never been broadly true.
It is all that.
And.
2/N
I am a programmer in the year 2024 who doesn't use AI.
I'm not even curious about it.
It's not just the mistakes. Hallucinations. Artificial confidence.
It's not just the unconscionable energy use. Laundering and reinforcement of historical biases. Ripoff of creative works. Exploited workers. Scams. Bots. Political propaganda. Mass surveillance to train the beast. And this is just off the top of my head here.
1/N
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-series
A patch adding lime1 to LLVM is here: https://github.com/llvm/llvm-project/pull/112035
[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