Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

slack.engineering

Post reply on HN
Print view View original

91–100 of 282 posts

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

#91

Post by freehunter »

bmurphy1976 wrote: post #83
rorykoehler wrote: post #74

Earlier quoted context omitted.

We don't use most of the platform but the stuff we do use is rock solid (VPC, EC2, RDS, Route53, S3 etc). I do sometimes wonder what the point is for half the stuff they release. What I do know about GCP is they had a production bug in their tooling that was breaking everything for literally 100s of customers and they never even bothered replying to the bug report on their support forums. That experience along with t…

> I do sometimes wonder what the point is for half the stuff they release. I'm convinced they mvp every possible idea because it makes their platform more sticky. The more services you use, the harder it is to leave them for something better. The problem with that is you get 100 half dead zombie services and it's really hard to know which services are actually supported and which aren't. It's the Amazon equivalent of…

It almost seems to me (as an outsider) that Amazon has a policy that any tool they build internally or for a specific customer also has to be offered to the public on AWS. Like their managed satellite service or any number of things that make you say “I’ll bet some critical AWS thing was the first customer of this hyper-specific product”.

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

#92

Post by amedvednikov »

bigiain wrote: post #68
user5994461 wrote: post #49

Earlier quoted context omitted.

The way they are doing things. HAProxy is configured with a fixed amount of slots. This effectively acts as a maximum limit, so should be enough for the running instances + newer instances coming up anytime due to auto scaling. They have a tool listening to applications starting and shutting down. It's adjusting the configuration live while running to remove shut down instances (free a slot) and put in newer instance…

"640K ought to be enough for anybody!" Eventually, seemingly sane assumptions become anachronistic laughing points. (Even if they're apocryphal...)

This is not a sane assumption, and he never said it, it's a myth.

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

#93

Post by jacquesm »

tinco wrote: post #40
jacquesm wrote: post #12

Earlier quoted context omitted.

This same sort of thing tends to creep into backup systems that work for a long time without if the backups are never restored. The more reliable the systems they backup the bigger the chance that a restore will fail when you need it most. So test your backups .

Would you consider it evil to use production backups for the QA step in CI/CD? It would catch two birds with one stone, continuously verifying the backups, and ensuring the new code works on real world data. We don't have any personal information in our production database, but even if we did, as long as the QA is thoroughly prevented from interacting with the outside world, it can't hurt to use production data right…

Big risk of having your privacy sensitive information stored on other infra than the main servers a path to get that information to your QA servers should not even exist.

Many more people that should not have access to that data, in bulk or otherwise suddenly have access which does an end run around all your - hopefully - carefully crafted security.

Keep in mind that what you think isn't privacy sensitive may very well be radioactive when combined with other data.

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

#94

Post by Tyr42 »

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.

Oh no poor HipChat. (Atlassian's chat tool)

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

#95

Post by taormina »

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.

Well, Hipchat would be the literal Atlassian of chat tools.

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

#96

Post by k__ »

jrockway wrote: post #89
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.

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.

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

#97

Post by k__ »

taormina wrote: post #95
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.

Well, Hipchat would be the literal Atlassian of chat tools.

Ah yes, they have their own thing now :D

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

#98

Post by rkrzr »

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.

We have been using self-hosted Mattermost for years and I can highly recommend it. It never crashes, performance is great, and upgrading it is very easy to do.

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

#99

Post by xtracto »

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.

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

#100

Post by luisehk »

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 Discord is very gaming oriented. But yes, Discord is great.
Post reply on HN