I stopped using Visual Studio Code

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
Search for a command to run...

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
All JetBrains product are great, You cant go back once you start using them :-D
I disagree with you. I think you know the WebStorm IDE, a JetBrains product. The IDE is always good more than an editor. It needs many CPU, and RAM, for running (Compare the number of resources used).
The Editor like VSCode can be considered lighter than IDEs if we use extensions sensibly. But finally, I like your perspective, to some extent, I agree with you
I love JetBrains products. I have used them for PHP, Python, Angular, and NodeJS and they are awesome, really! But for Javascript Frameworks, I switched back to VS Code since it is so minimalistic and fast, if you need a feature, you just download the extension. Eventually, when I'm stuck on some complex projects, I occasionally use Webstorm as it is better at finding problems.
Thanks for this article! I was using VSC for a long time but when I discovered PhpStorm I don't want to go back to VSC cause VSC was not great for PHP especially when it comes to enterprise projects VSC was just lagging and was a pain to use after I switched to PhpStorm I was impressed by the performance, no lag and too many features the only thing that is a problem is the license cost, 10$ per month is a lot in Egypt
Okay, cool, and I think this is an eye-catching title. You stopped using it, good for you. But I'll keep using it. It's hard for me to switch from one IDE to another easily. 🫢
brilliant
Have to agree with JetBrains always amazes me with their awesome code editors i always prefer pycham and intellige idea for writing python and java code and after reading it i might switch to web-storm
Oh you didn't like the JetBrains line?
Chris Bongers it was mainly because of the license costs that I was searching for an alternative. But that was back in 2016, I guess. Back then I choose Sublime Text. And when I discovered VS code, I never looked back 😅
Hello, I registered just to answer you.
First of all what you pay on webstorm, vscode does it too, then it's free and offers more functionality than webstorm if you know how to use it and especially configure it and finally I don't agree with you
Thanks for registering just for my article, and taking the time to reply.
If VSCode does everything for you that's perfectly fine, I'm not against it at all. It's merely me sharing why WS works better for me personally 🙏
Most of you know me for my consistency, a golden arrow in my blog series. I've written 1000 articles in 1008 days! Almost an article a day, and my honeymoon was the only holiday I ever took. I'm super proud of this achievement; it has been a fantasti...

It's not the first time I'll be talking about community. I think it's an essential aspect of any successful tool. This shows in my previous explorations of Astro, Medusa, and now Vendure as well. All these products thrive in a super open, welcoming, ...

The cool part about Vendure is how easy it is to set up and how abstract each layer is. Basically, we get the following elements: External database Server Worker Admin UI Frontend While this is amazing, it also brings a bit of complexity when it co...

The previous article looked at customizing Vendure on a data and process level. In this article, we'll look at customizing emails, as they are often a big part of a webshop system. We'll be looking at two different layers of customization for customi...

Even though Vendure is a pretty significant project out of the box, in some cases, we might want to go in and modify some elements to work to our specific use case. In this article, I'll take a high-level look at some elements we can customize within...

Not because it's bad, not at all, and to be fully honest, I use it for my blog still 🤫.
But because I started using Webstorm, a JetBrains product and love it.
Let me explain why I love this one so much. There are a couple of game-changing elements to it.
I think the first time, I was overwhelmed by all the panels, menus, and actions.
However, you quickly realize they do have a use, but until you learn about that, you can remove panels to make it a super clean editor.
Example of the basic editor opening up.

One of the great features of Visual Studio Code is that it has so many amazing plugins available to make your experience better.
When I downloaded WebStorm, I looked for amazing plugins but quickly realized you don't even need them.
It has so many great things already installed out of the box that you rarely need a plugin.
And if you do, their plugin ecosystem is also huge.
Some examples of things that work out of the box:
If you need a plugin, check out the plugin repo on the Jetbrains website.
The cool part about WebStorm is that it has perfect search functionality.
We can search for either file and actions using the double shift search. This is a powerful way to find files by name, actions, plugins, etc.

Alternatively, we get find-in files, which can be used to find any code in your files! Again super powerful search functionality.

If you are writing a lot of tests, WebStorm has your back! It provides a super robust testing flow, where you can quickly test singular test cases and even quick-view snapshots.
It's super easy to test single tests or files. You can even quickly debug your tests in WebStorm.

Another great option it comes with is code inspection, and this has many incredible benefits to it.
It can quickly detect any issues you might have with your ESLint rules and unused methods.

It will also tell you when you are doing things that don't make sense, like not including alt tags on images.

And the list goes on of code inspection it can do to help you write robust code.
Another great thing about WebStorm is that it's simply super quick. It runs projects without hesitation and has no issue refactoring a widely used import.
Since I started using WebStorm, it hasn't had a single issue (about three months now).
VSC was also pretty fast to me, but WebStorm feels a bit more stable. I had VSC crash on me before, especially while opening large files or refactoring widely used imported files.
I'm not here to tell you that you have to switch. Just sharing why I switched and what benefits I see in WebStorm.
The obvious con is that it's a paid product compared to VSC, which is free.
Thank you for reading my blog. Feel free to subscribe to my email newsletter and connect on Facebook or Twitter