>>108053803
TOML is just an ini file: https://toml.io/en/

>>108053814
ini files are shit for configuration, json is legitimately superior

>>108053837
do elaborate. my config files contain paths, slashes need to be escaped in json, so its shit for my usecase

>>108053803
sexp or bust

File: 1743173215999927.png (55.9 KB)

55.9 KB PNG

>>108053803
>sqlite
>config files
Yeah what a genius idea, have to use sqlite and write sql just to edit a setting. Change a column, etc? Have fun making all your consumers migrate their "config" file.

>>108053814
Real INI files are the best. TOML is way too overcomplicated, and JSON sucks to edit by hand.
>b-b-but there's no a-authoritative specification
Because it's too simple to need one.

>>108053942
{"key": "value"} > key = value
simple as

>>108053803
No, it's not. JSON is serialization format.

>>108053814
I've seen so many shitty ini file extensions, this is right up there with some of the worst. The latest spec loosening multiline shit makes it a lot less bad but still. Jesus Christ. At least it isn't some flavor of significant indented ini bullshit.

>not using json5 for configs
ngmi

>Sqlite
>Config file
Explain to me how sqlite is not overkill for a config file? When is configuring something a relational problem?

File: 1764115609435247.webm (452.7 KB)

452.7 KB WEBM

>>108053803
in my project i use a compressed protobuf file as the config file

>>108053803
>no comments

>>108053803
>config file
For any config file on planet, a humble .txt is perfectly fine. Only fags need to be chained to some gay arbitrary format and syntax.

>>108053803
Plaintext, key value, tab or colon seperated.
/thread

CSV files are just superior since they let me configure a dozen programs at once

>>108053814
Tranny format

File: tiresome.png (642.7 KB)

642.7 KB PNG

>>108054815
>trannies out of nowhere

File: configs.png (830.5 KB)

830.5 KB PNG

Imagine using anything but simple text files.

>>108054759
Indeed.

>>108054274
>Explain to me how sqlite is not overkill for a config file?
Depends what the config is. If your config is a complex graph with properties on everything, then that DB is probably simpler than the alternatives, and definitely easier for someone else to understand.

>>108054918
text files are terrible for any nesting
json lets you use jq and similar for parsing

>>108054274
it was half shitposting but you can query via bash from an sqlite db
the most important thing in a config file is that AI can parse it with standard tools

xml is the correct answer for config files btw

>>108055266
xml fags can't even figure out how to encode a list of values
>Should we do ...bros?

>>108055266
XML is certainly better than this JSON shit. I don't care about these young people crying about how it's too verbose.

>>108055231
>text files are terrible for any nesting
It works fine. You're doing it wrong if you need 100 layers of nested shit.
>SQLlite
Garbage. Now you're stuck depending upon a daemon being up at all times just to read configuration.

Text files are the gold standard because they're fail proof. There is a reason why UNIX has always used them.

>>108055300
>daemon
>sqlite
Anon....

How do I convert a jpg to a text file?

How do I convert a movie to a book?

# comment
foo 42
bar "something"

that's it, meng

>>108055300
>It works fine.
no it doesnt
grep has no idea of nesting

also
>sqlite
>daemon
lmao

>>108055328
>How do I convert a movie to a book?
whisper

>How do I convert a jpg to a text file?
paddleocr

>>108055307
*library

My point stands. I have never liked SQLlite. Either use a full blown RDBMS or use simple text files. Your config files should never get to the point where you need a database to store them in. SQLlite has several downsides and is a compromise no one should ever be making. Like the fact that the entire database becomes locked when something is accessing the file it's stored in.

>>108055378
Oh I see because I had a brain fart and said daemon when I mean to say library you'll just ignore anything I have to say. Par for the course for this board in 2026.

JSON is retarded. SQLlite is retarded. If I see that (or YAML) I instantly know trying the application is not worth my time because only a retard would make those choices.

>>108055364
the only other sane option are gnu recfiles

>>108055399
you're retarded, sqlite has countless uses
i was shitposting when i suggested it for a config file but to discount it entirely is lmao tier

>>108055416
It's shit. Most everything that uses it is shit (see: Firefox).

I've discounted it completely because I spent years determining it's shit and dealing with retards that would do stuff like use it as the DB for their forum when we offered MySQL and Postgres support in the same web application. It only ever caused everyone a bunch of pain.

Use a proper RDBMS instead of this piece of shit or code your shit properly where you can use flat files instead of a flat file LARPing as a SQL server.

>>108055431
this is some novel mental illness

>>108055431
sqlite3 is fine. In 2026 you can't fuck up. Literally the only issue you'd run into is busy errors and you can fix that with single writer or partitioning your data into multiple sqlite3 DB files.

>>108054918
thats a .conf file idiot

>>108053814
FPBP
>>108055431
I don’t even like SQL, but SQLite is so robust and battle tested it’s certified for use in aviation while MySQL and PostgreSQL are dog shit everywhere.

>>108053803
Json annoys me, it's simple but it's also easy to mess up the syntax and not find the missing comma

File: 1769971059757923.png (802 KB)

802 KB PNG

>>108053803
>sqlite
>not T-SQL

>>108053803
>42:
Oh well well well. You are incorrect mister. .txt is enough for most config applications where sqlite is too much hassle. Screw your head on straight dummy.

>>108053814
This formst is the worst of all worlds.
It's more bloated than plain .ini, yet misses all the more powerful features of YAML.

>>108053803
You can't even comment inside json files.
xray-core chinks use json for configs and it's absolute ass.

>>108056766
that's because json is not a configuration format.

File: 1681500810058254.gif (2.4 MB)

2.4 MB GIF

>>108053803
>>108054143
>json
Use the command pattern baka, JSON was made for data serialization not for configuration, in fact it's dumb to do config in a declarative way, configuration should be imperative, JSON/YAML should all stop being misused by webshitters that don't know any better.

iptables -A INPUT -p tcp --dport 22 -j ACCEPT
iptables -A INPUT -j DROP

>sqlite
That is good for runtime settings not init configuration (two completely different things).

>>108054119
Exactly.
>>108054759
>>108054801
No plaintext is retarded UNIX braindamage.
No CSV/TSV is for data, again.
>>108053966
>>108054274
He confuses config file with runtime store for application settings, the kind you would do for a graphical application.

>>108054098
>key = value
that's just a .properties file

>>108057105
therefore it's not the best option for config files

json configs are for people to dumb to handle flex and bison

XML or die. A format made for J*vaScr*pt is a parody to config formats, and cannot be taken seriously.

Isn't yaml supposed to be the best of all worlds?

>>108057825
You may use a anime pic to look like one of our regular pervert but making incoherent statement gave you real streeshiter identity away

>>108057864
You're literally too ignorant to understand my post.

>>108055328
>Open the image as text
>Print the frames and staple

Best option is a single line text file, with values separated by commas.

It's simple and easy to parse, while still being totally readable and easy to write.
Of course neckbeard incels will hate it.

>>108053803
it's genuinely easier to edit a config.h file and recompile than it is to use json
INI files with no distinction between numbers and strings are better for mere mortals to use, and if you think that more precise is better, then just have the user edit the source code
mpv style configuration where command line flags can be put in line by line without the leading dashes is also good

>>108053803
The best option for a config file is just whatever language the program is written in. The prigram can just import it directly. No need for serialization. Als comes with the versatility of actual code.

>>108053803
>human readable serialization format
>NO COMMENTS

>>108053803
XML>>>>JSON
Always has been.

>>108058927
Absolute on the spectrum comment

>>108057849
Based.

File: 1320710158754.jpg (4.2 KB)

4.2 KB JPG

the problem with json or yaml or any text file config format, really, is that when you need a crapload of configuration, you end up with either 1 huge unmaintainable config file, or multiple config files which are also a pita to maintain because of possible dependencies and having to remember what is where, making sure they get loaded in proper order etc.

with sqlite you get structure and dependency validation for free (FKs) but it's a pita to version it (you need to serialize to sql and back)

if only there was some GOOD structural editor for json or yaml..

File: G_5fcvUaUAAOsaW.png (1 MB)

1 MB PNG

>>108053803
Are you ready for the era of symantic config files read by an llm, which then configures the program at every boot?

File: G_OE7mbXIAABAG2.png (464.2 KB)

464.2 KB PNG

>>108053803
What's wrong with cvs? Or better yet, whatever you call what mpv uses.

>>108059882
>config files read by an llm

congratulation, that's the most retarded thing I heard this week
a configuration reader implementation that can make your program behave differently each time it's run because llm will hallucinate something new each time

any actual application that needed a serious amount of config, like a d2 bot or wow bot, would have it's own txt based format and its own methodology for using various config files tell me im wrong you cant

>>108059986
>noviceware like bot programs
seriously?