And 440MB tab memory usage
Missed opportunity for 404mb
Tricky to slim down, but 4.04 GB should be a snap
Slack's 57MB 404 page
61–70 of 84 posts
Re: Slack's 57MB 404 page
#62Earlier quoted context omitted.
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.
No - the customer is not asking to spend additional developer time in minimizing bundles.
This is exactly the type of business acumen that is missing.
Re: Slack's 57MB 404 page
#63Not sure what's wrong here, but in Safari, cache disabled, the page size ballooned to 110 MB: https://imgur.com/a/EJja3V0
Re: Slack's 57MB 404 page
#64Clearly 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 did what my manager asked me to. Asking questions is no in my job description. I've got kids to feed".
Re: Slack's 57MB 404 page
#65Earlier quoted context omitted.
> 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.
I don't know where you've met all those programmers who are good at their job. In my experience the ones who don't care beyond the questions "does it compile? Does it pass the test suite?" outnumber the ones who ask questions like "is this even the correct approach at all?"
Mostly worked at bigger companies. Once joined a company with pretty shit colleagues/management. Left after three months.
If you have mobility, it's worth shopping around for a decent place to work.
Re: Slack's 57MB 404 page
#66Earlier quoted context omitted.
I doubt customers specifically ask to make the product really large and slow.
No - the customer is not asking to spend additional developer time in minimizing bundles. This is exactly the type of business acumen that is missing.
Is the customer asking for a product that takes 5 minutes to open? Eventually customers do move away from crap… they're just very slow.
Re: Slack's 57MB 404 page
#67It would be an interesting competition to find the biggest JavaScript payload for a single page of any Fortune 500 company.
Re: Slack's 57MB 404 page
#68I’m laughing at the idea of someone there seeing this article.
Organizes a meeting: “we look like clowns”. Technical person explains the package being big. Non technical person asks to remove, hoping for some kind of correction story. Marketing people looped in to maybe come up with a way to float this story.
Fix is evaluated for in a couple of sprints from now. A simpler html page is shipped for the sprint. Everybody high fives about one month from now for the simpler html page.
Non technical manager feels like they delivered something and the org is sluggish but they can get things done.
Re: Slack's 57MB 404 page
#69I’m laughing at the idea of someone there seeing this article. Organizes a meeting: “we look like clowns”. Technical person explains the package being big. Non technical person asks to remove, hoping for some kind of correction story. Marketing people looped in to maybe come up with a way to float this story. Fix is evaluated for in a couple of sprints from now. A simpler html page is shipped for the sprint. Everybod…
No way it happens. The business/marketing people can't stand their JS getting messed with.
There was a whole thread the other day about a framework for smuggling these huge analytics bundles through content blockers. Funny it was just around the same time another large thread was on the front page full of marketing people spazing out over the low click through rate when people are given AI summaries and aren't forced to "experience" these corporate sites running on their computers.
Re: Slack's 57MB 404 page
#70Earlier quoted context omitted.
No - the customer is not asking to spend additional developer time in minimizing bundles. This is exactly the type of business acumen that is missing.
Is the customer asking for a product that takes 5 minutes to open? Eventually customers do move away from crap… they're just very slow.
Customers of Slack don't care - and I think you are talking about the users.
This is exactly why developers need more business acumen.