I didnt think I needed to reiterate what others have said. Clearly, you do not understand anything that was on DF article. I imagine you are having a hard time understanding these concepts.
Here, it clearly explains why your theories are nonsense.
Trolls belong on the ignore list. If you can't offer actual points to discuss you'll be joining him.
If you are going to reply to my posts and make assertions about their content you get to volunteer to supply some rationale and evidence to support said assertions. You can expect to be called out when you fail to do so.
I'll pretend to be unaware of your post history and banning from TXB and give you the benefit of the doubt by explaining why your assertions are nonsense. You can reply here or to the post you quoted.
First of all, the scenario I described was interactive and dynamic, just not immediate. I'm not interested in DF's assertion that only non-interactive things can be done with latency insensitive tasks. That assertion is flatly wrong, as I've explained in that post you quoted without reading. What you CANNOT do is have latency sensitive tasks, like anything that has to update every frame or even every few frames. A slow moving ship with many seconds between player interaction and the expected outcome leaves a rather long window for rich new animation data to be computed/streamed in well before the actual collision takes place.
The player can still affect the initial conditions and as such it is still interactive. The player can still do things to either trigger or prevent the collision from happening (in which case the streamed anim data stores in RAM is just ignored/cleared). In that sense it is dynamic. And yet, it's a task that's extremely insensitive to latency. There are loads of large scale physics-based events like this that can be computed when the player is within a certain range and triggered upon request (or ignored when not triggered). It's not hard to think up such scenarios.
If you disagree you can explain why. Trolling or asserting I am wrong isn't contributing to the discussion, especially a technical discussion.