Hacker News Reader

I agree that being literally forced to use Codespaces is kind of shitty.

On the other hand, establishing code consistency is important, and it all depends on your editor's linter/prettier. They have to produce the same output, and even managing that within the same editor is difficult because you might have different versions on each dev machine, or different user settings. Doing so across editors is even more difficult.

View on HN

Prettier / linter can just be run in a git hook and verified in a GitHub action / CD step though. Prettier config should be committed to the repo itself, then let devs decide how they want to apply it to their workflow (and prevent them from merging otherwise).

There's also the benefit of "dog fooding" their own product that they're selling to customers.

Reply on news.ycombinator.com