Howdy all!
Excited to see this work moving forward and the explainer is in generally very helpful. It'd be helpful to perhaps follow the TAG's guidance on explainers in a few more detailed ways.
First, the TAG guidance explicitly suggests not having IDL in explainers. Given that a draft spec doc is in progress, perhaps that's a better place for that?
Similarly, it'd be great to see more example code to compare/contrast how folks have to do this sort of thing today and the advantages of this approach.
Lastly, seeing a fuller list of considered design alternatives (potentially with example code for each) would help observers understand the thinking that went into the API design.
Thanks again!
Howdy all!
Excited to see this work moving forward and the explainer is in generally very helpful. It'd be helpful to perhaps follow the TAG's guidance on explainers in a few more detailed ways.
First, the TAG guidance explicitly suggests not having IDL in explainers. Given that a draft spec doc is in progress, perhaps that's a better place for that?
Similarly, it'd be great to see more example code to compare/contrast how folks have to do this sort of thing today and the advantages of this approach.
Lastly, seeing a fuller list of considered design alternatives (potentially with example code for each) would help observers understand the thinking that went into the API design.
Thanks again!