When comparing Textnut vs Visual Studio Code, the Slant community recommends Visual Studio Code for most people. In the question“What are the best Markdown editors for OS X?”Visual Studio Code is ranked 10th while Textnut is ranked 24th. The most important reason people chose Visual Studio Code is:

Visual Studio Code comes fairly complete out of the box, but there are many plug-ins available to extend its functionality.

Pros

Pro

Can automatically convert Markdown to rich text

TextNut has two modes that it can switch between on-the-fly - Markdown and rich text editing mode. In rich text editing mode Markdown syntax is automatically converted to rich text. For example, typing ***bold*** will automatically convert it to bold. In Markdown mode syntax will be kept (with chosen styling applied).

Pro

Advanced yet easy way to add images

Images can be added by writing a curly brace ({) anywhere in the text and a popup will appear that will allow dragging and dropping the image in as well as customize the parameters without having to remember the proper syntax.

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

Good support for new Emmet syntax

Ad

Cons

Con

Rich text editing mode has incomplete Markdown support

Some Markdown elements don't convert to rich text in rich text editing mode. For example, for emphasis only * will convert, _ will be left as is.

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

Is not an IDE, is a text editor

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

Very bad auto import

Con

Project search limits results

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

Con

Slow launch time

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

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

Memory hog

Allegedly, VS Code is "lightweight". Yet, running multiple instances of it at once, you may get many "out of memory" messages from Windows despite 16 GB RAM. (While of course also running other things. The point is the comparison with some other IDEs/editors where running them alongside the same number of other applications doesn't cause Windows to run out of memory)

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

Have no good default js style analyzer

In WebStorm there is analyzer that checks for warnings and highlight this in yellow, here you 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.

Con

.sass linting is terrible

Alternative Products

Each month, over 2.8 million people use Slant to find the best products and share their knowledge. Pick the tags you’re passionate about to get a personalized feed and begin contributing your knowledge.