I was profiling an ecommerce site we're responsible for and noticed that the app.js package felt a bit big: nearly 4MB unzipped. Most of it was the standard SPA/React attendant stuff with modern development, but within it was a 180 kB SVG of an old version of the company logo that wasn't being used anywhere on the site, but which had made it into a dev and then production branch and was shipped live. The zipped version was 175 kB total, but this SVG ended up being a decent portion of that size, and we do about 6M uniques per month, so it adds up, though we're now caching through CloudFlare instead of AWS/CloudFront, so that helps.
Slack's 57MB 404 page
31–40 of 84 posts
Re: Slack's 57MB 404 page
#32Is 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.
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 to the negatives - which also align with my experiecne developing software for roughly the same target segment.
Re: Slack's 57MB 404 page
#33Re: Slack's 57MB 404 page
#34Slack 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.
Teams is far worse than Slack though, an embarrassment for a billion dollar company. Think of the collective waste of time and electricity.
Re: Slack's 57MB 404 page
#35But you can click on the chicken and it will jump. KPIs matter.
Re: Slack's 57MB 404 page
#36Earlier quoted context omitted.
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.
How would you implement that scrolling background? Particularly the mouse interaction, where it scrolls with a dynamic speed ( depending on how far to the side the mouse it) and even has some smooth damping when you stop scrolling. And what part uses the visibility state? The grayscale seems to be triggered by focus which I think would be doable with CSS
Ah, I forgot that (everything except for the interaction should be okay, though). For the visibility state however, checking for focus is insufficient because you can have elements focused without the document being visible.
Re: Slack's 57MB 404 page
#37Slack 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 us we must only work on the assigned tasks and for no reason go out of task, I configured it to not join general discussions channels where people ask for help and such things. In theory I'm on them, but from the point of view of my IRC client I'm not.
It re-joins automatically if someone mentions me specifically. Unfortunately it won't fetch the history when this happens so I might need to open the real slack to get the context before I can answer.
Anyway, it has worked mostly fine for me… I can have decent battery life and I don't get most of the useless notifications.
Re: Slack's 57MB 404 page
#38Saw this Slack 404 page years ago so not a new release.
Re: Slack's 57MB 404 page
#39Clearly 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.
Should we what?
This is an effect from no one prioritizing extra complexity that might / might not provide any tangible value.
Re: Slack's 57MB 404 page
#406.5MB compressed, and will be cached. Shrug