vscode

Quiet in here? Check #calva-dev out :smiley:
2020-01-29T00:53:49.073900Z

@pez btw, have you experimented with vscode extension packs at all?

pez 2020-01-29T06:52:26.075600Z

Just a little bit. Calva used to be an extension pack, but I never really used any API between them.

2020-01-29T10:59:42.077100Z

thanks for the info. if you don't mind sharing, what were the reasons for calva to stop being an extension pack? is there somewhere i can read about that?

pez 2020-01-29T11:13:20.081Z

The reason it was an extension pack was that I wanted non-Calva-REPL users to be able to use parts of Calva, like formatter, highlighting, structural editing. But it was hard to maintain when in pieces, so I decided to let Calva be an all-or-nothing offer instead.

2020-01-29T12:09:50.086800Z

ah thanks. the "hard to maintain when in pieces" aspect is most unfortunate. it seems to be quite a tricky situation. the larger a project becomes, the harder it seems to be to wrap one's head around things (especially for potential new contributers, but sometimes coming back to pieces that haven't been visited in a while). on the other hand, it also seems difficult to ensure things work together well when they are split apart. i haven't really encountered a good testing story for extensions (whether it's in vscode or plugins in atom) which i guess doesn't help either. may be there are good ways that i just don't know about :) i wonder how some of these larger extension packs are being managed (e.g. the java extension pack).