11:01 <Rurik> hi ec

11:05 <ec> hi!!

11:05 <ec> how’s life

13:10 <Rurik> ec: very good

13:10 <Rurik> I'm studying Computational Linguistics now

15:38 <jfhbrook> oh interesting, how did I not know that :D

15:38 <jfhbrook> ljharb: so it looks like I'm gonna be writing something kinda like nvm but for postgres. if you knew that I was going to do this without reading nvm's source code, what would you want me to know to make sure I don't do something dumb?

15:39 <jfhbrook> I've looked at bits and pieces of the pyenv and conda codebases so I'm not *worried* but I haven't done this on a practical level before

16:06 <jfhbrook> one thing I've been pondering is the format for the config file (this part is a lot more like conda than nvm) - I kinda wanna be a turd and write a typescript-based DSL, but Many People Are Saying that yaml is the preferred format

16:09 <jfhbrook> of course I can support both - have two formats that expose roughly the same declarative AST

16:09 <jfhbrook> and use the typescript DSL to make it less boilerplate-y

17:26 <ljharb> jfhbrook: so rule number one, don't fucking use posix

17:27 <ljharb> jfhbrook: for any config file, make sure that it's extensible from day one; meaning, there's a way to safely ignore new additions, ideally warning on them in a cached way so they only warn once

17:27 <ljharb> also yaml sucks

17:27 <ljharb> toml is better but niche; use json

17:43 <jfhbrook> yeah I kinda hate yaml and I think toml is not great for declarative DSLs

17:43 <jfhbrook> nice thing about json is —save would work for managing pgxn extensions and such

17:45 <jfhbrook> that was my biggest frustration going from npm to setuptools