Catch is type system complexity and that you can’t be sloppy. But C++ spends much more complexity points on incidental exceptions and gotchas than Rust spends on modelling the essential complexity right. (Granted, it is not immune from accruing incedental complexity)
Conversation
Oh, and there might be better ways of modelling the essential complexity in systems programming - see 's Kitten language for instance. But I digress. This also shows why I am bad at marketing.
1
If I was running a company and choosing a language I'd rather go with C# or F# + C than Rust. 🤷♂️
2
This Tweet is from a suspended account. Learn more
Part of the reason I'd go with C# or F# is because it *can* interface with C code better than many languages. You need libraries, C has all the libraries, and if you're using C libraries you'll inevitably sometimes need to write C code.
1
F# is a fine language too, if you need to run .NET. It helps to know C, but I definitely would not want to be writing any more of it in 2018, unless in a legacy code base or if the platform is out of reach of LLVM. Rust has a great C FFI, and can be embedded in other runtimes.
1
If you use C libraries and never need to edit them somehow....consider yourself lucky, I guess.
1
1
That’s what I’d class as ‘legacy’.
1
New libraries in Rust with a C ffi. Gradual migration after that.
1
As an individual decision, that's fine.
For a company, I think that would be a strategic mistake.
1
It does very much depend on your context. For us we don’t want to deal with the cost of memory safety bugs and security vulnerabilities.
For smaller embedded programs that are mainly stack allocated, fine, but we’re dealing with large, concurrent software with hard to track lifetimes. Rust brings lots of sanity to that.
1
You're at Mozilla? Working on Firefox Quantum?
1
Show replies