Cowork: Claude Code for the rest of your work
51–60 of 593 posts
Re: Cowork: Claude Code for the rest of your work
#52It's really quite amazing that people would actually hook an AI company up to data that actually matters. I mean, we all know that they're only doing this to build a training data set to put your business out of business and capture all the value for themselves, right?
Its impossible to explain this to the business owners, giving a company this much access cant end up well. Right now, Google, Slack, Apple have a share of the data but with this Claude can get all of that.
They may still decide to use the tools, but I'd be shocked if it isn't something they are thinking about.
Re: Cowork: Claude Code for the rest of your work
#53It's so important to remember that unlike code which can be reverted - most file system and application operations cannot. There's no sandboxing snapshot in revision history, rollbacks, or anything. I expect to see many stories from parents, non-technical colleagues, and students who irreparably ruined their computer. Edit: most comments are focused on pointing out that version control & file system snapshot exists:…
There's no reason why Claude can't use git to manage the folders that it controls.
I wanted to comment more, but this new tool is Mac only for now, so there isn't much of a point.
Re: Cowork: Claude Code for the rest of your work
#54Earlier quoted context omitted.
Hi Felix! Simple suggestion: logo should be a cow and and orc to match how I originally read the product name.
OK I couldn't resist that one: https://gist.github.com/simonw/d06dec3d62dee28f2bd993eb78beb...
Re: Cowork: Claude Code for the rest of your work
#55YMMV but TFA page content body didn’t render for me until I disabled my local pihole.
Re: Cowork: Claude Code for the rest of your work
#56Re: Cowork: Claude Code for the rest of your work
#57It's so important to remember that unlike code which can be reverted - most file system and application operations cannot. There's no sandboxing snapshot in revision history, rollbacks, or anything. I expect to see many stories from parents, non-technical colleagues, and students who irreparably ruined their computer. Edit: most comments are focused on pointing out that version control & file system snapshot exists:…
Q: What would prevent them from using git style version control under the hood? User doesn’t have to understand git, Claude can use it for its own purposes.
So maybe on some apps, but "all" is a difficult thing.
Re: Cowork: Claude Code for the rest of your work
#58It's so important to remember that unlike code which can be reverted - most file system and application operations cannot. There's no sandboxing snapshot in revision history, rollbacks, or anything. I expect to see many stories from parents, non-technical colleagues, and students who irreparably ruined their computer. Edit: most comments are focused on pointing out that version control & file system snapshot exists:…
Q: What would prevent them from using git style version control under the hood? User doesn’t have to understand git, Claude can use it for its own purposes.
Re: Cowork: Claude Code for the rest of your work
#59Re: Cowork: Claude Code for the rest of your work
#60They can and most likely will release something that vaporises the thin moat you have built around their product.
This feels like the first time in tech where there are more startups/products being subsumed (agar.io style) than being created.