Re:The Problem with Slack at Scale
by dvt on Tuesday May 10, 2022 @12:43AM
(#31323532)
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.
[ Parent
| on HN ]
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.
Re:The Problem with Slack at Scale
by jamesfinlayson on Tuesday May 10, 2022 @01:10AM
(#31323662)
And yet Atlassian managed to not solve it with HipChat and not solve it again with Stride.
Re:The Problem with Slack at Scale
by glotzerhotze on Tuesday May 10, 2022 @01:17AM
(#31323709)
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.
Re:The Problem with Slack at Scale
by paulryanrogers on Tuesday May 10, 2022 @08:56AM
(#31326525)
They're rich enough to try twice?
Re:The Problem with Slack at Scale
by jamesfinlayson on Tuesday May 10, 2022 @07:38PM
(#31334036)
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.