this post was submitted on 08 Sep 2024
1235 points (98.3% liked)

Programmer Humor

32712 readers
1439 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 181 points 3 months ago (8 children)

Some data formats are easy for humans to read but difficult for computers to efficiently parse. Others, like packed binary data, are dead simple for computers to parse but borderline impossible for a human to read.

XML bucks this trend and bravely proves that data formats do not have to be one or the other by somehow managing to be bad at both.

[–] [email protected] 52 points 3 months ago (1 children)

The thing is, it was never really intended as a storage format for plain data. It's a markup language, so you're supposed to use it for describing complex documents, like it's used in HTML for example. It was just readily available as a library in many programming languages when not much else was, so it got abused for data storage a lot.

load more comments (1 replies)
[–] [email protected] 26 points 3 months ago (2 children)

Strong competition from yaml and json on this point however

[–] [email protected] 43 points 3 months ago (4 children)

JSON not supporting comments is a human rights violation

[–] [email protected] 15 points 3 months ago (1 children)

IIRC, the original reason was to avoid people making custom parsing directives using comments. Then people did shit like "foo": "[!-- number=5 --]" instead.

load more comments (1 replies)
load more comments (3 replies)
[–] [email protected] 33 points 3 months ago (17 children)

Alright, the YAML spec is a dang mess, that I'll grant you, but it seems pretty easy for my human eyes to read and write. As for JSON -- seriously? That's probably the easiest to parse human-readable structured data format there is!

load more comments (17 replies)
load more comments (6 replies)
[–] [email protected] 144 points 3 months ago (2 children)
[–] [email protected] 19 points 3 months ago (2 children)

Disagree. I prefer XML for config files where the efficiency of disk size doesn't matter at all. Layers of XML are much easier to read than layers of Json. Json is generally better where efficiency matters.

[–] [email protected] 17 points 3 months ago (1 children)
load more comments (1 replies)
load more comments (1 replies)
load more comments (1 replies)
[–] [email protected] 90 points 3 months ago (1 children)

Wow, that's a very passive aggressive reaction. I enjoyed a lot.

[–] [email protected] 46 points 3 months ago (2 children)

This is what happens when stack overflow is used for training.

[–] [email protected] 21 points 3 months ago (1 children)

Not long before AI just tells me to google it, or read the manual.

load more comments (1 replies)
load more comments (1 replies)
[–] [email protected] 70 points 3 months ago (2 children)
[–] [email protected] 15 points 3 months ago

Except for obvious typos

load more comments (1 replies)
[–] [email protected] 70 points 3 months ago

a wate of time

[–] [email protected] 60 points 3 months ago (1 children)
[–] [email protected] 63 points 3 months ago* (last edited 3 months ago) (2 children)
[–] [email protected] 28 points 3 months ago (1 children)

Lots or file formats are just zipped XML.

I was ~~reverse engineering~~ fucking around with the LBX file format for our Brother label printer's software at work, because I wanted to generate labels programmatically, and they're zipped XML too. Terrible format, LBX, really annoying to work with. The parser in Brother P-Touch Editor is really picky too. A string is 1 character longer or shorter than the length you defined in an attribute earlier in the XML? "I've never seen this file format in my life," says P-Touch Editor.

[–] [email protected] 10 points 3 months ago* (last edited 3 months ago) (4 children)

Sounds like it’s actually using XSLT or some kind of content validation. Which to be honest sounds like a good practice.

load more comments (4 replies)
load more comments (1 replies)
[–] [email protected] 44 points 3 months ago (3 children)

I hate writing xml with a passion

[–] [email protected] 31 points 3 months ago (1 children)

If you are writing it then you are doing it wrong.

load more comments (1 replies)
load more comments (2 replies)
[–] [email protected] 38 points 3 months ago* (last edited 3 months ago) (1 children)

It’s not a waste of time… it’s a waste of space. But it does allow you to “enforce” some schema. Which, very few people use that way and so, as a data store using JSON works better.

Or… we could go back to old school records where you store structs with certain defined lengths in a file.

You know what? XML isn’t looking so bad now.

If you want to break the AI ask instead what regex you should use to parse HTML.

[–] [email protected] 11 points 3 months ago (2 children)

Had to work with a fixed string format years ago. Absolute hell.

Something like 200 variables, all encoded in fixed length strings concatenated together. The output was the same.

...and some genius before me used + instead of stringbuilders or anything dignified, so it ran about as good as lt. Dan.

load more comments (2 replies)
[–] [email protected] 33 points 3 months ago
[–] [email protected] 30 points 3 months ago

I'm starting to like this AI thing...

[–] [email protected] 26 points 3 months ago (2 children)

I'm sorry which LLM is this? What are its settings? How'd you get that out of it?

And how did it give sources?

[–] [email protected] 60 points 3 months ago (1 children)

I’m sorry which LLM is this?

It's perplexity.ai. I like it because it doesn't require an account and because it can search the internet. It's like microsoft's bing but slightly less cringe.

How’d you get that out of it?

The screenshot is fake. I used Inspect Element.

[–] [email protected] 18 points 3 months ago (2 children)

perplexity.ai

Like DuckDuckGo's AI's, but with sources? Sounds cool, thanks!

fake

Ah... Too bad (:

load more comments (2 replies)
load more comments (1 replies)
[–] [email protected] 19 points 3 months ago (2 children)

XML is good for markup. The problem is that people too often confuse "markup" and "serialization".

load more comments (2 replies)
[–] [email protected] 17 points 3 months ago

RSS/ATOM has to be the best thing to come out of XML

[–] [email protected] 16 points 3 months ago (1 children)

BASED. What is the name of this AI? I want to use this.

load more comments (1 replies)
[–] [email protected] 14 points 3 months ago

Listen we all know deep down the solution is to try to parse it with regex

[–] [email protected] 13 points 3 months ago (1 children)

stuff like this is how reddit found out their users comments were being used 😂

[–] [email protected] 12 points 3 months ago (11 children)

It is very cool, specifically as a human readable mark down / data format.

The fact that you can make anything a tag and it's going to be valid and you can nest stuff, is amazing.

But with a niche use case.

Clearly the tags waste space if you're actually saving them all the time.

Good format to compress though...

[–] [email protected] 18 points 3 months ago (1 children)

I disagree, with a passion.

It is soooo cluttered, so much useless redundant tags everywhere. Just give JSON or YAML or anything really but XML...

But to each their own i guess.

load more comments (1 replies)
load more comments (10 replies)
load more comments
view more: next ›