KSON looks neat.

I think the post is hurt by the desire to sort of… “have a theory” or take a new stance. The configuration file is obviously not a user interface, it is data. It is data that is typically edited with a text editor. The text editor is the UI. The post doesn’t really justify the idea of calling the configuration file, rather than the program used to edit it, the UI. Instead it focuses on a better standard for the data.

The advancement of standards that make the data easier to handle inside the text editor is great, though! Maybe the slightly confusing (I dare say confused) blog title will help spread the idea of kson, regardless.

Edit: another idea, one that is so obvious that nobody would write a blog post about it, is that configuring your program is part of the UX.

▲

vrighter 15 hours ago | parent [-]

if writing a "data" file is how you configure the app, then that data file is the interface between you and the software. Since you are a user, that makes it a user interface.

▲

bee_rider 13 hours ago | parent [-]

I’ve never written a file directly. The cells in the SSD are very small, my hand is not steady enough to flip the bits manually. For me the UI for writing files is usually Vim.

	▲	vrighter 3 hours ago \| parent [-]
		the ui for writing the data file is vim. The ui for the target application is the data file you wrote.