Oddbean new post about | logout
▲ ▼
jb55 | 4 months ago (raw) | root | parent | reply | flag +2 
 I think standards will evolve organically, the apps that want to be compatible in the ways that are important will talk and make it so. the nips repo is no longer reliable and nips are edited at will without discussion. It has become meaningless except for the core nips.
▲ ▼
mleku | 4 months ago (raw) | root | parent | reply | flag 
 and that's largely because it's not a collaborative document workflow, but a codebase workflow

and nip numbers have extremely complex, contextual relationships that are hard to follow without simply reading everything and then digging through all the PRs as well just to find out if you should put something in a field or expect something in a field or not

mostly it's a problem for client devs also, which also really reinforces my point about how while you all are busy making clients you are also gatekeeping the specs

seems like a recipe for loss of focus to me