this post was submitted on 28 Aug 2025
66 points (97.1% liked)

PC Gaming

12241 readers
493 users here now

For PC gaming news and discussion. PCGamingWiki

Rules:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments, within reason.
  10. Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)

founded 2 years ago
MODERATORS
EXiLExJD@lemmy.ca
UncleBadTouch@lemmy.ca
KairuByte@lemmy.dbzer0.com
66
Tim Sweeney on Unreal Engine 5 Optimization Issues: "The main cause is order of development" ["Ideally, optimization should begin early—before full content build-out."] (clawsomegamer.com)
submitted 2 weeks ago* (last edited 2 weeks ago) by alessandro@lemmy.ca to c/pcgaming@lemmy.ca
26 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] GissaMittJobb@lemmy.ml 8 points 2 weeks ago (1 children)

I mean, putting in a bit of thinking before you actually hit the keyboard can be an incredibly effective form of optimization, if you can get for example an O(n^2) down to an O(log n). You'll even save time on not having to rework the thing later, and if you build on poor foundations, chances are you'll stumble upon fundamental architectural challenges down the road, which can be extremely costly in terms of development time.

[–] Badabinski@kbin.earth 2 points 2 weeks ago

Yep, taking some care early on can pay dividends down the road. The data structures you choose really matter, and YAGNI can stop you from going overboard with indirection and other shit. Premature optimization is bad, but there's nothing wrong with writing performant software as long as it's still comprehensible and extensible.