The problem is benchmarking on the 96 vcpu server, because at that point the author seems to miss the point of Kafka. That's just a waste of money for that performance.

And if the OP hadn't done that, someone here would complain, why couldn't the OP use a larger CPU and test if Postgres performs better? Really, there is no way the OP can win here, can they?

I'm glad the OP benchmarked on the 96 vCPU server. So now I know how well Postgres performs on a large CPU. Not very well. But if the OP had done their benchmark on a low CPU, I wouldn't have learned this.

you're missing the point. Postgres performs well on large CPU. Postgres as-used by OP does not and is a waste of money. It's great that he benchmarked for a larger CPU, that's not what people are disputing, they are disputing the ridiculous conclusion.

I remember doing 900k writes/s (non-replicated) already back on kafka 0.8 with a random physical server with an old fusionio drive (says something about how long ago this was :D).

It's a fair point that if you already have a pgsql setup, and only need a few messages here and there, then pg is fine. But yeah, the 96 vcpu setup is absurd.

I think they can be a helpful hint about how things are positioned relative to each other.

There was one this Sunday, but it wasn't even mentioned in the news.

So it has begun

Then they lose their 11 years of history

But they said their instance would be deactivated which is what I'm asking about.

Does it stay active w/ the ability to continue to use it minus the features of the paid account or is it shut down completely.

Probably worth it and possibly a great lesson for others.

Back in 2006 everything was self hosted, and chat was - everyone sharing each others AIM accounts around the room. Everything should probably go back to self hosting, including our servers.

The data and searchability is slacks main selling point. A lot of people don't get that.

I've been using slack for years, since they didn't have video chat or any of that.

There are countless chat apps, including IRC. Slack's offering is that I can find messages or files on some subject from years ago with little effort in a matter of seconds. The history is the product IMO. The free 90 day version is worthless IMO, and barely better than IRC etc.

Slack's name is supposedly derived from "Searchable Log of All Conversation and Knowledge".

> The free 90 day version is worthless IMO

I strongly disagree. The company I work at (sub-50 people) has never paid for Slack over our entire history (founded in 2009).

It's chat and it works fine. That's all it needs to be for us. We don't need to switch to IRC or one of the other countless chat apps.

We're never going to need to be indignant that Slack is suddenly asking us for more money and then rush to migrate. When they shut down the free tier, we'll take our ephemeral chat somewhere else.

I think the lesson is more to not to pay for ephemeral chat. If Slack will let you chat for free with 90 days history, don't get sucked into the paid version if you can at all avoid it.

Yeah this. Do not pay for something that is absolutely integral to your operations, when viable alternatives exist.

This is very well explained in the linked post.

Can you quote it? From what I can gather the linked post doesn't mention Zulip

Zulip no (which has its own issues from what I read) but they are migrating to mattermost:

> Anyway, we’re moving to Mattermost. This experience has taught us that owning your data is incredibly important, and if you’re a small business especially, then I’d advise you move away too.

Are you importing things from all over the internet, without pinning to a specific version? It sounds a lot like it, at least, and in that case I'm not sure how this is a flaw of Nix, or how it would be much different in other places.

To be fair, you get this all the time when you run nix-channel update, "<whatever> has been deprecated/removed, use <something-else> instead".

Nix channels (and NIX_PATH) break reproducibility. Pinning revisions makes things more robust; my preferred approach is to use default function arguments, so they're easy to override (useful when composing lots of things together).

It seems like flakes are another way to do that, but they seem way too over-complicated for my taste.

Yeah of course, but channels probably shouldn't be used outside of managing the local machine, and there's usually quite long and fair time period for deprecation warnings taking effect. Not sure how bad if one uses unstable, but if using unstable the complaint isn't really fair to begin with.

Hate it (using the Firefox one). The look is weird, seems to waste space. New copy button sucks. I spent 10 minutes one day not being able to login with a copied password, bit realising it was because I was lacking the second click. Also the new suggested results (when searching) honestly just gets in the way, since the order of the results are not always the same anymore.

You can doubt all you want, but none of us really know, so maybe you could consider interpreting people's posts a bit more generously in 2025.

No normal person has a chance against the capacity of a company like Facebook

Anyone can send 10k concurrent requests with no more than their mobile phone.