Live data from Hacker News

Slack's 57MB 404 page

a.slack.com

51–60 of 84 posts

Re: Slack's 57MB 404 page

#51
post #13

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

Yes - everyone hates teams

Teams is useless comparing to slack if you need to coordinate work indeed.

I suppose you're supposed to use the whole Microsoft "ecosystem" for what a single app can do.

Re: Slack's 57MB 404 page

#53

Looks like the biggest part is a 37MB vendor bundle, so I assume those are all the libraries they use. It's 6.5MB transferred, but compression only helps with the network part, something still parses and interprets that JS.

I'm guessing at that size (37MB!), the bottleneck becomes the initial parsing and interpretation of the JS for most clients, rather than the transferring part, which is kind of bananas when you think about it.

Re: Slack's 57MB 404 page

#54
post #26

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

Add Teams and Outlook to this pile. For some reason there isn’t a non-shitty enterprise chat software.

Yeah.. seems like a great opportunity for Discord to start a Discorp whitelabel brand. :-) Just remove all the fun/spammy/nitro features, add SSO and an SLA, and slab on a steep per-seat price.

Re: Slack's 57MB 404 page

#55
Absolutely insane. Some silly comparisons to what software has changed the world at less than 50MB:

- VisiCalc: ~27KB - i.e. the first killer app, and probably still the most successful. I wonder what DAUs on excel & google sheets compared to tiktok and insta are like...would be interesting to see.

- Wolfenstein 3D (1992): ~2MB - invented the FPS genre

- DOOM (1993): ~2.5MB (shareware), ~12MB (full)

- Quake (shareware) ~8.7 MB

- Quake (full) ~15-25 MB (excludes the CD audio)

- nginx: ~2-5MB - powers ~35% of all websites

- bash: ~1MB

- git (*nix only): ~3mb

- gcc + toolchain (ie ld, cc1, etc) ~40-45 mb

- FFmpeg: ~30-40MB

- curl: ~3MB

- OpenSSL: ~5MB

- windows 95: 50-55MB depending on features installed

- google.com circa 1998 - 10-15kb

- google.com today (anonymous session, ublock disabled) ~700kb

edit: my kingdom for markdown

Re: Slack's 57MB 404 page

#56

Absolutely insane. Some silly comparisons to what software has changed the world at less than 50MB: - VisiCalc: ~27KB - i.e. the first killer app, and probably still the most successful. I wonder what DAUs on excel & google sheets compared to tiktok and insta are like...would be interesting to see. - Wolfenstein 3D (1992): ~2MB - invented the FPS genre - DOOM (1993): ~2.5MB (shareware), ~12MB (full) - Quake (sharewar…

- The Legend of Zelda: Ocarina of Time: 32 MB

Re: Slack's 57MB 404 page

#58
post #26

Earlier quoted context omitted.

Add Teams and Outlook to this pile. For some reason there isn’t a non-shitty enterprise chat software.

Yeah.. seems like a great opportunity for Discord to start a Discorp whitelabel brand. :-) Just remove all the fun/spammy/nitro features, add SSO and an SLA, and slab on a steep per-seat price.

Imagine sitting down to work for the day, firing up Discorp, and waiting an hour for all those updates to download.

Re: Slack's 57MB 404 page

#59
post #42

Earlier quoted context omitted.

Yep, it is a SPA - but there is still a category of old grumpy devs who insist that the real web is a single hand crafted HTML file sprinkled with a bit of CSS. Yes, a 6MB (compressed) bundle is big. But it is not clear that the alternatives are better. The bundle would need to be split increasing complexity of building the application. It is likely judged that splitting the bundle only has minimal positives compared…

I assure you that 20 years ago websites with chats existed and they worked fine. Which means they weren't so huge because it would have taken days to download that amount of stuff.

Just like 40 years ago we where able to store a POSIX compatible OS on a floppy drive.

The things developers usually forget is that there are other stakeholders than the computer executing code - IMHO a lot of developers would benefit from developing a bit of business acumen.

Re: Slack's 57MB 404 page

#60
post #42

Earlier quoted context omitted.

I assure you that 20 years ago websites with chats existed and they worked fine. Which means they weren't so huge because it would have taken days to download that amount of stuff.

Just like 40 years ago we where able to store a POSIX compatible OS on a floppy drive. The things developers usually forget is that there are other stakeholders than the computer executing code - IMHO a lot of developers would benefit from developing a bit of business acumen.

I doubt customers specifically ask to make the product really large and slow.
Post reply on HN