Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

because inin files have no or very limited support for nesting

there are also some issues with keys being all string by default making some things like linting harder and allowing more less standard ways to get something done, e.g. in json true is true in init files all of true, 1, yes, y and others might be true depending on the application (but then yaml no problem is worse)

also there is no clear single standard for init files

through this is where toml comes from it took the general layout ideas behind init files but give it a strict standard and strict string vs. bool vs. float types and a bit more nesting capabilities and fixes some string distance escape issues, etc



you might want to read this fine piece of propaganda https://github.com/madmurphy/libconfini/wiki/An-INI-critique...


is that satire?

I'm really not sure.

I mean some of the critique is very reasonable like inline tables needing to be inline but inline arrays do not.

But then they present something as INI file which most INI parser will not parse and is directly against much of their previous critique.

and why do I have the feeling that the author is constantly screaming for help internally while writing this article?




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

Search: