5 ms·
The Rust I used to know (2022)
- FrankWilhoit 3y agoI know, let's invent a new language that is supposed to make software transformatively more reliable -- and name it after the universal avatar of intractable decay.
- smolder 3y agoAnother way of looking at it... If you create something from iron oxide in the first place, it can't rust.
- skavi 3y ago> TL;DR: Rust is named after a fungus that is robust, distributed, and parallel. And, Graydon is a biology nerd. https://www.reddit.com/r/rust/comments/27jvdt/internet_archaeology_the_definitive_endall_source/ https://www.reddit.com/r/rust/comments/27jvdt/internet_archa...
- ogogmad 3y agoMake a pull request changing it to Stainless Steel Or Silver To be honest, these choices look witless. Show, don't tell
- ixaxaar 3y agoI think the world of programmers have spent a bit too much time trying to avoid pointers, inventing a whole bunch of different languages, mechanisms and with them a horde of other problems and useless complexities. Instead of this utter wastage, why not just use C?
- MrVandemar 3y agoBecause 'C', as fantastic as the language is, is prone to users making errors, and errors cost (sometimes incredible amounts of) money, and even peoples lives. See the Great 1990 Telephone Crash for the former. I like 'C', but I'd never get in an aircraft where a 'C' compiler was used for anything other than the in-flight entertainment system.
- LispSporks22 3y ago> I'd never get in an aircraft where a 'C' compiler was used So I take it you've never been in an airliner?
- defrost 3y agoThere's a lot of C code in avionics op systems, both new and old. There are multiple static analysis frameworks for verifying C code in aviation; Frama-C and Astrée just to name two. https://frama-c.com/html/overview.html https://frama-c.com/html/overview.html https://www.astree.ens.fr/ https://www.astree.ens.fr/ If you've ever got in an aircraft it's too late, you've almost certainly been in one using C for flight control functions.
- ixaxaar 3y agoI've worked in automotive where literally everything except the infotainment systems are in C. Almost all, if not all, firmware is in C. Also, not to mention every operating system. I really don't know where the "bugs are horrible" argument grounds itself on. I've worked on large C, rust, go, python and even Haskell codebases. Everyone of them had their share of super corner case bugs. The systems which use the simplest concepts and tools tend to have the least bugs cause they are more readable and hence fixable.
- kramerger 3y agoNot sure if this is a piece in favor or against Rust. Rob says he had so much fun with Rust, but a significant number of his projects were abandoned or are still "work in progress".
- gs17 3y ago> but a significant number of his projects were abandoned or are still "work in progress". That sounds like Rust is at worst the same as any other language people program in.
- fl0ki 3y agoHot take: It's nice that Box, Arc, etc. are all just types and nothing special to the user, but it's not as nice that modern async code in particular ends up with Arc<T>, :Send+Sync+'static, Future<Output=T>, copied absolutely everywhere and often taking up half of each function signature. As a general rule, anything that can be orthogonal should be, but also as a general rule, more syntax should only be needed for non-default cases so the default is minimal. With modern async treating these things as effectively the default, these rules end up in constant tension. C++ has the same problem and it's getting worse and worse, and I hope Rust doesn't continue down that direction.
- 3836293648 3y agoCalling C++ a strongly typed language is just objectively wrong. It's very much statically weakly typed. Static-dynamic and strong-weak are orthogonal