3 ms·
I agree with this general feeling, and it is hard to articulate Rust forces you to figure out ahead of time where each bit or byte is going to go and on which
by conradev 3y ago
I agree with this general feeling, and it is hard to articulate
Rust forces you to figure out ahead of time where each bit or byte is going to go and on which thread and using which mutation scheme. I’m happy to play the game, but it feels tedious for anything short of a parser or a microcontroller.
It messes with my process because I like to get something working before I determine the best API structure for it
I can get 90% of the performance with Swift and it flows much more easily, even though Rust’s type system is more powerful.
- Ar-Curunir 3y agoI’ve written plenty of Rust code in my life (easily more than 100kLOC, and I’ve really never worried about putting which bit where. You can just clone and be on your merry way; you don’t need to worry about perf-related things if you don’t want to.
- conradev 3y agoThose two sentences feel in contradiction of one another. You don’t need worry to about where the bits go, you just need to know to call a method to move the bits? Swift makes every type implicitly copyable on the stack, including object pointers (through ARC), so you don’t have to clone. You can even pass functions as variables without any hoops. I love lots of things about Rust, though, and will continue to use it for lots of things. Cross-platform things, for one!