Hacker News new | past | comments | ask | show | jobs | submit login

That ugly child doesn't cut it, these are the comments people want:

key1=value1 # this is a proper key1 comment, if you move a line, it stays with key1

key2=value2 # it also doesn't break the table

# and you don't need to write a config parser

# nor modify a syntax highlighter

# nor make sure other people use your comment style




If people absolutely want those, they can use TOML, which supports single line and inline comments.

Given a choice, I'd even opt XML over YAML.


That's fine, you can pick whatever XML ugliness you like, I was just pointing out that you can't solve the basic fail of JSON with comments by making them data


> I was just pointing out that you can't

No, you were pointing out that some people won't like that solution. Which is completely fine. And yes, that solution is ugly as hell, and it is a dirty hack, and I don't recommend actually doing that if there is a better way (like TOML).

But it does work.

https://www.youtube.com/watch?v=C5kGCwJ25Yc


> ugly as hell, and it is a dirty hack, and I don't recommend actually doing that

you're just paraphrasing the obvious - it's not a solution. And YAML is a better way and addresses the problem you choose to ignore as such - ugliness.


> And YAML is a better way and addresses the problem you choose to ignore

I haven't ignored it, as shown by us discussing it here.

And no, YAML isn't a better way. It does commenting better, true, and at the same time, it does so many things wrong, that are absolutely no problem in JSON, that it becomes a treatment worse than the disease.


You've argued that ugliness is a solution while the problem that needs to be solved is ugliness. You can't have it both ways, either it's a solution, then don't call it ugly as hell, or it's ugly, then not a solution (or it is but that means you ignore that ugliness is the problem)

This specific brand of cleanliness does have a bunch of issues, but that's a trade-off depending on a use case


> You've argued that ugliness is a solution

I think I speak for basically the entire history of programming when I say that ugly solutions exist and are widely used throughout our profession.

> while the problem that needs to be solved is ugliness

That's your opinion. I never argued that this hack solves ugliness. I argued that it solves the problem of not having a way to comment in JSON...which it does. I never claimed that it does so in a non-ugly or even good way.

> This specific brand of cleanliness does have a bunch of issues

Issues so massive they, imho, make it not worthwhile to use. As in, I rather miss the ability to write comments or write them with ugly hacks, than put up with YAMLs nonsense.

The fact that better solutions exist (again, like TOML) make this worse.


You just persist in failing to understand the issue

> I think I speak for basically the entire history of programming when I say that ugly solutions exist and are widely used throughout our profession.

I can raise it to the level of the entire history of humanity when I say that people yearn for cleanliness and beauty

> I never argued that this hack solves ugliness.

Sure, because "you choose to ignore [the problem of ugliness] as such". People who share "my opinion" don't ignore that and use cleaner formats, so YAML is a solution that addresses the problem, your suggestion doesn't


> You just persist in failing to understand the issue

And you just persist in making a "counter" based on your opinion of what my argument is, as opposed to what my argument is actually about.


Not "actually", but as opposed to your opinion of what your argument is about




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: