Visual Studio Code

• Go because it's easy and simple, facilitates collaboration , and also it's fast, scalable, powerful.
• Visual Studio Code because it has one of the most sophisticated Go language support plugins.
• Vim because it's Vim
• Git because it's Git
• Docker and Docker Compose because it's quick and easy to have reproducible builds/tests with them
• Arch Linux because Docker for Mac/Win is a disaster for the human nervous system, and Arch is the coolest Linux distro so far
• Stack Overflow because of Copy-Paste Driven Development
• JavaScript and Python when a something needs to be coded for yesterday
• PhpStorm because it saves me like 300 "Ctrl+F" key strokes a minute
• cURL because terminal all the way

Problem was wanting to save time and money on converting well-written C# code to Ubuntu . Solution was to use Mono and Visual Studio Code which allowed us to convert our application libraries straight across.

As developer at Applied Health Analytics we decided to create a React Native App. In terms of #IDE I'm a good fan of PhpStorm cause we have a lot of PHP in the backend, but I've definitely gave a try to Visual Studio Code and now is my primary JavaScript #IDE . I was impress how fast VS Code has become the No.1 @JavaScript Editor in the community.

When I switched to Visual Studio Code 12 months ago from PhpStorm I was in love, it was great. However after using VS Code for a year, I see myself switching back and forth between WebStorm and VS Code. The VS Code plugins are great however I notice Prettier , auto importing of components and linking to the definitions often break, and I have to restart VS Code multiple times a week and sometimes a day.

We use Ruby here so I do like that Visual Studio Code highlights that for me out of the box, with WebStorm I'd need to probably also install RubyMine and have 2 IDE's going at the same time.

Should I stick with Visual Studio Code , or switch to something else? #help

Prettier not formatting code on save in Visual Studio Code ? - I've come across the same issue and took me a long time googling around to find the issue.

It is actually a very simple fix. Add the below to your Visual Studio Code settings.json

"[javascript]": {
    "editor.formatOnSave": true
},
"[javascriptreact]": {
  "editor.formatOnSave": true
}

I use Visual Studio Code every day, it was very refreshing coming from Atom to get a lightweight, all i need setup right out of the box.

After working with Atom for around 2 years I switch to VSCode.

Here is why:

1. Color display of variables in code. This may now sound much, but it improve the display of scss variables and its a core feature.
2. Out of the box features.
3. Automation! VSCode suggests usefull things to you.
4. Integraded console. I love the console in VSCode. It is faster than my 'default' cmd on Windows. For Atom you would have to install a package, that doesn't work so well on Windows.
5. Output logging per Plugin.
6. Setup time. In VSCode I can set up my workspace in under 5 minutes. For Atom I need
7. Plugins work perfect out of the box. This is a mayor one for me. For example: In order to set up Editorconfig you have to adjust mutliple values and plugins to get it work. Plugin creators of Editorconfig for Atom are not to blame: They include a linter, that verifies whether the settings are correct or not.
8. Git implementation. VSCode ships with Git and even if the git packet of vscode doesn't look like much, theres a lot to it. For example you can watch changes inline.
9. Minimap and vertical scrollbar. This feature is much better implementet in VSCode and you don't need an extra plugin.
10. Auto completion. Sass mixins example: @include and you press CTRL+SPACE and VSCode shows you every Sass mixin.
11. Copy paths from open file tab. In VSCode you can copy the path of an file directly when you have it open. In atom you need to select 'show in tree view' and than copy the path or relative path.
12. Tree view. The tree view VSCode automaticly brings you to the current open file by default. This helps when working with components.
13. File search. The file search supports the asterisk so you can search for eg molecule-*.ts .
14. Tasks support. Tasks are integrated in VSCode so eg. for Typescript you can CTRL + SHIFT + B and select tsc: watch - tsconfig.ts .
15. Short waiting time. For example when deleting files or beautifying 20.000 lines of json (Atom hangs up).
16. More releases. Faster feature implementation. Active community.