I guess the idea is was that Firedancer is designed with fixed update rate in mind. And the demo makes an assumption that it will run at 60 FPS = 60 updates per second, probably becoming very fast and hard on 360 Hz screens. But that's just nitpicking on details in library demo. It would be bad to have such mistake in a real game or game engine demo, but it's not that surprising for example code to skip details for the sake of simplicity. The main purpose of example is demonstrating the library as cleanly as possible without distracting reader by containing more boiler plate code for third party game engine than the thing it's attempting to demonstrate. I don't see a reason why you couldn't update FireDancer VM at whatever fixed rate you want (faster or slower than typical FPS) just like many games and game engines with fixed tick rate for physics or game logic handle it.