Preparing an internal talk for C and Java devs


#21

Why can’t you talk about ownership on itself. We need no multi threading to make this relevant, specially for C, C++ developers.

Well that was my plan initially, but the coworker who asked my the talk (lead dev for the team doing C and C++) specifically asked me to talk about concurrency.


#22

Ah there are some good links in there, thanks!


#23

To argue against Python, I’ve found Rust to significantly increase readability due to the explicitness. There’s never a question as to whether a corner case was handled or silently ignored, what input argument types are supported in what positions, what the output argument is, or whether the script will simply break at any point (many Python applications packaged on Linux distributions are broken in some way or another, and this can only be detected by actually running the script and testing each of its features – needs many integration tests).

I do have an example of a rewrite of a Python application that turned out to be more readable in Rust:


#24

So I’ve finally settled on some slides. I’ll focus on memory safety and concurrency but I do want to say a word about tooling so there’s one slide for that. Note that some slides contain invalid rust code (using Vec instead of Vec<T> for instance, or let x instead of let mut x) because I wanted to remove as much noise as possible from the examples where I introduce ownership and borrowing.

Here are the slides, if anyone is interested or has feedback https://github.com/little-dude/rust-talk

Thank you everybody :slight_smile:


#25

I think I know what kind of developers you deal with :wink:

Rust has an amazing multi threaded ecosystem. In the case you are cpu bound and you use parallelism to speed processes you should talk about rayon. It follows Intel’s cilck philosophy and is just amazing.

In case you are IO bound and you use multi threading to hide latencies and improve response time, have a look to futures and tokio. This is absolute alien for a C developer as there is nothing close to a future at this level. They need to understand that you are getting a very high level abstraction and paying close to nothing for having it.

I hope you enjoy the research you are doing, don’t forget to share the outcome!
Cheers


#26

Yeah, I’m using Tokio in a bunch of projects and found it pretty amazing although quite hard to approach!

I did learn a lot while preparing this talk!

Sure thing! Thank you!


#27

Alright, I did the talk, and it went pretty well! Thank you everyone! :slight_smile:


#28

Cool! Glad that it went well!

For travelers from the future, who will likely be preparing their own talks, can you share a bit about the feedback you got? What kind of questions? Which themes resonated well? (Constructive) criticism the language received? Those kinds of things :grin: