Totally agree with this, not to mention that chat apps are some of the most boring, uninteresting, and braindead "problems" to solve and they have been basically completely "solved" over and over again since bulletin boards.

It's different with Google products. Every new iteration of Hangouts/Chat (or whatever it's called this week) is a bit more "unsolved" than what they're killing to introduce it.

It's less boring when your tools are getting shittier over time.

And yet Atlassian managed to not solve it with HipChat and not solve it again with Stride.

What does that tell about Atlassian?

Atlassian is weird in that they seem to have vacuumed up the entire market but all of their products are (AFAIK and experienced) objectively shitty and have negative demand.

They're rich enough to try twice?

I only vaguely remember Stride but I don't think it amounted to much more than a rebranding of HipChat.

A zulip clone written in end to end rust sounds interesting, with reasonable allowances for non-rust code on android/iOS. So maybe just end to end swift would also be fine.

But instead, probably instead we're going to get something like kernels written in electron forced onto us by our IT departments out of nowhere just because it's included in our Microsoft or Atlassian plan at no additional cost.

I remember at a previous company there were discussions on what to go with (HipChat/Stride had just been killed by Atlassian) and Zulip seemed to be the best free solution. But ultimately we went with Slack.

>> Slack is based on IRC

> Not true any more, maybe in ancient history.

I see that comparison more in the conceptual sense, rather than using the actual IRC protocol.

The word "enterprise" is notable in its absence in the article. Framing your problem as "enterprise xxx" would evoke Teams and HipChat, not improved Slack.