261–270 of 349 posts
Earlier quoted context omitted.
Yes, for a company the size of Google, a two year old product is effectively brand new. It is not ironic whatsoever that much smaller startups in much more precarious positions relative to the incumbent move very quickly to integrate with the incumbent.
Google Wave was launched, marketed, and killed in 2 years
Yes I understand sometimes something is better than nothing but teams is _so_ bad it causes user communities to fracture when they would previously congregate on the same platform.
Sure if deployed correctly and not by ape sysadmins with a thump of "deny everything in terms of security" I'm sure teams is a reasonable product, but in the real world, no, it's a nightmare.
Google should build slack. Its a travesty how incredibly good their google workspace suite of tools is, and then google chat is what sits between it all. If it wasn't for the fact that google bungled an internal communication tool so badly, slack wouldn't even have to exist. For the life of me I cannot understand why they after a decade, has let slack and teams become basically a duopoly in this space. Source: I use…
Google Chat is definitely a product that could use more love, but it is situated in a specific internal landscape, and grows out of it. Slack is built for a very different context, and I doubt Google would build something like that. Google simply doesn't see the world the way someone who likes Slack would (and I also doubt a large co like Google could operate out of Slack).
Earlier quoted context omitted.
But it's so unreasonably slow. It lacks basic features like syntax highlighting on ``` blocks. It's basically become a super expensive and painful to use while Discord continues to be a joy. And the 'start a thread' nazis are just too much to bear. Prediction: they will add subthreads within 3 years.
Use threads, bozo, stop polluting feeds.
Earlier quoted context omitted.
What issues do you have with teams? It works well and there’s nothing I can think of that I want in it. It’s just a video and chat app.
It's by and large the slowest, jankiest, laggiest software I use regularly. And I say that as someone who swears Adobe has added a bunch of sleeps in Lightroom. On basic chat: it will sometimes scroll up when I get a new message, while I'm actively participating in that chat, so I need to scroll back down to read the new messages. Occasionally it flickers, for bonus points. It will not mark the chat as read if I'm on…
Like mate - I'm on Mac, I use CMD+n for new tabs, not windows-like shortcuts...
Google should build slack. Its a travesty how incredibly good their google workspace suite of tools is, and then google chat is what sits between it all. If it wasn't for the fact that google bungled an internal communication tool so badly, slack wouldn't even have to exist. For the life of me I cannot understand why they after a decade, has let slack and teams become basically a duopoly in this space. Source: I use…
Good is really good at engineering great software and really sucks at making them enterprise ready. It's why they've been failing with GCP, Google Tables (shutdown now I guess), Analytics or any product that aims for enterprise consumption. Note: they are really good at making consumer softwares though (take the success of Google Photos or Gsearch)
If Google had stuck with Wave, and applied proper product management to it to refine the design feature set, it would be Slack+Notion today and I'd enthusiastically be using it.
Google Chat in the early years worked with Jabber clients. Maybe with Wave they changed the protocol? That killed any interest in Google's chat technologies for me.
Still haven't ever used Slack. My office uses Teams now. It works but it's pretty unpleasant. Gets the basic task done I guess.
> Microsoft did, and Teams is by all reports a solid success. Not sure if the author has used Teams. But otherwise, I agree we need an actual good, adorable Slack clone. I thought Google might do this after not buying Slack, but I'm not hearing anything about their solution.
Teams is definitely a solid success. It is by no means a good app. Those two things aren't the same. Slack started with an aggressive "bottom up" approach, they made something actually good and got to worrying about the sales part later. You don't need sales as much when companies come to you, begging you for an actual contract that fulfills their enterprise requirements, knowing that rooting you out is almost imposs…
> Developers routinely complain about Slack’s API costs and permissions What? What API costs is the op talking about?
Developers will always hate to ask the system owner for changes to permissions don’t think you can just fix that. If the company has enough grc red tape, integrating with slack can become almost impossible I can imagine
Earlier quoted context omitted.
a lot of knowledge lives in our slack history.
But that's chaotic chat messages, you should really have proper docs in place and standard operating procedures etc.