Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
I have written once a XML parser to get data from XML.....
I support this opinion.
Json > XML -
ac123511438yjson = data format
xml = full blown technology stack with specification system, transformation tools, and query language
seriously, both have their use cases -
I know in the environment I code in, xml is used because there is a whole really crazy impressive schema and parsing / generating platform built into it that allows you from a web interface to build things that are almost as feature rich as what you can build with the SDK. I thiiiiiiink xml is easier to handle in that environment too because I can query it like a database table and join it to other tables easily. But really it all just boils down to the best tool for the best job.
-
Also see flatbuffers if you would. They're amazingly fast and better than json.
-
@GurpreetSK95 Yes, but its bs to use the super fast what ever tech. JSON is mature, well supported everywhere and has no problems. Even Protobufs are more difficult to get on every platform, and whatever it is youre suggesting, if i dont know it, is has the same problem.
-
@vortexman100 yes it is difficult to understand and apply the first time, but are much faster and use very less bandwidth as compared to JSON. (I still use JSON tho)
Related Rants
Seriously? Why choose xml rather than json? json is easier to handle people!
undefined
xml
json