• 0 Posts
  • 34 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle




  • linting config itself wouldn’t be defined there, and it would be verified in ci and such, but a setting to tell vscode which linter and extension it should use to show warnings would be.

    modern languages may have their own way for configuration but they don’t have a way to bind it to the list of vscode tasks and define how to run a debugger, which is the part that gets stored.

    it’s easy to go overboard with extension suggestions, but I don’t think adding an extension for linter used, extension for formatter used, and any languages used if there’s a definitive extension.

    My team is split between visual studio, vscode, and I use emacs. we have config for both vs and vscode in our repos since it makes working on a new project so much nicer and means we aren’t just sharing editor configs through side channels instead. it doesn’t do anything to me if I have editor config for an IDE I don’t use in the repo, but it makes it easier for someone new to jump in with a sort of same environment immediately
















  • I’ve found nixos is perfect for me since I like how precisely I can configure it.

    Oddly enough, I’ve had a decent chunk of my only barely technical friend group switch to it for the opposite reason. They all just copypaste snippets of config between each other, and if something breaks they just go back a revision. I doubt any of them spend much time configuring anything. It really is the perfect idiot proof distro and I don’t normally see people talking about that side of it