6 ms·
When you write Rust long enough you settle on certain architectures (message passing, event loops) that go well with the borrow checker, and don't end up thinki
by ijustlovemath 5mo ago
When you write Rust long enough you settle on certain architectures (message passing, event loops) that go well with the borrow checker, and don't end up thinking about it too much. Plus you can always throw an agent at the first set of errors from the refactor and let the compiler guide the annoying parts.
- bheadmaster 5mo ago> When you write Rust long enough you settle on certain architectures (message passing, event loops) that go well with the borrow checker So basically Go?
- flossly 5mo agoGo only provides one concurrency paradigm. Rust support many (if not all). The type system of Go is very weak. I'd say that'd be my main reason to pass on Go, even when the concurrency paradigm fits the project perfectly.
- jen20 5mo agoThe biggest reason to pass on Go right now (if your software can tolerate a runtime) is the lack of algebraic data types when doing interesting domain modeling. It makes such a huge difference it’s worth tolerating the pain points of Rust (or Swift, or F#) just to have them.
- ijustlovemath 5mo agoTraits, Enums, and Typestate allow much richer paradigms at much lower cost