3 ms·
My guess it started relatively small, and more features added over time to the feature, and they never thought changing about the XML part. Another thing is, X
by bayindirh 4y ago
My guess it started relatively small, and more features added over time to the feature, and they never thought changing about the XML part.
Another thing is, XML can be converted to objects and vice-versa relatively easily, so it is a neat serialization format in nature.
Also, parsing XML fast is a solved problem for the most part.
I have worked with relatively big XML files, and when done right, the path is not heavy, at all.
Edit: Oh, Considering this is IntelliJ and Java talks XML natively, this might also played a role in this being XML.
- hyperman1 4y agoNot complaining about the xml vs json vs yaml vs csv thing. It's more that when you choose XML, you've chosen streaming and reading it completely. There is no way to read it partially and only use the little bit needed.
- bayindirh 4y ago> ...when you choose XML, you've chosen streaming and reading it completely. That part is pretty true. I didn't use XML in a case where I didn't need to read it completely and transform to objects, yet. I'd not choose XML in these cases probably, if I ever encounter such a case.