6 ms·

It's hard to tell which camp is more angry: the C# developers stating Microsoft is ditching its own ecosystem or the Rust developers unwilling to accept anythin

It's hard to tell which camp is more angry: the C# developers stating Microsoft is ditching its own ecosystem or the Rust developers unwilling to accept anything in this category not being written in Rust. From my understanding, all three options (Go, C#, and Rust) represent a significant speedup. The only legitimate concern I see is the one around WASM support, which is quite valid. But at the end of the day, it seems like the team is making a decision that maximizes speed and deliverability, with the offset being that some cracks are now present (e.g. WASM). I can respect them for that choice.

metaltyphoon 2y ago
> The only legitimate concern I see is the one around WASM support, which is quite valid If this is also priority, wouldn't Rust be the right choice? I’m not sure Go and C#’s WASM story is that great.
- sepositus 2y ago
  The problem is there are multiple competing priorities at play here. I'm sure the dev team is aware of the poor WASM support. Still, as stated in the OP, they seriously value the ability to efficiently rewrite their current code in a more performant language without drastically altering it. Obviously, to someone depending on WASM, the latter brings no value to them, so they can more easily criticize the dev team because they are simply ignoring that priority.
Hemospectrum 2y ago
> It's hard to tell which camp is more angry: the C# developers stating Microsoft is ditching its own ecosystem or the Rust developers unwilling to accept anything in this category not being written in Rust. Is it really? I must be reading the wrong comments somehow. I've seen lots of Rust people express only brief and mild surprise: "Wait what? Oh, okay, that makes sense. Carry on." None of them are taking this as a death knell for Rust. Meanwhile, the C# camp is erupting in a crisis of faith because Anders Hejlsberg has eaten something other than his own dogfood. They are outright grieving over this announcement with much wailing and gnashing of teeth.
- sepositus 2y ago
  Sorry, there was another HN thread where the Rust backlash was a bit more pronounced. Wasn't clear from my original comment.

metaltyphoon 2y ago

> The only legitimate concern I see is the one around WASM support, which is quite valid If this is also priority, wouldn't Rust be the right choice? I’m not sure Go and C#’s WASM story is that great.

sepositus 2y ago
The problem is there are multiple competing priorities at play here. I'm sure the dev team is aware of the poor WASM support. Still, as stated in the OP, they seriously value the ability to efficiently rewrite their current code in a more performant language without drastically altering it. Obviously, to someone depending on WASM, the latter brings no value to them, so they can more easily criticize the dev team because they are simply ignoring that priority.

Hemospectrum 2y ago

> It's hard to tell which camp is more angry: the C# developers stating Microsoft is ditching its own ecosystem or the Rust developers unwilling to accept anything in this category not being written in Rust. Is it really? I must be reading the wrong comments somehow. I've seen lots of Rust people express only brief and mild surprise: "Wait what? Oh, okay, that makes sense. Carry on." None of them are taking this as a death knell for Rust. Meanwhile, the C# camp is erupting in a crisis of faith because Anders Hejlsberg has eaten something other than his own dogfood. They are outright grieving over this announcement with much wailing and gnashing of teeth.

sepositus 2y ago
Sorry, there was another HN thread where the Rust backlash was a bit more pronounced. Wasn't clear from my original comment.