wip

diff --git a/talk.txt b/talk.txt
index 5a21bbafd0d9ed153d28f934d4b4f77511f486b8..fa3aa7bfc2d024959daa21293c5f29d8928df6cc 100644 (file)
--- a/talk.txt
+++ b/talk.txt
@@ -162,6 +162,14 @@ stability.  They make a clear distinction between stable and unstable
 features, and try quite hard to avoid backward-incompatible changes to
 anything which has been declared as stable.
 
+[ slide with error message ]
+
+The Rust compiler's error messages are truly outstanding.  They are
+brief enough to be comprehensible, but contain enough information to
+know precisely what is wrong.  They even usually come with a
+suggestion from the compiler about what to do about it - suggestions
+which are right about half the time.
+
 [ process and code of conduct ]
 
 There's a mature process for evaluating and deciding on new features,
@@ -222,22 +230,18 @@ Despite these difficulties, and of course a fair few minor
 irritations, I have found programming in Rust to be both fun and very
 productive.
 
-
-
-polylingual sharp relief
-
-
-
-
-
-
-
-not
-very good either.
-
-
-
-Unlike many other modern programming language ecosystems, the Rust
-project and its community have a welcoming, cautious and mature feel.
-
-The 
+I'm a very polylingual programmer.  I think my record is 6 languages
+in the same personal project.  Some of my recent forays into Rust have
+involved switching between Rust and C++ and Perl.  This kind of thing
+throws differences between languages into sharp relief.
+
+Rust is now my language of choice for many nontrivial programs.  I'll
+probably still use Perl for small programs with a lot of string
+processing, and of course I often end up choosing a language for a
+project based on the availability of good libraries in the problem
+domain.  I don't think I would now want to start a new project in C or
+C++.
+
+If you want to know more, there's a wealth of stuff online.  The place
+to start is probably https://docs.rust-lang.org/.  And of course I'd
+be happy to help.