When you set to work on a task and feel a sense of foreboding about it, that's intuition telling you that you're doing the wrong thing or building on the wrong foundation. Trust it!https://twitter.com/TimSweeneyEpic/status/1101519237603119104 …
-
-
And, more generally, when you move beyond C++ std / TArray style containers to a more functional style approach, you create so much garbage with such complex reference dependencies that all other memory management schemes are intractable.
-
I don't particularly understand that, because functional flows with the stack. You push questions and answers pop. Each question pushes more, smaller questions, until you get to individual CPU ops. That's very stack-modeled memory usage (if you don't resize up).
- 4 more replies
New conversation -
-
-
I think as Programmers we have to think about ownership eventually. Yes, the Rust compiler is maybe a bit too pedantic, but it forces one to think about it (and there are improvements to be made). In other languages just deferring thinking about ownership creates technical debt.
-
In Rust you are naturally steered towards a model of having data that lives separately from the systems that manipulate it. Functions that take a mutable struct (or methods using `&mut self`) are all fine and dandy.
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.