A public community forum had pan excellent discussion around an article](https://news.ycombinator.com/item?id=41043568) "types as interfaces." Commentary indicated why Protobuf and Capnproto maintainers and software makers had to strongly discourage required field usage and it is because how people do not understand strictly enforced schemas and how composite data structures work. For policy makers how they convey required should be handled very carefully and communicated to protocol and data model developers with extreme care. I do not see much of this in the current draft.
A public community forum had pan excellent discussion around an article](https://news.ycombinator.com/item?id=41043568) "types as interfaces." Commentary indicated why Protobuf and Capnproto maintainers and software makers had to strongly discourage
requiredfield usage and it is because how people do not understand strictly enforced schemas and how composite data structures work. For policy makers how they convey required should be handled very carefully and communicated to protocol and data model developers with extreme care. I do not see much of this in the current draft.