Switching IDEs can be a bit annoying (and a RAM hog if you have both open at the same time), but it allows me to use the best tool for the job, so I find it's worth it in the end. In reality, I usually have both IDEs open at the same time and switch to the one that meets my needs best for the particular task I'm working on. Also, I may find myself missing GitHub copilot suggestions when coding in WebStorm, but right now I don't feel that way (possibly because I haven't used GitHub copilot enough). the Prisma extension that can format prisma schema files on save). An open source version of GitHub Copilot, a language model About GPT-Code-Clippy (GPT-CC) GPT-Code-Clippy (GPT-CC) is an open source version of GitHub Copilot, a language model based on GPT-3, called GPT-Codex - that is fine-tuned on publicly available code from GitHub. That being said, there are some times where I'm coding in WebStorm and want to benefit from a VSCode extension (e.g. I've found myself switching over to WebStorm while working in VSCode if I need to do some significant refactoring. If I had to pick a single editor, I would pick WebStorm due to its superior refactoring capabilities.
The past couple of weeks I've been switching between both VSCode and WebStorm for the sake of being able to compare both editors accurately.
When I open up webstorm it locks up on some. This is the same as I've done the last 4 years. I run win 11, but all my dev work is in WSL. I recently built a new dev box that is by any standard top of the line. The GIT tooling is top notch and one of the killer features I rely on. The only thing I've noticed that WebStorm does better than VSCode is that WebStorm will switch to the correct TypeScript version based on which file you're editing in the monorepo, whereas VSCode doesn't do that. I've been using webstorm professionally these last 4 years. Both editors seem to be able to handle opening projects at the root of a monorepo and still provide working autocompletion and formatting on save.
0 kommentar(er)
