Hacker News Reader

Comment by cauterized | Hacker News Reader

Asana is painfully slow in Firefox. It's not nearly as bad in other browsers in my experience. FF's JavaScript engine still leaves a lot to be desired.

View on HN

If you read the comment section on the original site they're saying that their devs use Chrome so Asana ends being more optimized for it.

Which is a good reason but a poor excuse.

Yet even in chrome, the slowness of Asana is just too painful for me to use.

I don't know what Chrome they are using, but if I get Asana email to my inbox, I don't want to click it because I know the whole experience is slow slow slow and annoying.

I'm using Chrome too.

I am not having issues of optimisation, even the front page takes like ten minutes to load; "loading unicorns...". I seriously do not know what kind of JS they write. But I remember reading a post by a front end dev which said the following:

"I went to interview for a front end position at a big company and in the interview, I wrote a very optimum JS code for something and I got laughed at, the interviewer saying in this era of 64GB rams and stuff why do you need to bother about optimising JS"

sorry, can't find the source.

Of course. Your engineers have workstations with 64GB of RAM. So obviously none of your customers are using your software on tablets or chromebooks or the 8-year-old hand-me-down vista-era PC that the IT department decided was all they could spare.

And of course your software is the only thing they have to use that computer for, so it's perfectly fine to consume every last scrap of resources it has.

I miss the 2004-era web, where the most resource-consuming webpage was the one where some idiot posted a dozen thumbnail-size images but forgot to actually thumbnail his camera's enormous 2MP images.

Reply on news.ycombinator.com