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 …
-
-
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).
-
In an eager functional programming language, it’s impossible to create cycles. Hence every function that’s called can produce a copy of its return value and free all of its intermediate values, so no manual or automatic memory management is required.
- 3 more replies
New conversation -
-
-
Whether such a move makes sense is debatable, but my thesis is that adopting a massively multithreaded and distributed programming model without sacrificing ease of use requires the mostly-functional programming style to reduce contention over shared data.
-
I don't feel I have the best grasp of all of your arguments here, but I'd be curious to hear your position on the cost of infrequent gc on framerate vs amortized freeing of memory over many frames? (assuming we're allocating / freeing at any time during gameplay)
- 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.