[evincarofautumn]

As long as the process is acceptably fast, nuking & restarting (with an appropriate amount of isolation) is a fine approach to many things that would be harder or less efficient if done the “right” way. Memory pools and “let it fail” architecture in Erlang come to mind; and there’s a practice sometimes seen in Forth, where you ensure that the codebase itself is always small enough that it can always be easily rewritten, for example if requirements change enough that incremental development would be harder.

[k__]

I do it like that on mobile too.

New screen? Okay, lets throw everything away.

As long as performance is okay, I don't keep stuff around in memory.