My 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 shi…
Slack's 57MB 404 page
71–80 of 84 posts
Re: Slack's 57MB 404 page
#72Clearly 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.
Did the product itself not give it away? ;)
Re: Slack's 57MB 404 page
#73Since nobody's mentioned this yet: this must be a left-over from or tribute to Glitch ( https://en.wikipedia.org/wiki/Glitch_(video_game) ) the video game project that Slack originally grew out of.
Re: Slack's 57MB 404 page
#74This isn't about being performative. This is about having fun. Blame a thousand Web 2.0 companies from yesteryear or blame Google for their legacy of little jokey easter eggs. This has a nod to Slack's history and some devs got to blow off some steam and have some fun. Would it be better if they crammed the animation into 1kb? Sure, but this isn't a demoscene comp. And perhaps Marketing gets a positive bump for it when someone shares it saying this is cool (or conversely threads like this).
This is about having some fun. It's part of our internet roots and culture.
Re: Slack's 57MB 404 page
#75My 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 shi…
But there are interactive chickens if you wait long enough.
Re: Slack's 57MB 404 page
#76Slack is a constant garbage fire where clearly all the devs have a fast desktop and don’t care about performance or battery use in the slightest. I wish my org would move away from this junk.
My org hasn't moved away but I use localslackirc to connect via my preferred IRC client. I get perks like not seeing reaction emojis, gifs, and being able to mute the constant flow of @channel notifications by configuring a list of people or channels from which I am not interested in getting these generic notifications. Also most importantly, since my company recently shifted from treating us like adults to telling u…
Re: Slack's 57MB 404 page
#77Slack is a constant garbage fire where clearly all the devs have a fast desktop and don’t care about performance or battery use in the slightest. I wish my org would move away from this junk.
Same with how much space the entire thing wastes: it's clearly designed by people with 8K 30" monitors and perfect vision.
I have many more gripes, but that would be too off-topic. I don't understand how it got so popular.
Re: Slack's 57MB 404 page
#786.5MB compressed, and will be cached. Shrug
Re: Slack's 57MB 404 page
#79Slack is a constant garbage fire where clearly all the devs have a fast desktop and don’t care about performance or battery use in the slightest. I wish my org would move away from this junk.
It's always been like this as well. Back when Slack first started gaining prominence ten years ago it was the only webapp that made my laptop's fan spin loudly. We actually migrated to HipChat because of that. Same with how much space the entire thing wastes: it's clearly designed by people with 8K 30" monitors and perfect vision. I have many more gripes, but that would be too off-topic. I don't understand how it got…
Re: Slack's 57MB 404 page
#80My 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 shi…
But there are interactive chickens if you wait long enough.
Wow, that phrase triggered a tune burried deep in my brain I hadn’t heard in 20 years.
Brains are weird