4 ms·
Making your tool less compatible with the rest of the ecosystem at large not only makes it harder to move to your tool, but also harder to move away from your t
by embedding-shape 2mo ago
Making your tool less compatible with the rest of the ecosystem at large not only makes it harder to move to your tool, but also harder to move away from your tool. Given these AI labs basically have no moat, seems they're trying to hold on to every little piece they can do make it harder to move away, even if it's a really tiny and marginal feature, like specifically titled file on disk... Kind of embarrassing overall, but I guess they make so much money no people there have any shame left to feel.
- xienze 2mo ago> Making your tool less compatible with the rest of the ecosystem at large not only makes it harder to move to your tool, but also harder to move away from your tool. That's true but this is really not something that's a barrier to switching, just an annoyance for users. All it takes is a rename/symlink/reference whatever from the user's perspective. If it required a lot of rearchitecting on Anthropic's side or it was a _lot_ harder for users to adapt to I'd understand them standing their ground on this issue. But neither of those are true, it's just pettiness.
- embedding-shape 2mo agoDepends on how you use these harnesses, I don't interact with any of them directly for example, but have my own harness around them, mostly so I can collect all the different ones under one "roof". With that, comes certain expectations of where things live. Anything that has "CC uses file path X" for example would require refactoring/changes, compared to other agents. Contrived example, but sometimes it's more than just "mv AGENTS.md CLAUDE.md".
- OJFord 2mo agoIt's not a moat, or much of a barrier because you can literally just rename it, but it is 'good' marketing/branding. People talking about CLAUDE.md is much better for Anthropic than people talking about AGENTS.md.