Remix.run Logo
firesteelrain 7 hours ago

JSON so much easier in my experience and less prone to error

verdverm 7 hours ago | parent [-]

JSON does not have comments, no JSON5 is not the answer either

Think bigger, it's not something you are using today. The next config language should have schemas built in and support for modules/imports so we can do sharing/caring. It should look and feel like config languages and interoperate with all of those that we currently use. It will be a single configuration fabric across the SDLC.

This exists today for you to try, with CUE

I've been cooking up something the last few weeks for those interested, CUE + Dagger

https://github.com/hofstadter-io/hof/tree/_next/examples/env

throwaway7783 6 hours ago | parent | next [-]

Like XML? :)

lijok 7 hours ago | parent | prev | next [-]

Like Python?

verdverm 6 hours ago | parent [-]

CUE

lijok 4 hours ago | parent [-]

Why not Python?

NewJazz an hour ago | parent [-]

Typing is bolted on rather than a native concept, for one.

firesteelrain 7 hours ago | parent | prev [-]

I genuinely despise the identing requirements of YAML.

For comments, I use a _comment field for my custom JSON reading apps

orev 4 hours ago | parent | next [-]

I dislike the idea of _comment because it’s something that is parsed and becomes part of the data structure in memory. Comments should be ignored and not parsed.

verdverm 6 hours ago | parent | prev [-]

yeah, this is what I'm talking about, innovation has stopped and we do dirty hacks like `imports: [...]` in yaml and `_comment` in json

How are people not embarrassed by this complete lack of quality in their work?

firesteelrain 6 hours ago | parent [-]

I don’t think we need anything formal resembling XML like JSON. It was originally meant for over the wire payloads and people like myself use it for more than that

verdverm 6 hours ago | parent [-]

You're still thinking "good enough". I'm advocating for the "we can do so much better" attitude

The current popular config choices cause a lot of extra work, bugs, and effort. Is improving the status quo not a worthy goal anymore? Are we at a point in history throwing our hands up and saying meh, I deal with this... is basically where people are today? (I'm somewhat a believer of this based on anecdata and vibes)

firesteelrain 3 hours ago | parent [-]

The uncomfortable reality is that config formats don’t win by being best. They win by being:

1. already installed everywhere,

2. easy to parse in every language,

3. supported by editors/linters/CI tools,

4. stable enough that vendors bet on them.