Rust for C#/.NET Developers
-
[Introduction - Rust for C#/.NET Developers](https://microsoft.github.io/rust-for-dotnet-devs/latest/)[^]: This is a (non-comprehensive) guide for C# and .NET developers that are completely new to the Rust programming language. Some concepts and constructs translate fairly well between C#/.NET and Rust, but which may be expressed differently, whereas others are a radical departure, like memory management. This guide provides a brief comparison and mapping of those constructs and concepts with concise examples.
Now you have no excuse not to learn Rust!
-
[Introduction - Rust for C#/.NET Developers](https://microsoft.github.io/rust-for-dotnet-devs/latest/)[^]: This is a (non-comprehensive) guide for C# and .NET developers that are completely new to the Rust programming language. Some concepts and constructs translate fairly well between C#/.NET and Rust, but which may be expressed differently, whereas others are a radical departure, like memory management. This guide provides a brief comparison and mapping of those constructs and concepts with concise examples.
Now you have no excuse not to learn Rust!
-
[Introduction - Rust for C#/.NET Developers](https://microsoft.github.io/rust-for-dotnet-devs/latest/)[^]: This is a (non-comprehensive) guide for C# and .NET developers that are completely new to the Rust programming language. Some concepts and constructs translate fairly well between C#/.NET and Rust, but which may be expressed differently, whereas others are a radical departure, like memory management. This guide provides a brief comparison and mapping of those constructs and concepts with concise examples.
Now you have no excuse not to learn Rust!
-
[Introduction - Rust for C#/.NET Developers](https://microsoft.github.io/rust-for-dotnet-devs/latest/)[^]: This is a (non-comprehensive) guide for C# and .NET developers that are completely new to the Rust programming language. Some concepts and constructs translate fairly well between C#/.NET and Rust, but which may be expressed differently, whereas others are a radical departure, like memory management. This guide provides a brief comparison and mapping of those constructs and concepts with concise examples.
Now you have no excuse not to learn Rust!
-
[Introduction - Rust for C#/.NET Developers](https://microsoft.github.io/rust-for-dotnet-devs/latest/)[^]: This is a (non-comprehensive) guide for C# and .NET developers that are completely new to the Rust programming language. Some concepts and constructs translate fairly well between C#/.NET and Rust, but which may be expressed differently, whereas others are a radical departure, like memory management. This guide provides a brief comparison and mapping of those constructs and concepts with concise examples.
Now you have no excuse not to learn Rust!
Along a similar line, back in college when I took a class in C, we used a book which was designed to teach C to developers who knew Pascal. "C as a Second Language" C as a second language : for native speakers of Pascal : Müldner, Tomasz : Internet Archive[^]
-
Nooo, don't tell me you became rusty at this! :laugh:
-
Along a similar line, back in college when I took a class in C, we used a book which was designed to teach C to developers who knew Pascal. "C as a Second Language" C as a second language : for native speakers of Pascal : Müldner, Tomasz : Internet Archive[^]
And so the wheel turns... :-D
-
[Introduction - Rust for C#/.NET Developers](https://microsoft.github.io/rust-for-dotnet-devs/latest/)[^]: This is a (non-comprehensive) guide for C# and .NET developers that are completely new to the Rust programming language. Some concepts and constructs translate fairly well between C#/.NET and Rust, but which may be expressed differently, whereas others are a radical departure, like memory management. This guide provides a brief comparison and mapping of those constructs and concepts with concise examples.
Now you have no excuse not to learn Rust!
I always thought metal and water creates rust, seems I missed something if you have to learn it. I will have to follow suit and start learning then... :laugh:
-
Thanks ... The idea of both languages side-by-side makes it very interesting for learning :thumbsup:, and Rust Playground makes it even more interesting :)
peterkmx wrote:
and Rust Playground makes it even more interesting
[Rust Explorer](https://www.rustexplorer.com/b) is better. Richer intellisesnse and inline compiler errors. It also keeps a history even if not logged in. Though not always operational. Not working right now. Code runs but no intellisense. :(
Kevin
-
But a long way from 1.0. Having said that, a while back I saw a post from someone who's used both and he feels there could be room for both.
Kevin
-
Along a similar line, back in college when I took a class in C, we used a book which was designed to teach C to developers who knew Pascal. "C as a Second Language" C as a second language : for native speakers of Pascal : Müldner, Tomasz : Internet Archive[^]
PIEBALDconsult wrote:
we used a book which was designed to teach C to developers who knew Pasca
When I took a C course way back before becoming a dev they actually started with a bit of Pascal before moving to C. But I never used C very much commercially. Started with C++.
Kevin
-
They have [Take your first steps with Rust - Training | Microsoft Learn](https://learn.microsoft.com/en-us/training/paths/rust-first-steps/) (5h 30m) And for a TLDR taster - [Rust for professionals](https://overexact.com/rust-for-professionals/).
Quote:
This is a short introduction to Rust, intended for developers that already know another language. In the examples, Rust is compared with TypeScript, JavaScript or Java, sometimes with C++ or Kotlin.
Kevin
-
peterkmx wrote:
and Rust Playground makes it even more interesting
[Rust Explorer](https://www.rustexplorer.com/b) is better. Richer intellisesnse and inline compiler errors. It also keeps a history even if not logged in. Though not always operational. Not working right now. Code runs but no intellisense. :(
Kevin
-
Thanks, good to know ... I'll keep it on the agenda :thumbsup: Lately I also installed RustRover, I will try it too, it will be a kind of multi-track learning :) ...
[Rust for professionals](https://overexact.com/rust-for-professionals/) is also worth a look just to get a quick overview of he syntax.
Quote:
This is a short introduction to Rust, intended for developers that already know another language. In the examples, Rust is compared with TypeScript, JavaScript or Java, sometimes with C++ or Kotlin.
And also bookmark [GitHub - jondot/rust-how-do-i-start: Hand curated advice and pointers for getting started with Rust](https://github.com/jondot/rust-how-do-i-start) What I found initially was that when I first read the initial concepts around ownership and borrowing they seemed straightforward enough. But it's when you start writing real code that things get scary quite quickly. :laugh: I remember being stuck for three days at one point when trying to convert a C# program to Rust. I never did solve the problem. Instead I took a different approach. I'd also say don't sweat over trying to write idiomatic Rust at the first attempt. Just get something working. So in my case when porting an application I just wanted to get the correct results. Having achieved that I then successively "Rustified" it as I started to learn more.
Kevin
-
[Rust for professionals](https://overexact.com/rust-for-professionals/) is also worth a look just to get a quick overview of he syntax.
Quote:
This is a short introduction to Rust, intended for developers that already know another language. In the examples, Rust is compared with TypeScript, JavaScript or Java, sometimes with C++ or Kotlin.
And also bookmark [GitHub - jondot/rust-how-do-i-start: Hand curated advice and pointers for getting started with Rust](https://github.com/jondot/rust-how-do-i-start) What I found initially was that when I first read the initial concepts around ownership and borrowing they seemed straightforward enough. But it's when you start writing real code that things get scary quite quickly. :laugh: I remember being stuck for three days at one point when trying to convert a C# program to Rust. I never did solve the problem. Instead I took a different approach. I'd also say don't sweat over trying to write idiomatic Rust at the first attempt. Just get something working. So in my case when porting an application I just wanted to get the correct results. Having achieved that I then successively "Rustified" it as I started to learn more.
Kevin
-
Many thanks, my backlog for multi-track learning becomes still more interesting, Wish you a good weekend ... :)
It's fun though, even when you get stuck. :laugh: Also the Chat AIs are pretty good. Though these came out well after I'd started learning. It's best to avoid them until you've reached a certain level on your own first. Then you can gain more from them.
Kevin
