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
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
This specific brand of cleanliness does have a bunch of issues, but that's a trade-off depending on a use case