3 ms·
The part where it favorably mentioned namespaces also blew my mind. Namespaces were a constant pain point!
by mkozlows 9mo ago
The part where it favorably mentioned namespaces also blew my mind. Namespaces were a constant pain point!
- riffraff 9mo agoNamespaces are a cool idea that didn't really seem to pan out in practice.
- masklinn 9mo agoNamespaces were fun! But mostly used for over engineering formats and interacted with by idiots who do not give a toss. Shout out to every service that would break as soon as elementtree got involved. And my idiot colleagues who work on EDI.
- pjmlp 9mo agoNope, they were great. Our AOLServer like clone in 2000 used them to great effect in our widget component library.
- VerifiedReports 9mo agoI took an XML class as it neared its heyday, and even the teacher was rolling his eyes at the inclusion of namespaces. Amateur hour.
- aezart 9mo agoWe use Mulesoft where I work, and XML namespaces are a constant issue. We never managed to define an API spec in such a way that the RAML compiler and the APIKit validator would both accept the same payload. In the end we just had to turn off validations in APIkit.
- Mikhail_Edoshin 9mo agoNamespaces give you human readable GUIDs as element names. This is important. I agree their implementation and integration is a bit inconvenient.