David Crawshaw note/article on exe.dev’s open-source stance
crisp founder-level framing for where startups should draw the open/closed boundary
What it is: David Crawshaw note/article on exe.dev’s open-source stance
Gist: strong pro-open-source bias, but keeps bespoke infra pieces closed because making them usable/supportable externally would cost ~25% of eng time; code that runs in the user’s VM (agent/Shelley) is open source under a permissive license with CLA
Newsletter angle: “open source the user-facing plane, keep bespoke internal substrate closed when support burden dominates”