NireBryce

Nire Bryce

@NireBryce

reality is the battlefield

the first line goes in Cohost embeds

🐥 I am not embroiled in any legal battle
🐦 other than battles that are legal 🎮

I speak to the universe and it speaks back, in it's own way.

mastodon

email: contact at breadthcharge dot net

I live on the northeast coast of the US.

'non-functional programmer'. 'far left'.

conceptual midwife.

https://cohost.org/NireBryce/post/4929459-here-s-my-five-minut

If you can see the "show contact info" dropdown below, I follow you. If you want me to, ask and I'll think about it.

log inask
NireBryce
@NireBryce

I've got one more opinion until next week: you should never use json for your config file. yes even if it's not supposed to be user facing.

some day someone is going to need to dig into the config to debug something and the least you can do is let them use comments

"so... json-with-comments?" no. it's not a real standard and also in this house we do not "throw good money after bad". make your config yaml. make your config .ini. make your config in sh. I don't care. you're parsing options it doesn't matter what it's in. so make it in something that both supports code comments and syntax highlighting.

just don't make it in JSON. or if you do, have the user facing portion be in literally anything else and then juice it into JSON in the background if you need to be a filthy little gremlin about it.

You must log in to comment.

in reply to @NireBryce's post:

NireBryce
@NireBryce

good luck finding that one again on a skim, though honestly highlighting engines really should comment-color those.

you don't even have to worry about the trailing comma being a footgun if you go full haskell gremlin and

[ prefix
, them
, like
, bullet
, points
],
login to reply
Pinned Tags