> I believe that it is a remarkably well designed language
> and just overall a poor debugging experience make async Rust a frustrating experience for rapid iteration.
> is the result of conscious trade-offs, trade-offs that I believe were chosen correctly. I don’t believe that async Rust necessarily needs to change at all, although I don’t doubt that the experience could be improved.
That's rust for you. It's a remarkably well designed language. Except for all the ways it isn't. What's hilarious to me is none of these are even deep or hard to find issues. Right out of the gate.. cargo is a wart.. and async was designed inside out.
Remarkable. Indeed.
So, _of course_, let's use it to implement a _different_ language entirely. The niche is disappearing.
> and just overall a poor debugging experience make async Rust a frustrating experience for rapid iteration.
> is the result of conscious trade-offs, trade-offs that I believe were chosen correctly. I don’t believe that async Rust necessarily needs to change at all, although I don’t doubt that the experience could be improved.
That's rust for you. It's a remarkably well designed language. Except for all the ways it isn't. What's hilarious to me is none of these are even deep or hard to find issues. Right out of the gate.. cargo is a wart.. and async was designed inside out.
Remarkable. Indeed.
So, _of course_, let's use it to implement a _different_ language entirely. The niche is disappearing.