bze12

Joined 7 years ago

Karma
271
Submissions
71
Member since
Mar 18
https://benedelste.in
View on Hacker News

Recent submissions

Comment · 2 months ago
I like the distinction between imperative and declarative styles, but I still use imperative chat sessions to work through what the declarative plan should look like. I feel like this approach loses that.
Comment · 2 months ago
Comment · 3 months ago
If any fly people read this, could you please add the ability to create custom_api connectors to the api? Sprites are so close to being great for arbitrary secrets proxying. Right now you have to provision everything manually
Comment · 3 months ago
I’ve been working on a project for this - https://mymachines.dev

It provisions a sprite and spins up Claude code/Codex on it for each session you create. Finishing up an iOS client for it too

Comment · 3 months ago
This is interesting. I’ve been building a project on top of sprites for the past few months, but I’ve often thought about moving off because it didn’t feel like fly was devoting enough attention to it. The changelog is sparse and their developer discord is kinda dead. So it’s good to hear they’ll be prioritizing it going forward
Comment · 3 months ago
By the harness I believe he means the entire end-user product experience, not specifically the harness code. I’ve mostly stuck with codex because their Mac app is better and I’ve gotten used to running automations through it. The more workflows they can build around this (design tools, collaboration, etc), the better chance of lock-in.

He talks about this in another recent essay https://stratechery.com/2026/anthropics-safety-superpower/

> If you own the user touchpoint, then you have meaningful lock-in, and the best way to own the user touchpoint is to be the canvas for everything they need to do. This, by extension, means that the frontier labs are on a collision course with software companies: it’s software that owns the user touchpoint, and it’s in the frontier labs’ long-term interest to not simply be a commodity input into software but to simply replace software outright.

Comment · 3 months ago
Comment · 4 months ago
Comment · 4 months ago
They've gone too far on enforcing uniformity of icons and abusing liquid glass, but I disagree that arbitrary shapes were better. All the random icon shapes looked cool in isolation, but were harder to scan at a glance. The uniform squircle is a useful constraint.

I wouldn't mind if they allowed something similar to that audio hijack icon, where you require the rounded rect as the guiding frame but are allowed to have some elements protruding out of it. But completely arbitrary shapes are too jarring imo.

Comment · 4 months ago
“Build vs buy” assumes that there are only two parties. If it’s easier to build internally, then it’s easier for a 3rd party competitor to enter the market and bid the price down. I think the "zone of viability" is real, it just narrows and shifts downward.

The author hints at this in a footnote: > It does, however, pencil out to use a different product instead. In this particular case, it’s easy: use Linear instead of Jira.

Comment · 4 months ago
I agree. I followed this article for a repo I'm working on, and I had a very hard time inferring how, specifically, they implemented "providers" and enforced import layers. A sample repo would've been nice.
Comment · 5 months ago
Isn’t this very similar to cloudflare durable objects & workflows?
Comment · 5 months ago
Comparing fixed costs to revenue? Even if it’s cumulative this seems like a disingenuous framing
Comment · 6 months ago
It mostly feels like they’re just converging on each other. The latest Claude Mac app release pushed a new UI that looks almost exactly like Codex’s.
Comment · 7 months ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton