Hacker News Reader

> value in € = 345 # valid with libconfini but invalid in TOML

This is degenerate.

You want a key-value format easy to pick up, and easy to edit by hand - otherwise you'd rather just use something like SQlite - in particular if you "need" the other insanity that is sections in INI files.

Why the heck allow spaces and UTF8 in key names? To satisfy someone's libido?

View on HN

Unicode is useful for languages other than English, and has nothing to do with anyone's libido.

Don't tell me, my native language uses a bunch of those weird çharacters. I also know that it always eventually cause problems because there's always legacy software that doesn't handle them properly.

But what really is the purpose of allowing supporting in key names? Current keyboards - at least those sold in Europe - do have a key for €, but imagine some lunatic "app developer" insists that another INI key name should be spelled "value in ¥". Customers, coworkers, support desk staff, everyone will curse them.

Reply on news.ycombinator.com