Cranston's Life - Rust and More Rust

If you like BOOKS about Rust then it may interest you to know that reportedly all chapters of Rust in Action are now available!

I have not read it myself, but Rust in Action is DESCRIBED on its web site like this: "Rust in Action introduces the Rust programming language by exploring numerous systems programming concepts and techniques."

The web site says that the EXAMPLES include things like a CPU emulator, an NTP client, and handling UNIX signals!

WOW!

Those sound like PRACTICAL examples to me!

I think I SHOULD add this book to my reading list!

I have seen the Rust Lang in a nutshell: 2# Enums, pattern matching and Options article by Bartłomiej Kozielski.

It is an intro to Rust FEATURES like enums, pattern matching, and Option.

That article could be USEFUL for somebody who is stuying these features of Rust.

I have seen the question asked, What do you miss about Rust when working in other languages?

What an INTERESTING question!

The given responses on reddit are MANY and diverse.

But for me, what is it about Rust that I MISS the most when using other languages?

EVERYTHING, dare I say it!

EVERYTHING!

I miss the Rust SYNTAX.

I miss the Rust SEMANTICS.

I miss the Rust STANDARD LIBRARY.

I miss the Rust COMPILER.

I miss the Rust COMMUNITY.

I miss the Rust EVERYTHING!

Compiled software application binary size is not a CONCERN for many programmers.

When storage is measured in TERABYTES then sometimes there is the luxury of ignoring even a GIGABYTE of usage.

But that is not the world that ALL programmers live in!

Storage space can be so LIMITED for some embedded programming applications.

Great CARE must be taken to use space wisely.

Today I have seen a comparison of Rust and Nim binary sizes.

For those not in the know, Nim like Rust is an EMERGING programming language.

The Nim binary sizes are found to be SMALLER than the Rust binary sizes!

While this binary size comparison is not as SCIENTIFIC as I would like to see, it still makes me ask QUESTIONS.

What is the CODE that is being compiled?

Are these findings showing a REPRODUCIBLE phenomenon?

Are these findings showing where Rust can be IMPROVED?

Is there deeper UNDERSTANDING that we can learn from?

This is an issue that I would find to be most INTERESTING if a Rust expert weighed in!

One thing that I am most AMAZED by with Rust is how it keeps IMPROVING so quickly!

For example, the plan for Sealed Rust as described says to me that Rust is MATURING.

That article INFORMS us that Sealed Rust is this: "Sealed Rust is the effort led by Ferrous Systems GmbH to qualify the Rust Language and Compiler for use in the Safety Critical domain."

What RIGOR!

I think that this effort shows how Rust is SERIOUS.

I must FOLLOW the Sealed Rust efforts as the plan unfurls.