"YAML is the worst of all" => only if you want to do complicated things with it. If you stick to the basic types (int, float, str, list and dict), it's no more complicated than TOML.
Oh but it is. The simple fact you need to know what version of yaml your document and your parser are for and that most people don't know about thay is proof of it.
Indeed, I never bother with the version of yaml my document is written with. But I don't see it as a problem.
Again, if you use the simple types, you have almost no problem nowadays. Issues arise when people overcomplicate their configuration file and try to use advanced features of the YAML specification (a big mistake IMO).
If the Python core devs managed to have a bug because of the leading zero of python 3.10 (https://hugovk.dev/blog/2021/the-python-3-1-problem/), and I think it's safe to say they have a modicum of software experience, then the format is a problem. How do you expect the average programmer to not make mistake? How to you expect people to restrain themselves to a safe subset they don't even know is needed ? How do you deal with the complexity of the matrix of all parsers and files used in different ways, with different versions?
This "if you do it right" stance doesn't hold water in practice.
Hi Bite Code!
There is some typo. in above Cue language link: it currently points to https://github.com/ClueLang/Clue, which is some "programming language that compiles into Lua code", whereas Cue language (without "l") GitHub is https://github.com/ClueLang/Clue, and its homepage https://cuelang.org/
Thank you !
"YAML is the worst of all" => only if you want to do complicated things with it. If you stick to the basic types (int, float, str, list and dict), it's no more complicated than TOML.
Oh but it is. The simple fact you need to know what version of yaml your document and your parser are for and that most people don't know about thay is proof of it.
Indeed, I never bother with the version of yaml my document is written with. But I don't see it as a problem.
Again, if you use the simple types, you have almost no problem nowadays. Issues arise when people overcomplicate their configuration file and try to use advanced features of the YAML specification (a big mistake IMO).
If the Python core devs managed to have a bug because of the leading zero of python 3.10 (https://hugovk.dev/blog/2021/the-python-3-1-problem/), and I think it's safe to say they have a modicum of software experience, then the format is a problem. How do you expect the average programmer to not make mistake? How to you expect people to restrain themselves to a safe subset they don't even know is needed ? How do you deal with the complexity of the matrix of all parsers and files used in different ways, with different versions?
This "if you do it right" stance doesn't hold water in practice.
OK, I see your point. I don't have a counter-argument at the moment, at least. :)
Why not https://pkl-lang.org/ ?
The python bindings are in an abysmal state.