"Teaching is a humbling and deeply educational experience, and I cannot recommend it enough!"
--Jon Gjengset.
Thank you, Jon, for giving your time, expertise, and energy to write a masterclass on Idiomatic Rust. I've always admired your knack for teaching and hope to do the same.
I just finished studying Rust for Rustaceans by @jonhoo.
After studying the Rust Book, like @dtolnay said in the preface, I noticed a knowledge gap between concepts explored in TRPL (The Rust Programming Language) Book (a.k.a., the Rust Book) and terminology in the std library and Rust Reference. I wanted to close that gap, to truly understand, because I've come to LOVE Rust. I wanted to leave no stone unturned. I found the best 2nd book after the Rust Book (goes without saying, I highly recommend).
As advised, in Chapter 13, Jon, I'll learn by teaching too. In the coming days, I'll share blog posts and hopefully hold live sessions where I debunk the myth that "Rust is too hard." Chipping at topics bit by bit.
It used to be that if you wanted to learn the inner workings of computer programming that'd tell you to learn C. Today, I'd tell you to learn Rust. Rust teaches you to appreciate the power you wield when you write, build and run a computer program. Yes, it is complex, but "complex is better than complicated." It might take some getting used to, yes, but with time and focus anyone can master the language and that's what I hope to do.
PS. Thank you @OReillyMedia for access to a plethora of golden technical resources. Thank you @timoreilly. That's two Rust books in 3 months! Grateful.
I've finished studying the Rust Book 🦀 (also known as The Rust Programming Language Book) by Carol Nichols and Steve Klabnik. Precisely, the interactive version by C.S. Brown University, (also known as the Rust Book experiment) which is available online for free via the link: https://t.co/PRps6DTSh0
Here is the story of of how @elonmusk convinced his team that Starship could be caught by the mechazilla arms of the launch pad. At first, they didn't believe him:
The people who win at building anything worthwhile aren't the ones who stayed hyped the whole time. They're the ones who built a system that kept running on the days they were exhausted, distracted, or completely uninspired
If someone invents a machine that makes food 50% cheaper and becomes a billionaire, society hasn't lost a billion dollars.
We've gained cheaper food.
The fact that someone got rich solving a problem doesn't mean the rest of us got poorer.
Wealth creation isn't theft.
In late 2020, Elon wanted to eliminate the heavy landing legs planned for Starship’s booster. He asked:
“Why don’t we try to use the tower to catch it?”
Most engineers argued against the idea. If the booster crashed into the tower, it could stop future launches for a long time. After more than an hour of debate, the team was leaning toward keeping the legs.
Elon decided to pursue the catch.
Inspired by Mr. Miyagi catching a fly in The Karate Kid, he called the arms “chopsticks” and the tower “Mechazilla.”
His reasoning was simple:
“Legs would certainly work, but the best part is no part.”
Years of engineering turned that idea into real booster catches. Today, SpaceX caught the Starship upper stage for the first time.
What began as a question in a room at Starbase became history in front of the world.
Respect to Elon and every SpaceX employee who helped make it happen.
Source: Elon Musk by Walter Isaacson.
Most people, to be honest, are not excited about this. They don’t understand the implications, nor what happens when flights accelerate.
Much media is quite hostile to SpaceX. Explosions get emphasised and achievements downplayed. So people are going to be taken off guard when the flight rate starts to pick up.
When it’s not long possible to dismiss Starship, the debate will move on to “how can one company and one man have this power? Surely it should be shared with us, the people who didn’t contribute to it and who criticised it endlessly when it was being developed?”