Mond_
Joined 1 year ago
Joined 1 year ago
The async design changed multiple times, and the current approach is that of requiring passing an I/O interface that encapsulates the logic, same approach as for passing around an allocator.
This effectively makes all I/O bound code "quasi-async", and it's all explicit and the caller is in control.
no?
just me?
ok
I don't think Carbon is dead, it just all depends on how easy it actually is to rewrite "all of C++" in Rust. (The jury is still out on this one, but it's not looking good.)
So again: You don't need plan mode, auto mode works just fine, there is no difference in the workflows here.
"Effort in GCP" is a red flag. (See Gemini CLI, which was shut down in favor of Antigravity CLI.)
Yes, it was developed by Google employees, that does not imply it has the full backing of Google, or Deepmind, or GCP. Notably, the website doesn't seem to claim this either.
> Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something.
He's not an AI Luddite by any means.