stardustreverie

What You Get When the Stars Collide

21yo plural autism, trans girl, professional internet weirdo, late blooming theater kid, video editor, occasional musicker, voice actress in progress, still learning about stuff
emily subsystem will probably be main posters

๐Ÿ - goatmily / emily delta
๐Ÿ - catmily / emily tau
๐Ÿช - omicron(?)

๐Ÿ’œ - josie/piece (@pieceofjosie)
๐Ÿฆ‹ - alex
๐Ÿ”† - soleil
๐Ÿช„ - marisa (@marisakirisame)
๐Ÿ–ฅ๏ธ - EMI (@exe-cute-able)
and many more...


discord
@stardust.reverie

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:

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
],