Add Rust guide for TypeScript Programmers (closes #9)

[Hristos Nenkov (ChrisX101010)]

Adds a new typescript-book/ mdbook with 24 chapters covering Rust for TypeScript developers, with side-by-side comparisons, exercises, and a capstone REST API project.
Closes #9

[Hristos Nenkov (ChrisX101010)]

Hristos Nenkov (@ChrisX101010) please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree

[atulkhare4096]

Looks very good, but I very limited experience in JavaScript. Let me see if I can enroll someone else to take a look at the content.

[atulkhare4096]

Hristos Nenkov (@ChrisX101010) Thank you so much for the Typescript PR. Having thought about it, as with the other suggestion for Java, the lack maintainer expertise in the language is going to be a bottleneck.

As such, my suggestion would be to fork the repo and maintain the Typescript book in it.

[atulkhare4096]

Nice work, but please consider maintaining on a work.

[Lex Nwimue P. (lexNwimue)]

atulkhare4096 it would be great to reopen this, because TypeScript is a very popular language, and Hristos Nenkov (@ChrisX101010) work looked really great. Coming from a TS background, I can find it helpful already, and I'm sure alot of persons would agree

[atulkhare4096]

Lex Nwimue P. (@lexNwimue) I am not doubting the utility, but my ability to maintain it. Basically, I have a limited understanding of JavaScript, whereas I can claim varying degrees of proficiency in the other languages.

Perhaps a middle-of-the road approach is to include a pointer in the README to self-maintained versions that are outside the scope? Hristos Nenkov (@ChrisX101010) How does that sound?

[Lex Nwimue P. (lexNwimue)]

That's a good middle ground. I think you should consider it Hristos Nenkov (@ChrisX101010)

[atulkhare4096]

Hristos Nenkov (@ChrisX101010) There's a thread in under Discussions to track notable forks, so if you do end up creating one, please add it there: #34

[Hristos Nenkov (ChrisX101010)]

Lex Nwimue P. (@lexNwimue) I am not doubting the utility, but my ability to maintain it. Basically, I have a limited understanding of JavaScript, whereas I can claim varying degrees of proficiency in the other languages.

Perhaps a middle-of-the road approach is to include a pointer in the README to self-maintained versions that are outside the scope? Hristos Nenkov (@ChrisX101010) How does that sound?

Sounds awesome! Will update the README file once I got everything sorted out. Thank you!

[atulkhare4096]

Great -- once you are done, please add a note the "Notable forks" thread here: #34. It looks like there's already another request for JS/TS material :).