> The concept is called 'optimistic updating' and the intent is to make the UI 'feel faster' by assuming a positive response from the back-end, and only reverting when things go awry. Given the vast majority of messaging attempts will complete successfully, it's easy to see why the interaction pattern is used.
It's easier than making the UI and server faster for sure, I'm just not sure why engineers don't insist of fixing things the right way.
It's easier than making the UI and server faster for sure, I'm just not sure why engineers don't insist of fixing things the right way.