171–180 of 264 posts
What a strange thing to post on a corporate CEO blog - proof that AI is making it too easy create things without asking why. How does it serve Fivetran to post open letter about why Slack sucks? This only happens if it's easy to write a couple bullet points and have Claude fill in the rest... If an LLM wasn't used they would have realized it wasn't worth a post during the process of writing it.
Earlier quoted context omitted.
If they sell a magic app building machine, its not crazy to ask them build an app with it, is it?
Of course it is. Making shovels and digging holes are different skills and require different organizations.
Just use one of the many chat products that doesn't have the same access limitations as Slack? Or, you know, Vibe code your own. People are so weird.
Or, you know, Vibe code your own. Right. If these tools are so good (and they are) there should be numerous better-than-Slack apps by now that let you do exactly what you want. It doesn't take Anthropic to make it. (At our company, we cheated and edited 37signals' Campfire instead because we got sick of Slack's ads pushed into our paid instance.)
That sounds crazy to me, but the other interpretation (that Campfire has ads for Slack) seems even crazier.
Why ask Anthropic? Why not build on something better like Matrix? Or Signal?[0] Or even Keybase? I really do agree we need to move away from Slack and Discord, but I'm also very confused why the call to action is to Anthropic. IMO we should really be pushing for open systems so that nobody can take it from us. Otherwise we repeat the cycle again and again. There's some good protocols to start on. I'd also say this is…
Earlier quoted context omitted.
I lead the Zulip project and I'm not aware of any common crash issues with either our server or any of our apps. Can you share details on what you're experiencing with us? https://zulip.com/help/contact-support .
Thanks for your work on Zulip! I have some feedback that's annoyingly non-specific. I used Zulip a few years ago as a contractor. It seemed _fine_, but I didn't love it. Specifically, the UI felt sluggish and generally the experience was somewhat unpolished. Maybe things have changed, a lot happens in a couple years, but there you go
Earlier quoted context omitted.
If they sell a magic app building machine, its not crazy to ask them build an app with it, is it?
Of course it is. Making shovels and digging holes are different skills and require different organizations.
Earlier quoted context omitted.
> Claude Code could absolutely build a chat client in the hands of someone who could also build the rest around it. So why can't Anthropic build a CLI client that doesn't flickr and doesn't consume 68 GB to run a CLI wrapper on top of their API? https://x.com/jarredsumner/status/2026497606575398987
That's still light years better than Slack. The thing lags a few seconds while typing a message on a 20 core 128g ram machine. That's with their desktop (electron) app. Mercifully, the web app works better. Still, CC blows it out of water. Slack is that bad.
We're a small company (about 150 Slack users), and I've run the Slack (Electron) app on a 16GB M2 (macOS) and a 4GB Chromebook (running a non-ChromeOS Linux), and it has never had any noteworthy performance issues.
It still sucks, but not because of performance.
Why ask Anthropic? Why not build on something better like Matrix? Or Signal?[0] Or even Keybase? I really do agree we need to move away from Slack and Discord, but I'm also very confused why the call to action is to Anthropic. IMO we should really be pushing for open systems so that nobody can take it from us. Otherwise we repeat the cycle again and again. There's some good protocols to start on. I'd also say this is…
Claude-in-Slack is a big enough feature to overcome the slack-connect network effect. Openness is absolutely key! I wrote this post because I hoped that if Anthropic is already planning to do this I might be able to influence them to make open-data part of the plan. But openness by itself isn't a big enough feature to get users.