twtxt

Timeline for https://eapl.me/twtxt.txt

🔄 Refresh timeline

👨‍💻 Login

Following: 16

tkanos https://twtxt.net/user/tkanos/twtxt.txt Remove

eaplme https://eapl.me/twtxt.txt Remove

eaplmx https://eapl.mx/twtxt.txt Remove

lyse https://lyse.isobeef.org/twtxt.txt Remove

prologic https://twtxt.net/user/prologic/twtxt.txt Remove

rrraksamam https://twtxt.net/user/rrraksamam/twtxt.txt Remove

darch https://neotxt.dk/user/darch/twtxt.txt Remove

shreyan https://twtxt.net/user/shreyan/twtxt.txt Remove

movq https://www.uninformativ.de/twtxt.txt Remove

bender https://twtxt.net/user/bender/twtxt.txt Remove

stigatle https://yarn.stigatle.no/user/stigatle/twtxt.txt Remove

darch http://darch.dk/twtxt.txt Remove

xuu https://txt.sour.is/user/xuu/twtxt.txt Remove

jason https://jasonsanta.xyz/twtxt.txt Remove

mckinley https://twtxt.net/user/mckinley/twtxt.txt Remove

eapl-mes-7-daily-links https://feeds.twtxt.net/eapl-mes-7-daily-links/twtxt.txt Remove


lyse
Question of the day: What configuration file formats do you all like and use?
2 months ago
💬 Reply


mckinley
Reply to #zwpd7hq
@lyse `key=value\n` or JSON. YAML is the worst and I don't understand why it's so popular.
2 months ago
💬 Reply


xuu
Reply to #zwpd7hq
@lyse i made my own :D

I do prefer toml for the old school ini style with added support for object lists.

my second would be hjson or any other json with comments style.
2 months ago
💬 Reply


eapl.me
Reply to #zwpd7hq
For Python, env files with dotenv.
For JS, usually JSONP or a config.js
For PHP a config.php with an array usually works
For C#, I try to avoid the ugly native XML, but it's what most of the team use...

For most I have a .env.sample in the repo, and we ignore .env or config* to avoid storing credentials.
2 months ago
💬 Reply


lyse
Reply to #zwpd7hq
Yeah, the lack of comments makes regular JSON not a good configuration format in my view. Also, putting all keys in quotes and the use of commas is annoying. The big upside is that's in lots of standard libraries.

I think the appeal with YAML is that is has comments, is kind of easy to write and read and also provides unlimited nesting levels. But it has all its drawbacks, no question. Forbidding tabs, thousands of different string flavors, having so many boolean options (poor Norwegians) etc. I use it, but I don't particularly enjoy it.

Among simple key value pairs, I like INI files, but with `#` for comments, not `;`. I never used TOML, read up on it yesteray before writing this question, but it looks a bit weird and has some strange rules. I guess I have to give it a try one day.

And yes, as mentioned by several of you, it always depends on the complexity of the configuration at hand.

I'm developing something for the scouts at the moment with rather simple requirements on the config. Currently, there are just four settings. Even INI would be overkill with its section. I selected JSON for now, because that's readily available with Go's std lib. But I do not like it.

Btw. what's your own config format, @xuu?
2 months ago
💬 Reply


mckinley
Reply to #zwpd7hq
@lyse Lack of comments are definitely a shortcoming of JSON. I don't like TOML because it lets you have nested categories (`[foo] [foo.bar] [foo.baz]`) and it just feels confusing to me, even with indentation. Simple INI files are okay.

The Prosody XMPP server's configuration file is just a Lua script because Prosody is written in Lua, and that's excellent.
2 months ago
💬 Reply


mckinley
Reply to #zwpd7hq
@lyse Regarding YAML's readability, I miss the `-` for list items *constantly* when reading YAML files. I'll get confused because I think I'm not in a list or I'm in the previous list item, then I have to go back. List items are all on the same indentation column and one tiny character is the only thing defining a new one. I don't know if others have this problem.
2 months ago
💬 Reply


⏭️ Next