When comparing SciTE 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 SciTE is ranked 9th. The most important reason people chose Visual Studio Code is:
Ranked in these QuestionsQuestion Ranking
It's property files allow for fine tweaks of its behavior, at a global or per language / project level. These textual settings might be confusing for those used to preference dialogs, but prove to be powerful, flexible, and fine grained.
With less than 2 MB of binary on Windows, SciTE starts instantly. Plus, if you don't need all the config, syntax files, blah, there's a 678k standalone .exe version. Nothing is going to beat that for lightweight and start-up times. Stick it in a folder that is already on your PATH.
Pro Built-in shell
The console window can show the result of ran commands (like build current file, reporting warnings, and errors), but also accept interactive shell commands.
SciTE works on Windows and Linux, and it also has a commercial port on MacOS.
Based on the Scintilla source code editor, SciTE has some advanced features like rectangular editing, simple regular expression search and replace, code folding, etc. It allows the user to launch a compiler or interpreter, and it can also interpret the error messages, jumping at the location they point to.
Lua scripting is key to SciTE's power and flexibility. The Lua scripting language can be used to perform complex text transformations. It's relatively simple syntax and its large user-base makes it a great choice for a scripting feature.
Pro Powerful syntax highlighting for numerous languages
Lexers providing folding and syntax highlighting are based on code, not on regular expressions. They support context, nesting, special rules, etc.
Pro Free (except on Mac) and open source
SciTE is written in C++, with lot of contributors, both to the core and to the numerous lexers.
Has a simple graphical user interface
Pro Integrated debugging
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 Embedded Git control
Visual Studio Code has integrated Git control, guaranteeing speed, data integrity, and support for distributed, non-linear workflows.
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 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.
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 Great performance
For a 'wrapped' web-based application, Visual Studio Code performs very well.
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 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 Libre/open source
Released under the MIT License.
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 Huge community behind it
The ease of getting assistance and finding tutorials is increasing as the community grows.
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 High fidelity C# plugin
The Omnisharp plugin is very powerful providing full sln, csproj, and project.json support.
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 It has gotten really good
All it takes is one stop for all the features many people need.
Pro Support RTL languages
It supports pretty web rtl languages like arabic languages when most of other editors don't support it.
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.
No extensions, Themes.
Con Missing file browser
SciTE's greatest weakness is perhaps the file browser. It does not really have one, just a poor substitute which works a little bit like a terminal window with
dir commands to show the files in a directory.
Con Hard to config
The configuration is mainly a file-based config, which can be unintuitive and difficult to use for new users.
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 A "me too" offering from MS, far behind other well established editors that it attempts to clone
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.
Con Slow launch time
Than it's competitors, e.g. Sublime Text.
Con Project search limits results
Because file search is so slow your results are limited in order to simulate a faster search.
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.