> tightening the schema only works when you can adequately define the requirements of both ends up front There are degrees of tightening though, aren't there?

> tightening the schema only works when you can adequately define the requirements of both ends up front There are degrees of tightening though, aren't there? It would be a matter of necessity (to me, at least) that an interface like he describes be extensible. To me, it's about better OS primitives with more guarantees, etc. Versioned APIs with options to fallback to older versions (to at least some extent) seems like an obvious outcome. The last thing anyone would want would be the equivalent of JSON in a database column, which would completely defeat the purpose.