veyepar: Introduction to Rust (for people who have never used a compiler)

Author(s):	Tim McNamara
Location	Room 9
Date	jan Thu 16	Days Raw Files
Start	13:30	First Raw Start	error-in-template
Duration	0:100:0	Offset	None
End	15:10	Last Raw End
Chapters
Total cuts_time	None min.

https://lca2020.linux.org.au/schedule/presentation/89/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Introduction_to_Rust_for_people_who_have_never_used_a_compiler.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

Rust is often described as having a difficult learning curve. Let’s find a hidden escalator. By the end of this tutorial, you’ll find building a command-line utility in Rust to be about as easy as one that’s written in Python or Ruby, and you’ll be able to distribute it as a stand alone binary.

Many of the difficulties learning Rust emerge from two sources: jargon and novel concepts. Avoiding the jargon keeps some the cognitive capacity in reserve to focus on the new concepts. Much of jargon has its roots in Rust’s functional programming heritage and early-adoption by programming language theorists. It’s possible to bypass much of that and focus on getting something working first. There’s plenty of time to learn about affine type systems and 
monomorphisation once you’ve got a working project or two.

This practical tutorial will take you through the process of writing a command-line from scratch. We’ll learn all about the essentials of the language, as well as the tooling that’s available for people who may not have worked with a compiled language before. We’ll also spend some time talking about how  to access further help when you’re working on your own.

At this stage of its life cycle, everyone who knows Rust learned something else first. That means that there are plenty of people in your position who have been able to push through and make progress.

Come and learn Rust!

Comment:

production notes