When comparing UltraEdit 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 UltraEdit is ranked 30th. The most important reason people chose Visual Studio Code is:

JavaScript IntelliSense allows Visual Studio Code to provide you with useful hints and auto-completion features while you code.

Pros

Pro

Handles large files (>1GB) extremely well

UltraEdit has small memory usage and allows for fast parsing/searching when handling large files.

Pro

Works perfectly with remote files

Supports several protocols for accessing remote files and working on them with the same ease as local files. Files can be integrated in the projects as normal files.

Pro

Fast, stable, easy to use

Pro

Extremely customizable GUI editor

UltraEdit offer the best of both worlds. it has a full on GUI along with all the shortcut commands you need. There's no need for the user to suffer 80 char limitations of a terminal editor.

Pro

Highly flexible

UltraEdit allows you to handle groups of files as a project

Pro

Probably the most versatile general editor in existence.

If you need a general editor, UltraEdit is the way to go. If you were writing C/C++ all day, then this would be your editor. If you need to slog through large files then this is your go to editor. If you need to go through XML files, then this is your editor. If you need to sort data, then this your my editor.

Pro

JavaScript IntelliSense support

JavaScript IntelliSense allows Visual Studio Code to provide you with useful hints and auto-completion features while you code.

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

JS typechecking

Cons

Con

Proprietary

It's not free and a license costs $79.99.

Con

The themes introduced in version 20 regressed certain aspects of syntax coloring

The themes simplified the syntax highlighting which lost the capacity to have as many colors as one wanted to define. Now it is limited to around 20 different colors. In general it's not a problem but in certain cases it broke coloring.

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

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

Project search limits results

Because file search is so slow your results are limited in order to simulate a faster search.

Con

Very bad auto import

Con

Generalized

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

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

Is not an IDE, is a text editor

Con

Slow launch time

Than it's competitors, e.g. Sublime Text.

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.