dmvinson

This is what opencode does for me. One harness for all models, standardized TUI, and they're rolling out a product to serve models via API with one bill through them

What are the new file format initiatives you're referencing here?

This solution seems clever overall, and finding a way to bolt on features of the latest-and-greatest new hotness without breaking backwards compatibility is a testament to the DataFusion team. Supporting legacy systems is crucial work, even if things need a ground-up rewrite periodically.

Lazy trees is a long awaited change for many, without it flakes are essentially unusable in monorepos. As a one-time Nix user, Flakes definitely don't seem like an ideal solution but the Nix community lets perfect be the enemy of better too often, and it has the largest following of all the solutions out there (niv being another). Given that, I hope lazy-trees and other improvements that make it actually usable get merged into Nix upstream.

If the NixOS/Nix maintainers don't like flakes/DetSys (which I think is somewhat valid!), they need to put forward a canonical way of pinning channels, otherwise there's not really an alternative standard for the community to build around. The usual answer of just use niv or some other esoteric solution that a subset of hardcore Nix users like isn't enough.

While assurances from the founders make (classically) liberal idealists all warm and fuzzy inside, they aren't worth much until there is a controversy to use this post as a measuring stick on. At that point, we'll have a more clear idea of exactly where they draw the line, which I'd be interested in knowing as a supporter of the company. Regardless, Substack seems to have high quality built in off ramps to the point where deplatforming someone from Substack won't have the same memory holing effect that it does with social media.

The best (and worst depending on which side of this future controversy I find myself on) part of Substack is the lack of switching costs. No one is staying on Substack for their barebones content editor, and retaining your own mailing list (and now custom domain!) makes firing up a Ghost newsletter easy. Their other value adds like legal support and revenue advances will most likely never be given to anyone of guilty of sufficient offense to be kicked off the platform, so that point is moot when it comes to the limits of their free speech ideals.

How did you know it was Clojurescript? Pretty awesome to see Clojure getting more use. It feels like a leap forward every time I even play with it.

Optimizing for efficient, capable teams is a difficult problem, and seemingly untenable above a certain size by nature. With that in mind, the obvious answer (especially in software) seems to be to keep teams as small as possible. Netflix's strategy is higher half the people, pay them twice as much, and give them as much autonomy as possible according to the CEO's new book. The obvious counterpoint to that strategy is it leads to overwork and will inevitably devolve above a certain size as well.

For a more radical strategy on keeping company size small, I like how the startup Stedi has taken a crack at innovating on this. Their entire tech stack is structured around AWS offerings, mainly serverless. The idea is that by paying a premium to Amazon, they can outsource all server management, scaling, etc. issues which typically take up tons of engineering bandwidth. Presumably, Amazon's round the clock experienced team will also be able to handle it more effectively than they could. In the meantime, Stedi can now avoid hiring for tons of jobs and keep headcount as small as possible, enabling engineers to only work on things that matter.

While I'm not sure how Stedi's strategy will play out, it is one of the few opinionated stances on company organizational philosophy that attempts to take advantage of recent evolution in cloud offerings, and internalize the consequences of those improvements.