I started working with Salesforce in 2015, and since then I've been told by mentors and the Salesforce community on the Internet that having multiple triggers for a single object is bad practice, mainly because the platform does not guarantee a trigger execution order. This makes absolute sense in a scenario where there is a single application being developed.
Considering a scenario where an enterprise customer wants to build different applications on their platform though, I think this recommendation doesn't make that much sense anymore. It is like having two installed AppExchange apps that have their own triggers on standard objects (like the Account).
So app A and B can have a trigger on an object, but as long as their logic are separate (logic from application A doesn't depend on logic from application B) there should be no issues. Does this make sense?