This certainly seems like Steam already had a bug open for startup performance, but it was always a lower priority than other things (because it wasn’t a breaking issue, and startup was still generally fine) so it was just never addressed. It may even have had a partial fix that hadn’t been shipped yet, waiting for another pass at it.
Once Epic tried to use that as an attack, they just fixed it as the low hanging fruit it was.
It was already in the Steam Client beta, improving performance of your application is just something you always look to do. It was in no way a response or anything to Epic Games.
As someone who has to wait several minutes for Office 365 and their dev environment to start at work, a 10s boot time is fine. The new speed is great, but I personally don’t mind it took this long to fix
This certainly seems like Steam already had a bug open for startup performance, but it was always a lower priority than other things (because it wasn’t a breaking issue, and startup was still generally fine) so it was just never addressed. It may even have had a partial fix that hadn’t been shipped yet, waiting for another pass at it.
Once Epic tried to use that as an attack, they just fixed it as the low hanging fruit it was.
It was already in the Steam Client beta, improving performance of your application is just something you always look to do. It was in no way a response or anything to Epic Games.
wouldn’t be surprised if all they did was defer some network traffic.
As someone who has to wait several minutes for Office 365 and their dev environment to start at work, a 10s boot time is fine. The new speed is great, but I personally don’t mind it took this long to fix