TypeScript vs Nim

Typescript has optional static typing with support for interfaces and generics, and intelligent type inference.

It makes refactoring large codebases a breeze, and provides many more safeguards for creating stable code.

Lot of benefits of it, you can read this.

Every existing Javascript program is already a valid TypeScript program giving it the best support for existing libraries, which is particularly useful if you need to integrate with an existing Javascript code base.

As a Microsoft developed project, it has first party Visual Studio support that's on par with its C# support with features like syntax sensitive statement completion.

There are many ready to use and high quality TypeScript definitions for popular libraries including jquery, angular, bootstrap, d3, lodash and many-many more.

Typescript enables familiar object-oriented programming patterns: classes, inheritance, public/private methods and properties, et cetera.

Typescript implements the fat arrow syntax, which always maintains the current context for this and is a shorter/more convenient syntax than traditional function definition.

Strongly typed react components, so UI "templating" automatically gains type safety.

Both can call Javascript code and be called by Javascript code. Making transitioning to the language very easy.

Compiles to simple looking Javascript making it easy to understand what is happening and learn the language (if you already know Javascript).

Being built by Microsoft, TypeScript is much more likely than most other similar open-source projects to receive continued long-term support, good documentation, and a steady stream of development.

TypeScript has a clear and defined roadmap with rapid and constant releases.

TypeScript's built-in type signatures allow developers to fully document interfaces and make sure that they will be correctly compiled. Therefore, cutting down on logical errors.

Angular 2 is built using TypeScript and applications built using it can make use of that (or not).

There are generics, templates, macros in Nim. They can allow you to write new DSL for your application, or avoid all boilerplate stuff.

Checks your code at compile time.

With built-in "unittest" module you can create test with a very readable code.

Nim has a built-in VM, which executes macros and some other code at compile time. For example, you can check if you're on Windows, and Nim will generate code only for it.

Nim has "asyncdispatch" module, which allows you to write async applications.

The same code can be used for web, server, desktop and mobile.

Nim has a lot of common with Python in terms of syntax. Indentation-based syntax, for/while loops.

Imperative, OOP, functional programming in one language.

You can use Nim with any language that can be interfaced with C. There's a tool which helps you to create new C and C++ bindings for Nim - c2nim.
Also, you can use Nim with Objective C or even JavaScript (if you're compiling for these backends).

You don't need to deal with all those manual memory allocations, Nim can take care of it. But also you can use another GC, or tweak it for your real-time application or a game.

You only need to specify types in your procedures and objects - you don't need to specify type when you're creating a new variable (unless you're creating it without initialization).

You can use unicode names for variables, there is "unicode" module for operations with unicode.

writeLine(stdout, "hello") can be written as stdout.writeLine("hello")
proc add(a: int): int = a + 5 can be used like 6.add.echo or 6.add().echo()