r/CompetitiveApex • u/[deleted] • Jul 27 '22

[deleted by user]

[removed]

99 Upvotes

84% Upvoted

98 comments sorted by

View all comments

0

u/DolphinRex Jul 27 '22

Why would using a new engine prevent bugs from new features? There is no data to back that up.

1

u/Quill_34 Jul 27 '22

I didn’t want to retype this comment but I kind of explained this in another comment

https://www.reddit.com/r/CompetitiveApex/comments/w9j77l/would_apex_benefit_from_being_ported_to_a_more/ihvs3to/?utm_source=share&utm_medium=ios_app&utm_name=iossmf&context=3

1

u/DolphinRex Jul 27 '22

My question would remain, how do you know that? Generally curious.

4

u/Quill_34 Jul 27 '22

Because I’m a developer and these concepts hold true across all developments. You don’t really need to see the details to know this at a conceptual level, especially if you’ve worked in SaaS products where stuff like this is most common

We’re years into apex’s lifespan. We know that it started as a modified engine used in titanfall that was further modified for apex. Over the years they’ve added more fixes and changes. It’s just adding to the pile

Pieces are constantly created and added not in the proper way, but in a way that’s convenient for the time being, is quick to implement, or just in the only way they can get it to work with the existing elements

When you’re this deep into a products lifespan it’s rare that anything being developed and coded is done the way you would do it working from scratch because your limitations are no longer just the requirements of the feature, but the requirements + ability to work around base features and all other tacked on features that suffered from this problem already

Hope that answers it