Re: What I've Learned About Rust: 7/2/2025 7pm Eastern Standard time
Sarah Newman <[email protected]> Wed, 2 Jul 2025 06:18:58 -0700
| Newsgroups | gmane.org.user-groups.linux.svlug |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============0092894752==
Content-Type: multipart/alternative;
boundary="------------EiT0FTCo0Nj0E3qWKulI60XF"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------EiT0FTCo0Nj0E3qWKulI60XF
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
On 7/2/25 00:14, Steve Litt wrote:
> You need to try really hard to write insecure code in Rust.
I would say there are plenty of opportunities to write insecure code in rust running on Linux if you don't know how Linux (or a lot of other
components) work too.
> Once compiled, it runs fairly
> fast. It's the second of two languages (other one is C) allowed to
> be used in the Linux kernel.
>
> Like all safety first languages (Ada for instance), the compiler gets
> in your way a lot, and when you're at my stage it's frustrating. But
> it's nice that nobody's going to buffer-overrun my Rust code. And that
> compiler that frustrates you: It also has very good error messages with
> rustc links to get you the right info to guide you.
>
> From what I hear, there are few Rust jobs and even fewer rust
> development competitors, so salaries are good and getting better every
> year.
My employer is hiring. Rust would help but it's not sufficient, and it's not clear what the long term plans for rust are.
> I couldn't get a Rust expert to give this talk so I did the next best
> thing: I'm learning Rust myself and will give a presentation on what
> I've learned so far:
>
> * Rust Terminology
> * Rust Mindset
> * Hello World
> * Hello World using Cargo
> * File reading program with error handling
> * String length comparison program
> * OOP in Rust
I know people I would consider experts, but I don't know if they're interesting in giving a presentation or not. What would you like to hear about?
> You won't learn enough Rust in this 90 to 120 minute presentation to go
> out and get a Rust job, but you WILL learn:
>
> * Whether you want to learn Rust
From my perspective, I'd recommend using it for production quality systems programming if someone isn't already an expert in C/C++ or doesn't have
strong guard rails for C/C++ in place. I think you really need both.
> * Enough material to learn via ChatGPT and web searches
> * Enough to get along on the ##rust IRC channel if you're careful233
> * Terminology that once you can really code rust, you'll interview
> credibly
> * Enough to network credibly
> * Enough to detect a know nothing walking acronym dispenser (WAD)
Have you spent any time looking at efforts to rewrite core Linux userspace components in rust?
> I hope to see you there.
Thanks for presenting! I would attend but I'll be with family.
--Sarah
--------------EiT0FTCo0Nj0E3qWKulI60XF
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 7/2/25 00:14, Steve Litt wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20250702031440.796a4803-s1DAj2AW31EXSucajVqtjwC/[email protected]">
<pre class="moz-quote-pre" wrap="">You need to try really hard to write insecure code in Rust. </pre>
</blockquote>
<p>I would say there are plenty of opportunities to write insecure
code in rust running on Linux if you don't know how Linux (or a
lot of other components) work too.</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:20250702031440.796a4803-s1DAj2AW31EXSucajVqtjwC/[email protected]">
<pre class="moz-quote-pre" wrap="">Once compiled, it runs fairly
fast. It's the second of two languages (other one is C) allowed to
be used in the Linux kernel.
Like all safety first languages (Ada for instance), the compiler gets
in your way a lot, and when you're at my stage it's frustrating. But
it's nice that nobody's going to buffer-overrun my Rust code. And that
compiler that frustrates you: It also has very good error messages with
rustc links to get you the right info to guide you.
>From what I hear, there are few Rust jobs and even fewer rust
development competitors, so salaries are good and getting better every
year.</pre>
</blockquote>
<div class="moz-cite-prefix">My employer is hiring. Rust would help
but it's not sufficient, and it's not clear what the long term
plans for rust are.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<p></p>
<p><span style="white-space: pre-wrap">
</span></p>
<blockquote type="cite"
cite="mid:20250702031440.796a4803-s1DAj2AW31EXSucajVqtjwC/[email protected]">
<pre class="moz-quote-pre" wrap="">I couldn't get a Rust expert to give this talk so I did the next best
thing: I'm learning Rust myself and will give a presentation on what
I've learned so far:
* Rust Terminology
* Rust Mindset
* Hello World
* Hello World using Cargo
* File reading program with error handling
* String length comparison program
* OOP in Rust</pre>
</blockquote>
<p>I know people I would consider experts, but I don't know if
they're interesting in giving a presentation or not. What would
you like to hear about?<span style="white-space: pre-wrap">
</span></p>
<blockquote type="cite"
cite="mid:20250702031440.796a4803-s1DAj2AW31EXSucajVqtjwC/[email protected]">
<pre class="moz-quote-pre" wrap="">You won't learn enough Rust in this 90 to 120 minute presentation to go
out and get a Rust job, but you WILL learn:
* Whether you want to learn Rust</pre>
</blockquote>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">From my perspective, I'd recommend
using it for production quality systems programming if someone
isn't already an expert in C/C++ or doesn't have strong guard
rails for C/C++ in place. I think you really need both.<br>
</div>
<blockquote type="cite"
cite="mid:20250702031440.796a4803-s1DAj2AW31EXSucajVqtjwC/[email protected]">
<pre class="moz-quote-pre" wrap="">
* Enough material to learn via ChatGPT and web searches
* Enough to get along on the ##rust IRC channel if you're careful233
* Terminology that once you can really code rust, you'll interview
credibly
* Enough to network credibly
* Enough to detect a know nothing walking acronym dispenser (WAD)</pre>
</blockquote>
<p>Have you spent any time looking at efforts to rewrite core Linux
userspace components in rust?<span style="white-space: pre-wrap">
</span></p>
<blockquote type="cite"
cite="mid:20250702031440.796a4803-s1DAj2AW31EXSucajVqtjwC/[email protected]">
<pre class="moz-quote-pre" wrap="">I hope to see you there.</pre>
</blockquote>
<p>Thanks for presenting! I would attend but I'll be with family.<br>
</p>
<p><br>
</p>
--Sarah<br>
</body>
</html>
--------------EiT0FTCo0Nj0E3qWKulI60XF--
--===============0092894752==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
svlug mailing list
[email protected]
http://lists.svlug.org/lists/listinfo/svlug
--===============0092894752==--