This is a spinoff from the discussion for #177. A lot of our design principles apply to developer code as well, not just spec authors. E.g. things like JS API design and naming are more broadly useful. It may be good to annotate these principles so that in the future we can generate a version of the design principles doc targeting web developers (akin to the subset of the HTML spec aimed at web developers).
This is a spinoff from the discussion for #177. A lot of our design principles apply to developer code as well, not just spec authors. E.g. things like JS API design and naming are more broadly useful. It may be good to annotate these principles so that in the future we can generate a version of the design principles doc targeting web developers (akin to the subset of the HTML spec aimed at web developers).