Instead of ridiculing, perhaps we should take the point about setting achievable targets to heart. I know I will as it is clear to me that the language team didn't in 2019. Today I think @graydon_pub's had more good points about limits and sustainability than I used to.
-
-
-
That’s a non-sequitur. You can’t use an argument in favor of *slowing down* the rate of change to argue that the language isn’t changing fast enough.
- 5 more replies
New conversation -
-
-
I have seen, and been similarly confused by, posts which claim async/await was shipped too quickly. I’m like “I remember
@aaron_turon talking about async/await in 2016” -
I tend to view these kinds of comments as a simple proxy for "I feel like important feedback was ignored" (which is usually not true, but occasionally is). "Too fast" is just noise.
- 1 more reply
New conversation -
-
-
I don't get my toys fast enough. Mother, Mother!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I think they meant Golang, not Rust :p
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I feel like different components move at different speeds. Async/await took 3 years to bear fruit, and IMO was the most important feature delivered during that time. But the WASM target and ecosystem support dropped very quickly. Similarly, the WGs haul ass.
-
Not a criticism of anyone or any team. These are hard problems, and everyone who worked on futures did a great job. I’m loving Rust more and more each day that I use it.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.