Even though everyone has the same tools and it can clearly be seen not everyone has the same output.

The obvious downside is that resizing any string but the last requires moving everything down the stack.

With objects that never need resizing, you can of course have much simpler memory layouts.

I have both what I call inline sequences, and out-of-line ones (store an offset to the object itself rather than pointers).

I made all my sizes and offset 32-bit, but I suppose they could have been 16-bit.

On a forum, every conversation is within a thread for example.

Chat is unthreaded by default, even if Slack allows threads. It also allows users to create channels and manage who's on those groups, while the forum equivalent is fixed up-front and only opt-in.

So really chat is a forum that's a bit more free-form.

The first is what it might say on paper, the second is more honest and reflects the real business value.

This is just a sub-par harness on the most expensive tier. If you're paying thousands a month for AI surely you can rent your own EC2 instance.

I mostly use Fable though, Opus only via sub-agents.

> Comparing your capabilities to that of claude fable 5.1 would be very similar. Both are stories about a clown who is a cunning and manipulative animal. They both have problems and challenges, and they face challenges to overcome them. However, they have different goals and approaches. The clown

I think that tells you all you need to know.

There is no reason not to use the native API directly.

A VLIW ISA is a classical example of a superscalar processor without out-of-order execution.