jsumrall
Joined 14 years ago
Joined 14 years ago
> Run <other harness> in tmux and interrogate it how feature X works, then build me the equivalent as a pi extension.
Maybe in a few years there will be obvious patterns with harnesses having built really optimal flows, but right now it works so much better to experiment and try new approaches and prompts and flows, and pi is the easiest one to tweak and make it your own.
And if there’s any feature codex has that you want, just have pi run codex in a tmux session and interrogate it how said feature works, and recreate it in pi.
In the ToS it states: >These Terms are governed by the laws of the State of California
What's changed is that I thought I was subscribing to use their API services, claude code as a service. They are now pushing it more as using only their specific CLI tool.
As a user, I am surprised, because why should it matter to them whether I open my terminal and start up using `claude code`, `opencode`, `pi`, or any other local client I want to send bits to their server.
Now, having done some work with other clients, I can kind of see the point of this change (to play devils' advocate): their subscription limits likely assume aggregate usage among all users doing X amount of coding, which when used with their own cli tool for coding works especially well with client side and service caching and tool-calls log filtering— something 3rd party clients also do to varying effectivness.
So I can imagine a reason why they might make this change, but again, I thought I was subscribing to a prepaid account where I can use their service within certain session limits, and I see no reason why the cli tool on my laptop would matter then.
When looking for alternatives to Kafka these are the most promising options I found, not counting RabbitMQ which needs no introduction.
Pulsar seems to be 'kafka done better'. The version of Kafka that Confluent used internally (Kora) seems closer to Pular as well. Pulsar has a lot of features that Kafka doesn't have, like per-message acknowledgement, similar to RabbitMQ. And it has protocol support for RabbitMQ and Kafka, so can be a drop-in replacement.
Redpanda seems like a great re-implementation of Kafka.
I'm hoping this boosts Pulsar's status and helps get some traction for StreamNative. It seems like the best technical solution for events and messaging. It just needs a bit more market adoption to make an easier choice for enterprise, in my opinion. This might be that moment.
*(yes I know about NATS)
https://docs.streamnative.io/cloud/build/kafka-clients/kafka...
I have recalled over the years this quote from his presentation: "Your app is sitting on a Ferrari-style computation engine!"