Rendered at 21:03:36 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
CharlieDigital 1 days ago [-]
I get that Rust is the new hotness, but I feel like they really address different segments, even post AI.
C# tooling for HTTP and gRPC web services is really, really good and very competitive performance wise. The large set of base class libraries and first party libraries that continuously get patched is a win, too.
WorldMaker 3 hours ago [-]
Something that stood out in skimming the document was how close to parity the two languages seem to have in general, especially with things like Span<T> filling in a lot of the things that might have been "gaps" earlier in C# history. Knowing Microsoft's historic biases and wars, a part of me is wondering if this document is something of a trojan horse for the opposite conversation, trying to sell more Rust users that C# can be a "system's language" today when a Rust mindset is brought to it.
Especially the "unfair" comparison of the document sticking as much to the BCL as possible and trying to avoid NuGet packages, but needing cargo packages for a lot of the side-by-sides, seems to favor C# for some types of programming.
It's great that C/C++ developers are finally starting to see the light and moving to Rust. Maybe Rust is finally the bridge from C/C++ to C# that Microsoft has historically been missing and has been the source of some internal wars at Microsoft.
tester756 22 hours ago [-]
Why?
I'm C# Dev that'd want to learn Rust at some point and such guide makes it very helpful
CharlieDigital 15 hours ago [-]
Do you need to learn Rust to use it at this point?
I think the tooling matters more than the language at this point.
slopinthebag 21 hours ago [-]
idk, rust is really good for web services. it depends on your taste obviously but i prefer it to C#.
CharlieDigital 13 hours ago [-]
Would love more specifics because I think this is an area where C# shines especially with hot reload. Even better if you wire it with CSharpRepl (no rebuild at all).
baranul 12 hours ago [-]
Comes across as Microsoft sending a subliminal type of message. Technically, C# developers should not need to give a care about Rust (unless they want to), but Microsoft looks to be "poking with stick" for unstated purposes.
wronex 1 days ago [-]
And here I was hoping for Rust support in Visual Studio.
pjmlp 13 hours ago [-]
Most likely it will never happen, unless too many key customers ask for it.
C# tooling for HTTP and gRPC web services is really, really good and very competitive performance wise. The large set of base class libraries and first party libraries that continuously get patched is a win, too.
Especially the "unfair" comparison of the document sticking as much to the BCL as possible and trying to avoid NuGet packages, but needing cargo packages for a lot of the side-by-sides, seems to favor C# for some types of programming.
It's great that C/C++ developers are finally starting to see the light and moving to Rust. Maybe Rust is finally the bridge from C/C++ to C# that Microsoft has historically been missing and has been the source of some internal wars at Microsoft.
I'm C# Dev that'd want to learn Rust at some point and such guide makes it very helpful
I think the tooling matters more than the language at this point.
https://learn.microsoft.com/en-us/windows/dev-environment/ru...
https://code.visualstudio.com/docs/languages/rust