我为什么更喜欢 Opus 5 而不是 Fable 5
4 分•作者: novlrdotcom•13 天前
自从它们发布以来，我一直在同时试验这两者。经过 4 款游戏、3 个网站和 2 个内容创作引擎的实践——我认为我已经准备好分享我的一些经验和看法。
**我对 Fable 的观察**
1. **输入什么，输出什么**——也就是说，在我给出 Fable 初始信息和提示之前，做出所有设计决策，就能获得最佳结果。它自己做决定时更舒适——它不会告诉你它做了什么决定——除非你事先明确告诉它哪些它可以自己决定，哪些不行。
2. **它是一个黑箱**——在某种程度上，这是上面观点的延伸。我用“代理机构”来类比向人们描述它，也就是说，它会接受一个简报（Fable 自己称之为“指令”）然后独立执行，直到完成才会回来。我曾有过一个 Fable 对话独立工作了 9 个小时，为我构建了一个客户自助服务门户。我只需要在它每 5 小时达到会话限制时输入“继续”。
3. **它功能强大得令人难以置信**——所以，如果你事先通过 Opus 对话进行思考和梳理，把一切都安排妥当，你就能获得惊人的结果。它会创建自己的子代理，进行自己的测试和自我验证，然后将一个完成的产品交给你。这让我大开眼界。
**但我更喜欢 Opus 5**
为什么？因为它不是一个黑箱。
1. **它会汇报**——它似乎会在自然的阶段性节点暂停，并更新它生成的内容以及原因。它有一种节奏，让你用户能够参与其中。
2. **它同样有能力启动子代理并进行自己的测试和验证。**
3. **它的成本确实便宜得多**——例如，当 Fable 在处理一项任务时，我的 Claude Max 限额大约在 30 到 45 分钟内就会耗尽（Fable 速度很快）。但这之后我就只能无所事事了。Opus 5 的感觉在某种程度上更具条理性（这可能仅仅是因为它会返回给用户，导致节奏变慢）。或者换个说法，Opus 让开发者在整个过程中都保持参与。而且它似乎更专注于给你你想要的东西。Fable 不会这样做——它基本上只是接受简报然后自己做决定。
我只是想分享我的经验，因为我很快就达到了熟悉度，并认为这可能对其他正在试验这些前沿模型的人有价值。
期待你的想法。祝好。
查看原文
I've been experimenting with both since the moment each came out. 4 games, 3 websites and 2 content creation engines later - I think I'm ready to share a bit of my experience and opinion.<p>WHAT I'VE NOTICED ABOUT FABLE<p>1. Gold in, gold out - meaning I've had the best results by making all my design decisions before giving Fable the kickoff information and prompt. It's much more comfortable making decisions by itself - decisions it won't tell you about - unless you explicitly tell it what it can and can't decide for itself up front.<p>2. It's a black box - which is an extention of the point above in a way. I've used the analogy of an agency when I've described it to people, i.e. it'll take a brief (what Fable itself describes as "an order") and go off and run with it, only coming back once it's done. I once had a Fable conversation work independently for 9 hours buidling out a client self-service portal for me. All I had to do was type 'Continue' once it hit its session limits every 5 hours.<p>3. It's insanely powerful - so if you've got everything worked out up front by thinking and working through it with an Opus conversation, you can get the most staggering results. It creates its own sub-agents, does its own testing and self-verification, and ships you back a finished product. It blew my mind.<p>BUT I PREFER OPUS 5<p>Why? Because it's not a black box.<p>1. It reports back - it seems to pause at natural phase gates and give an update on what it produced and why. There's a rhythm to it that keeps you the user involved.<p>2. It's just as capable of spinning up sub-agents and doing its own testing and verification.<p>3. It genuinely is a lot cheaper - for example when Fable runs on a task my Claude Max limits burn out in roughly 30 to 45 minutes (Fable is FAST). But then that leaves me twiddling my thumbs. Opus 5 feels more methodical somehow (which might just be because it comes back to the user, resulting in a slower cadence). Or maybe the better way of putting it is that Opus keeps you the developer involved throughout. And it feels like it's more interested in giving you exactly what you want. Fable doesn't do that - it basically just takes the brief and does its own thing.<p>I simply wanted to share my experience as I've quickly reached the point of familiarity and thought that might be valuable to others who are experimenting with these frontier models.<p>Look forward to your thoughts. Cheers.