#Webstorm javascript full#
#Webstorm javascript code#

Maybe my only gripe with VSCode is that it struggles with big projects, anything over 500k LOC and plugins/linters start bugging out. User land is better for VSCode by an order of magnitude, and I expect that to continue.

#Webstorm javascript full#

I appreciate that VSCode can painlessly switch between a plain old text editor, and a full fledged IDE. I used to find it tedious to basically have to use a new IDE for each language stack, considering it takes Jetbrains IDEs a lot longer to spin up. Having one editor handle everything is nice for monorepo style projects written in multiple languages. It has much better monorepo support, and I just find its source control easier to use for my day to day workflow. Source Control / Git - probably the biggest feature where I prefer VSCode. Since we're in the microservice meta it's a lot more common to switch between smaller projects. You can customize WebStorm really well too, so this is just preferential, but overall VSCode gives me the vibe of something like Sublime Text rather than an old school IDE like NetBeans. You can customize it to be a lot more minimal. WebStorm fans will regularly rave about this point, but WebStorm is only more capable out of the box with Prettier + ESLint configured properly it's about the same.Īesthetics, I think VSCode wins. Here are a few key points:Ĭode completion, refactoring, etc, is the same in both with extensions. Nowadays my language stack is mostly TypeScript, Python, and Rust, (mostly TS) and just having an editor that works exactly how I want for every language is a big deal. I'm a big JetBrains fan, I used to use IntelliJ, PHPStorm, and WebStorm. Try to give it a really fair shake and see if I can learn it better.

And this time I think I'm going to try and make myself use it for a while before I rage quit it haha.

#Webstorm javascript code#

I'm just hoping that someone out here has a bit of experience moving from webstorm to vs code and can give me some pointers because I'm probably going to try vs code again. The code completion the intellisense the debugging tools all of it.

Here's the thing though: as frustrating as web storm is when something like this is broken, when it gets things right (which is like 80 to 90% of the time) it is just amazing. In this case it's the svelte plug-in, it seems to be set to ES4 or something with some of the intellisense errors that I'm getting. Usually my motivation for taking a closer look at vs code is driven by webstorm handling something really terribly. Periodically I take a look at vs code because I keep hearing so much about it and I always believe in giving things a fair shake. I do a significant amount of front end work both at my job and at home and webstorm is my IDE of choice. I've been using webstorm pretty much forever.