Live data from Hacker News

Slack's 57MB 404 page

a.slack.com

11–20 of 84 posts

Re: Slack's 57MB 404 page

#11

Out of interest, is slack still being used as extensively as it was 4-5 years ago?

> slack still being used as extensively

Used differently I'd say, but can't say I have a 100% view of all the users. My feeling is that various software projects moved to Discord instead (particularly FOSS which feels strange), and Slack seen an uptake in enterprise usage which makes sense considering the new(-ish) owner.

Re: Slack's 57MB 404 page

#14

Out of interest, is slack still being used as extensively as it was 4-5 years ago?

I don't know, but anecdotally, I still use it for work, but no longer for personal chats.

It also seems like someone at Slack is tasked with driving up engagement, because I get these "Your team is missing you" messages from Slack (only to be find a dead slack community). That might be a sign that they're losing traction?

Re: Slack's 57MB 404 page

#15
post #10

Clearly 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.

> Clearly no one stops and ask "Should we?". Which is sad.

I'm not sure, I've seen plenty of cases where programmers do stop and ask "Should we?" while management says "It's not ideal, but you have 4 hours allocated to shipping this things, so decide the "right" approach for achieving our OKRs" or similar.

Re: Slack's 57MB 404 page

#17
post #10

Clearly 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.

You can stop and ask that question. This quickly antagonizes the entire org - because that 57MB bundle is composed of sub-bundles owned by teams with their own incentives, and none of them are interested in doing a 404 page right - that they do not own, won't get promoted for and which doesn't show up in their KPIs.

Re: Slack's 57MB 404 page

#19

Out of interest, is slack still being used as extensively as it was 4-5 years ago?

No. Everyone is on Teams.

Which is unfortunate, but a consequence of Microsoft's perennial, embrace, extend, extinguish - they embraced instant-messaging version 3 (or wherever we are now), and they're onto the extend part - extending Teams' reach by bundling it 'for free' in Office, and the OS, so people don't "need" to buy Slack.

Slack won't be 'extinguished' but it will have a falling market share, despite the dumpster fire that is Teams, and the bean-counters in most corporations getting kudos from their bosses for 'cost savings'.

Re: Slack's 57MB 404 page

#20
post #8

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…

It reacts with the visibility state, so no JS seems impossible. [ADDED:] Besides from the obvious mouse interaction, [/ADDED] everything else should be implementable in CSS I believe.
Post reply on HN