When comparing Qt Creator vs Visual Studio Code, the Slant community recommends Visual Studio Code for most people. In the question“What are the best programming text editors?” Visual Studio Code is ranked 3rd while Qt Creator is ranked 21st. The most important reason people chose Visual Studio Code is:
Ranked in these QuestionsQuestion Ranking
Pro Great syntax highlighting and auto-completion
Qt Creator has a code model which basically has the same information as the compiler. So it can do really nice syntax highlighting (e.g. of virtual methods or local variables) as well as provide great code completion.
Pro Integrates well with non-IDE workflows
Qt Creator uses normal .pro-files, CMakeLists.txt, Makefiles.am, etc. for its projects and rarely needs special configuration for projects.
Projects can be built on the command line as usual.
Pro Fast and fully keyboard-navigatable
Responsive UI, no need to use the mouse for the power users.
Pro Supports CMake
Pro Much space dedicated to the code
Small and beautiful UI, almost all the space is dedicated to the text with hardly and toolbars. Can actually be used on a 1024x768 pixel screen.
Pro Build in Qt GUI editor
Allows for the creation of a window based ui in a graphical editor, no code required to build the ui.
Pro Very responsive when compared to similar software
Pro TypeScript integration
There is very solid TypeScript integration in Visual Studio Code. Both are developed by Microsoft and VSC itself is written in TypeScript.
Pro Extendable through plugins
Visual Studio Code comes fairly complete out of the box, but there are many plugins available to extend its functionality.
Pro Embedded Git control
Visual Studio Code has integrated Git control, guaranteeing speed, data integrity, and support for distributed, non-linear workflows.
Pro Integrated debugging
Pro Ready to use out of the box
You don't need to configure and add plugins before being productive. However, you can add plugins if needed but for the basics you're well covered.
Pro Integrated terminal
There's no need to press alt+tab to go to a terminal: it is directly integrated into the editor.
Shift+~ is a handy hotkey to toggle the integrated terminal.
Pro Great performance
For a 'wrapped' web-based application, Visual Studio Code performs very well.
Pro Integrated task runners
Task runners display lists of available tasks and performing these tasks is as simple as a click of the mouse.
Pro Updated frequently
There's a new release of Visual Studio Code every month. If you are one of the insiders then releases are daily.
Pro ESLint integration
ESLint integrates great. You can define your rules trough .eslintrc.* as usual and vs code will autofix your code on save. So your code is always in style.
Pro Custom snippets support
Snippets are templates that will insert text for you and adapt it to their context, and in VSC they are highly customizable.
Pro Active development
It's really nice to see how the code editor evolves. Every month there is a new version with great communication of new features and changes.
Pro Libre/open source
Released under the MIT License.
Pro Huge community behind it
The ease of getting assistance and finding tutorials is increasing as the community grows.
Pro Fast and powerful
VS-Code has the speed of Sublime and the power of WebStorm. Perhaps this is the best software that Microsoft has ever created.
Pro High fidelity C# plugin
The Omnisharp plugin is very powerful providing full sln, csproj, and project.json support.
Pro It has gotten really good
All it takes is one stop for all the features many people need.
Pro Inline definition picking and usages finding
These features allow you to have a glance at code without opening it as a whole in a separate tab. Moreover, editing is allowed.
Pro Support RTL languages
It supports pretty web rtl languages like arabic languages when most of other editors don't support it.
Pro JS typechecking
It leverages TypeScript compiler functionality to statically type check JS (type inference, JSDoc types) with
Pro Python support
Excellent Python plugin, originally created by Don Jayamanne, now hired by Microsoft to extend and maintain the extension.
Pro Good support for new Emmet syntax
Con Errors only show on compilation
No default precompiler for early error checking.
Con Poor refactoring
QtCreator has lack of refactoring features. It's not even close to Resharper++ or CLion
Con Poor multi-window mode support
While multiple windows are supported, many operations will activate in the primary window (search, debug, goto-line... etc).
Con Qt Focused
Qt Creator is focused on being an IDE for Qt, as a general purpose IDE it performs quite well, but there are areas which are lacking such as project file support (support for generic/CMake projects lags behind Qt projects).
Con The autocomplete and code check is not as powerful as the one on WebStorm
Sometimes it doesn't tell you if you made a typo in a method name or if a method is not used and several other important features.
Con Project search limits results
Because file search is so slow your results are limited in order to simulate a faster search.
Con Embedded Git isn't powerful enough
You can do nothing but to track changes, stage them and commit. No history, visualization, rebasing or cherry-picking – these things are left to git console or external git client.
VS Code is a general code/scripting IDE built to be lightweight and for people familiar with their language of choice, not directly comparable to Visual Studio in power or scope.
Con No support for tiled/grid editor layouts
It can be configured for rows of editors, or columns of editors, but not both simultaneously. The development team has explicitly said this is not a priority.
Con Very bad auto import
Con A "me too" offering from MS, far behind other well established editors that it attempts to clone
Other IDEs specific to a language often offer better tools for deep programming.
Con Slow launch time
Than it's competitors, e.g. Sublime Text.
Con Is not an IDE, is a text editor
Con Have no good default js style analyzer
In WebStorm there is analyzer that checks for warnings and highlight this in yellow, here I cannot find or add it even with plugins. It is possible to have it as errors with linter but while you are actively changing file that's not very nice.
Con Emmet plugin often fails on even simple p tags
Con File search is extremely slow
It's absolutely not possible to use this tool with big projects given how long it takes to search for files.