It's not the network that's the bottleneck, but the Javascript-bloated mess of the frontend.

edit: That isn't to say that Jira and Confluence are the only offenders. They aren't even the worst. Slack/Teams/Rocket.Chat are all just as bad and make me consider switching to a career without computers on a regular basis.

That’s kind of my point; all the tech you list here doesn’t have horrible lag, and aren’t generally even close to so bad they’d make someone want to switch careers.

So if it’s not them…

That’s kind of my point; all the tech you list here doesn’t have horrible lag, and aren’t generally even close to so bad they’d make someone want to switch careers. So if it’s not them…

That's a lot of denial. Have you considered that Atlassian knows that these are Fortune 100 companies with contracts that would make Larry Ellison weep and therefore slap them on their biggest instances because hardware cost is negligible (as well as having dedicated employees to fix specific problems for them), and that _maybe_ the same amount of work isn't done for <generic company paying default prices for Jira Cloud>

Maybe!

But I doubt it. I run engineering at a b2b SaaS and specifically dedicating resources the way you're describing is not something I'd consider at the level Atlassian is at, especially considering there are people like you lurking out there.

Maybe! But I doubt it. I run engineering at a b2b SaaS and specifically dedicating resources the way you're describing is not something I'd consider at the level Atlassian is at, especially considering there are people like you lurking out there.