A terrible, horrible, no-good, very bad day at Slack

Post by jessaustin » Tue, Jul 07, 2020, 4:53 PM UTC

whatsmyusername wrote: post #117

k__ wrote: post #85

After I used Discord in different contexts for months now (and Slack for years), I can't understand why someone willingly chooses Slack. It's the Atlassian of chat tools. Horrible performance and bad usabillity.

Because it's the Atlassian of chat tools. It's the lowest common denominator. Discord also doesn't let you set message retention that I'm aware of which is an immediate nonstarter. End up in one lawsuit where the other party demands a fishing expedition and you'll be real happy that you've got retention limited to 90 days by policy and in practice.

Post by Pxtl » Tue, Jul 07, 2020, 5:10 PM UTC

kevmo314 wrote: post #154

Pxtl wrote: post #149

Not being involved in this kind of scaled-up devops kind of stuff, my read of this article was "HAProxy sounds awful "... but they noted in the article 1) Migrating to better software, and 2) Newer versions of HAProxy are also better software. But yeah, the first half where they're discussing "we don't do X, Y, or Z clean, idempotent way of doing config because the HAProxy doesn't perform right if you do it that way.…

I don't think that's fair. HAProxy is good and reliable. It's just old for the use cases we need today. Even the article has this opinion: > While HAProxy has served us well and reliably for many years, it also has some operational sharp edges Saying it sounds awful is like saying Vanilla JS sounds awful because it doesn't scale to the demanding webapp use cases of today. And, as you mentioned, it's really compounded…

Post by devdas » Tue, Jul 07, 2020, 5:16 PM UTC

peterwwillis wrote: post #142

sudhirj wrote: post #31

This is one of the biggest arguments I see for serverless (AWS Lambda + DynamoDB) or at least managed PaaS systems (Google App Engine, Heroku with RDS or CloudSQL). These systems may seem to cost more for some workload curves (or might even be cheaper for your curve), but the difference is worth it because you're paying for specialized 24/7 dev-ops teams whose only job is to keep these systems running smoothly, and b…

Replace "serverless" with "managed service" and I agree. But serverless doesn't give you any magical reliability improvement over anything else, because your NFRs dictate the implementation that will produce the most reliable product. The design of a wooden table will inform what tools will produce the best version of that table. It may not be the newest power tool; it may end up being chisels, hand planes, winding s…

Post by carterklein13 » Tue, Jul 07, 2020, 5:24 PM UTC

k__ wrote: post #96

jrockway wrote: post #89

Earlier quoted context omitted.

As someone who uses Discord, I can tell you it goes down too. My favorite part is looking at their status page, seeing that API response time is exceedingly high, and getting no updates from the team about whether or not they're fixing it.

I'm not saying Discord is perfect or "always up", it's just that their client UI is better structured and more responsive in most cases. I am on multiple OSS Discord servers with thousands of users, and it works just fine most of the time. I am on multiple Slack servers with just 10-20 users and it is unbearably slow.

Post by phumbe » Tue, Jul 07, 2020, 5:41 PM UTC

xtracto wrote: post #99

k__ wrote: post #85

After I used Discord in different contexts for months now (and Slack for years), I can't understand why someone willingly chooses Slack. It's the Atlassian of chat tools. Horrible performance and bad usabillity.

Threaded comments. I tried using Discord with a group of 4 people for real job and we missed threaded comments. Also the ability to draw on screen while screen sharing. So simple yet so useful.