Email or username:

Password:

Forgot your password?
dmitriid

The amazing engineering of Jira

It re-loads 15 MB of Javascript every time you open a ticket. It loads the same scripts again and again (yes, including a full copy of jQuery).

Even though these scripts are likely cached, just the sheer incompetence is staggering

9 comments
Jon Lunman

@dmitriid And all that JS just to show you ~3kb of text.

Ben

@dmitriid you know that deep inside Atlassian there are two engineers screaming to be given leave to fix this while execs complain that it might take them a full quarter which would be better used on making metrics go up.

Ben

@dmitriid Every big company has a few experts desperately trying to plug the holes with their fingers, hoping someone will come by with something that scales better. Mostly they just get a pat on the back and a vague request that they grow some more fingers to plug some other holes.

Franz

@sangster @dmitriid but the burn down chart would just look awful!!!!1! 🫠

Григорий Клюшников

bbbbbbbbut won't someone please think of the junior developers!!!!!

rfnix

@dmitriid I just went back to office from holidays a few days ago and my colleagues were like "hey, you know how JIRA got slow as heck when we were forced to switch to cloud? it got worse _again_ for no reason while you were away! oh, by the way, long time no see!"

Nick F

@dmitriid I'm no fan of Jira, but to be fair to them a lot of these scripts look like they are coming from browser extensions.

If you try this again in a private window (ie. without extensions), do you see the same thing?

no brain no pain

@dmitriid Atlassian is preparing the next billing concept: By traffic… 🤓

schrotie

@dmitriid Caching may help with not having to reload those 15MB via the network. But still the browser has to parse some of that JS, possibly quite some. And even "just" a few MB of code to parse unnecessarily is utterly irresponsible. A waste of user time and a waste of energy.

Go Up