Slack's 57MB 404 page
a.slack.com
Slack's 57MB 404 page
1–10 of 84 posts
Re: Slack's 57MB 404 page
#2like it
Re: Slack's 57MB 404 page
#3Well at least it's cute.
Re: Slack's 57MB 404 page
#4And 440MB tab memory usage
Re: Slack's 57MB 404 page
#554 requests
57.54 MB / 11.83 MB transferred
There's only 11.83 MB transferred, but that doesn't excuse it.
Re: Slack's 57MB 404 page
#6Out of interest, is slack still being used as extensively as it was 4-5 years ago?
Re: Slack's 57MB 404 page
#7Is this because it is a SPA? I'm hesitant to ascribe blame but I have to confess I'm pretty bored of inexplicably heavy frontend code that takes an age to both arrive and execute. Bonkers stuff.
Re: Slack's 57MB 404 page
#8My intuition was that most of the (transferred) 11MB would be images, but no! Of course it's JavaScript bundles: https://i.imgur.com/QoM0Mz5.png
I'm guessing most of that code is used for other things on the website/landing page (SPA without bundle splitting per page), and the same stuff is loaded for every page, since the code for building that would be trivial compared to the multiple large bundles like they're shipping right now.
Which kind of makes me think, what is the smallest amount of JS one could write to 100% replicate this page? Would <1KB be enough? Bonus points if it could be implemented with CSS only, under 1KB.
Re: Slack's 57MB 404 page
#9Out of interest, is slack still being used as extensively as it was 4-5 years ago?
No. Everyone is on Teams.
Re: Slack's 57MB 404 page
#10Clearly no one stops and ask "Should we?". Which is sad.
I was just spending long weekend at place with less perfect connectivity, that is 2-3 Mbs LTE... And the 11MB would have taken quite many seconds... Not exactly good user experience.
Good to know that Slack is not company to choose for user experience and efficiency.