Microsoft offers Visual Studio Code, an open source text editor that supports code editing, debugging, IntelliSense syntax highlighting, and other features.
Those are agentic IDEs, a fork of VSCode, but Visual Studio Code is used for inferior hardware and has fewer features, whereas others have more features but can't be used on those devices. So, it's the POV of the machine's config: which IDE should be used? If it has a good …
As described earlier, for low overhead projects, Microsoft Visual Studio Code does a great job of getting you in and out, all the way down as far as launch time for the app and compile time. Xcode is really feature heavy, but that makes learning how to use it a task of its …
Microsoft Visual Studio Code is a great competitor to all the IDEs listed above. The vast range of extensions is a strength of the Microsoft Visual Studio Code ecosystem. Integration of Copilot is another add-on, which makes development and debugging very easy and …
It is easy to use, has strong community support and add-ons, and lets you organize files in different languages in an easy-to-use, collaborative environment. The main reason I use it is its easy integration with Git and Jupyter notebooks.
As mentioned before, IDE's can be excellent with one thing, and the company we do a lot of things, so it's kind of annoying to have multiple programs, heavy ones to open your work, so just use one, Microsoft Visual Studio Code, personalize thanks to extensions, and you are …
Microsoft Visual Studio Code offers a wide variety of addons for supporting most scripting and programming languages. In contrast, Power Automate differs from the tools we need for our business task automation. We were told to use Power Automate, but it couldn't meet our …
Notepad++ is a great tool, but has most of the power tips and tools of notepad++ are available into Microsoft Visual Studio Code I use less and less notepad++. It's more easier to "stay" into Microsoft Visual Studio Code, open a new window do my stuff and go for the next task.
The other IDE that I use is Eclipse. Comparing both, Microsoft Visual Studio Code it clearly wins in resource consuming. I can have open many instances of Microsoft Visual Studio Code and the memory ram usage it doesn't go very high. Another point where I prefer Microsoft …
Microsoft Visual Studio Code provides more flexibility and supports easy integration to different platforms (including cloud). It is more modular and lighter application as compared to other integrated development environments. Microsoft Visual Studio Code is easy to learn and …
prior to Visual Studio Code, I was using Sublime Text, which was not the most effective in terms of third-party libraries and complex debugging, so I switched to Visual Studio Code where I got a positive as a developer. it is having all the features and third-party libraries to …
Verified User
Engineer
Chose Microsoft Visual Studio Code
Visual Studio code UI is very handy. Extension feasibility is good
Verified User
Engineer
Chose Microsoft Visual Studio Code
Far better than Eclipse IDE. Eclipse takes so much space, and it is slow. Whereas Vs Code IDE is so fast and having good UI as compared to Eclipse. I help to work efficiently and is also highlight the syntax in good way by recommending in editor. Microsoft Visual Studio Code …
Verified User
Director
Chose Microsoft Visual Studio Code
[Microsoft] Visual Studio Code beats the competition due to its extensibility. Their robust extensions architecture combined with the plethora of mostly free extensions written by the community can't be beaten. The fact that this tool itself is provided by a world-recognized …
VS Code is much more lightweight than IntelliJ and Eclipse and is certainly comparable to Atom. I find that for most of my projects, VS Code is the most stable option, and is generally the quickest to boot. Generally, trying out all four can't hurt, but VS Code has been the …
1. More features compared to Notepad++ 2. fast performance compare to Android Studio 3.More and usefull extensions then other two 4. Easy to use and everyone can start using it instantly 5. Version Control system is top notch 6.If you start using it , you will forget other ides …
Microsoft Visual Studio Code is a combined form of the above-mentioned products i.e. one product, many applications. Eclipse is suitable for java development, PyCharm is mainly for Python development whereas Android Studio is for Android applications development but in …
Verified User
Technician
Chose Microsoft Visual Studio Code
It has some much more functionality than Notepad++, all the addons make editing scripts a breeze
Microsoft VS Code is extremely customizable with needs. So, features like syntax highlighting, bracket-matching, auto-indentation, well-integrated terminal, and side-by-side editing are powerful. Even these features are given free with Microsoft VS code. PyCharm and WebStorm …
It has [the] right balance of solutions for [a] wide range of problems. Atom or Notepad++ are lighter but [have fewer] features, [Microsoft] Visual Studio [Code] is full of features but [a] tad heavier.
We had better luck with VS Code than Atom. We tried to like Atom pretty hard, but it just had some clunkiness and some unintuitive things that caused us to give up on it. Webstorm seems to be a much more capable competitor. The main pro of VS Code over Webstorm is that VS …
For low-end devices, it is a very good tool, but for devices that have decent RAM and decent CPU, I would recommend Android Studio for Android dev as it has more features, and for others, I will recommend agile IDEs like Cursor and Anti-Gravity, as they offer higher limits on AI models, and autocomplete is unlimited as well.
The customization of key combinations should be more accessible and easier to change
The auxiliary panels could be minimized or as floating tabs which are displayed when you click on them
A monitoring panel of resources used by Microsoft Visual Studio Code or plugins and extensions would help a lot to be able to detect any malfunction of these
Solid tool that provides everything you need to develop most types of applications. The only reason not a 10 is that if you are doing large distributed teams on Enterprise level, Professional does provide more tools to support that and would be worth the cost.
It is great for non-mainstream Apple device programming (anything not using Swift or Obj-C). However, it is not as full (some would say overly) featured as Xcode, so sometimes you are looking for a feature that it just doesn't have. The ability to add functionality via plugins is a benefit, but the NEED to add features that way is a drawback. Still in all, a solid "almost" IDE.
Overall, Microsoft Visual Studio Code is pretty reliable. Every so often, though, the app will experience an unexplained crash. Since it is a stand-alone app, connectivity or service issues don't occur in my experience. Restarting the app seems to always get around the problem, but I do make sure to save and backup current work.
Microsoft Visual Studio Code is pretty snappy in performance terms. It launches quickly, and tasks are performed quickly. I don't have a lot of integrations other than CoPilot, but I suspect that if the integration partner is provisioned appropriately that any performance impact would be pretty minimal. It doesn't have a lot of bells and whistles (unless you start adding plugins left and right).
Active development means filing a bug on the GitHub repo typically gets you a response within 4 days. There are plugins for almost everything you need, whether it be linting, Vim emulation, even language servers (which I use to code in Scala). There is well-maintained official documentation. The only thing missing is forums. The closest thing is GitHub issues, which typically has the answers but is hard to sift through -- there are currently 78k issues.
Visual Studio Code stacks up nicely against Visual Studio because of the price and because it can be installed without admin rights. We don't exclusively use Visual Studio Code, but rather use Visual Studio and Visual Studio code depending on the project and which version of source control the given project is wired up to.
It is easily deployed with our Jamf Pro instance. There is actually very little setup involved in getting the app deployed, and it is fairly well self-contained and does not deploy a large amount of associated files. However, it is not particularly conducive to large project, multi-developer/department projects that involve some form of central integration.