@ActionPhilip@owensd@cmuratori What on Earth are you imagining needs to be stored in RAM? This is like hundreds of bytes of data, tops. "What about run menu history?" Ok, thousands tops. Thousands. Of. Bytes. This is NOTHING.
@VAVhk@microsofterses@ClintRutkas@Niels9001 This. This. This. I have no idea how there's any room to defend MS in anyone's mind. Ignorance of what's possible maybe. https://t.co/UN7PRCE8D2
@JackHammerLane@cmuratori@Shinobu_uwu I want you to think about every single operation that has to happen to display a frame of cyberpunk 2077 and then read your tweet back to yourself.
@JackHammerLane@cmuratori@Shinobu_uwu I want you to think about every single operation that has to happen to display a frame of cyberpunk 2077 and then read your tweet back to yourself.
@JackHammerLane@cmuratori@Shinobu_uwu I want you to think about every single operation that has to happen to display a frame of cyberpunk 2077 and then read your tweet back to yourself.
@Eric_Cochran@cmuratori Yeah this stuff is known! Facebook made these extremely influential posts in like 2011 era showing that literally each millisecond of latency translated to millions of users getting impatient.
@NearestCommit@rfleury Agree with the theory. In practice there are usually some issues with having dependencies you can't control through your distribution method. You're relying on the OS guys getting it right.
@_take_hito_ It's possible to fixed-loop SwiftUI with the Timer.scheduledTimer API. Might need to DispatchQueue.main.async then restart the animation with an observed object (State vars cannot be modified outside of SwiftUI this way, but objects can. Might even work in TimelineView? Not sure)
@_take_hito_ https://t.co/58cbKijzUg works too.
Or even import https://t.co/58cbKijzUg to isolate the import.
But I didn't know about :: that is interesting. Thank you.