Haskell/Idris folks is probably the last group of users I’d personally care about, they have every piece of punctuation occupied for something highly useless for non-PL-enthusiasts.
last time i talked to the infra team they made a bot to replace kennytm. i fear if I ask them to write a rust based unikernel with a custom os to host the docs they'll actually do it
Explicitness is the fourth core value of Rust. Ironically, I don’t see that “Explicitness” is ever explicitly stated as a goal of Rust. But, given the choice between implicitness and explicitness, Rust usually chooses explicitness.
Software is partly a production problem, but it’s mainly a maintenance problem. Powerful primitives like Rust are our path to building sustainable services that don’t need human attention around the clock, and which can be expected to operate reliably over epochs measured in decades instead of weeks.
Well I didn't expect the bloody Rust Evangelism Strike Force.
bursts through conveniently placed door
NOBODY EXPECTS THE RUST EVANGELISM STRIKE FORCE! Our chief feature is safety. Safety and speed. Our two main features are safety and speed. And fearless concurrency. Three! Our three main features are safety, speed, and fearless concurrency. And a fanatical devotion to Ferris.
"We're able to replicate the structure of cows, but not their lifetimes, in C++, which makes Cows dangerous." -- https://twitter.com/hsivonen, closing his talk about integrating Rust and C++
When picking up a lentil (Result) a pigeon (?) must consider two options. If the lentil is a good one (Ok), the pigeon simply puts it into the pot (evaluates to the wrapped value). However, if the lentil happens to be a bad one (Err), the pigeon eats it, digests it (from) and finally “returns” it. Also the silhouette of a pigeon kind of resembles a questionmark.
I’m sorry to have subjected you to Java. You can stop weeping and screaming now, you’re not in the first year of your computer science course anymore. Unless you are, in which case I’m so sorry.
It can seem overwhelming when starting to learn Rust, because some of the stuff you need to be productive is more complex than in C++ (e.g. the borrow checker) so the initial curve from zero to productive is steeper, but it soon becomes second nature and then it's smooth sailing. Whereas in C++ it's easier to get started but you'll be sailing in a stormy sea with monsters (who want to segfault you) from the start, and have to spend a lot of time debugging..