hey @thdxr! are you considering adding support for the Kitty clipboard protocol (OSC 5522) for pasting images over ssh? I have a remote setup I want to distribute to my team and that is a huge pain rn
hey @thdxr y built this POC to mimick CC's workflows. your SDK was enough for it to work, nice. only thing missing was UI control to show the live status, had to work around it. arrived at not ideal but usable UX
https://t.co/ifvaxq2fuF
Mind boggling to me that I can make a thing faster and there's always people that ask "but why?" What kind of mentality is that? The pursuit of excellence does not need justification. Also, I find in so many cases, we can't know the impact of an improvement until we do it.
For example, one I've talked about before: Ghostty's high IO throughput has enabled terminal program (emulator and TUI) fuzzing at a speed thats incomparably fast to prior solutions. This has resulted in upstream patches to resolve issues in popular projects like btop, tmux, and more.
Speed enabled that anecdotally example that lifted the tides of adjacent communities that don't rely on Ghostty technology at all. I didn't predict this.
Make things better because they can be better and let the results naturally play out.
I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.
I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).
It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.
The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.
We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.
I worry.
sent this to the team today
everything great comes from being able to delay gratification for as long as possible
and it feels like we're collectively losing our ability to do that
We are live in @trycommet The goal is simple. Help any founder monetize their SaaS or AI product in minutes without dealing with billing, taxes, or compliance.
⦿ Subscriptions in 2 minutes with just 5 lines of code
⦿ We act as your Merchant of Record and handle all the heavy stuff
⦿ Native SDK for @nextjs
You build. Commet handles your revenue.
@iamdavidhill@opencode idk if everyone has this problem, but I feel like I'm constantly trying other models so my "latest" section is always fucked hahaha
i know the model labs are in fierce competition and feel like they need to respond to every move by their competitors
but people are getting really tired, they're totally checked out at what codex 5 vs codex 5.1 vs codex 5.1 max xhigh is
increasingly narrow audience that cares