this post was submitted on 16 Oct 2026
816 points (98.6% liked)
memes
23077 readers
2139 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads/AI Slop
No advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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