@astola_studio_official
Yeah. Am a developer. But i think, Json is better.
@ForesteamIV
When I was defining markup, it was pretty difficult to decide where to put things: attributes or nested properties. But when done with it, it looks pretty appealing. But parsing xml is horrible. JSON is way better for that
@garybenson
XSLT was amazing!
@FireCrafter728
Thats why json is a good alternative with some libraries online
@chakibchemso
TOML >> YAML > JSON > XML
@mattcargile
You should link off to those articles.
@barefooter2222
I've done a ton of SOAP, so a lot of XML. I will say it's not the worst, but a big problem is parsing arrays. When parsing an array in XML, you have to help it along as there is no way to notate an array in XML. JSON is just better in every way
@noahisamathnerd
Pain. XML is pain.
@adrianspikes6454
I love XML ❤ for making PDFs thru Adobe SDK very easy better than json
@akvamsikrishna5535
Come up with an video on Ansible as well that tool is a Gem 💎
@smurrlawa
I have worked with xml several times and generally I don't dislike it that much. Only if you need to generate it by yourself ^^ If you just parse it it's okay and actually quite readable
@Davidlavieri
that's why SQLite is better for storing data, even config data
@aidanbrumsickle
I agree. I think something like Maven is about as readable as you're going to get with XML. And I'll take XML over something like Gradle, because I don't really like the way Gradle and other Groovy-based DSLs blur the line between declarative and imperative. I might even take XML over YAML for large config files in certain cases. If I'm on a remote server or something like that without access to a good editor with proper code folding, it's gonna be easier to find and differentiate child, sibling, and parent nodes. Especially if the YAML has 2 space indenting.
@ChilledfishStick
Could you please add links of articles that you reference, and recommend? I looked it up. This is the title and website: "XML is almost always misused - devever"
@yahira.7031
Only cool usage of this thing ive done was when building a GTK application that accepted XML for layouts
@skylo706
Fun fact for js (which has actually nothing to with xml but with json instead, though I don't know when I'm gonna find a similar video to talk about this), you can actually get a bug in js which is comparable to pointer bugs in C/C++ for example and it makes js do some undefined behaviour: So basically, if you make an object in js, be it a class instance or self made, plain object, you can't have two keys in it with the same name. JS gives you an error if you try to do this and this is great, that shouldn't happen, like ever. HOWEVER Json DOES allow same name keys in an object for whatever reason. And JS also allows these JSON objects to be loaded and parsed into JS Objects from a Json file. You won't get any errors whatsoever. So what will happen? You now have a JS object that contains a duplicate key and if you try to write to it, strange things will happen. Values in between will get overwritten or corrupted (imagine you have a field called age, the first field in the obiect, then some other fields and at position 6 you have age again). Wrong values will be written to, fields will change data types or get interpreted as a different data type, you'll get fields suddenly copying itself in name and value and so on. A glitch I've encountered myself in my job and it still amazes me to this day
@tusharyadav7067
I am just starting out as learning programming and i also see this files somehow when exploring different projects
@patyna4775
Valve uses XML (and CSS) for UI in their games since panorama update in csgo
@teamstormcloud1281
I find XML is only readable/good and better than JSON in very simple use cases. Otherwise JSON is better for longer and more complicated or complex.
@crimsondragon2677