Nim vs ASP.NET MVC
When comparing Nim vs ASP.NET MVC, the Slant community recommends Nim for most people. In the question“What is the best programming language to learn first?” Nim is ranked 22nd while ASP.NET MVC is ranked 61st. The most important reason people chose Nim is:
There are generics, templates, macros in Nim. They can allow you to write new DSL for your application, or avoid all boilerplate stuff.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Great metaprogramming features
There are generics, templates, macros in Nim. They can allow you to write new DSL for your application, or avoid all boilerplate stuff.
Pro Strict typing
Checks your code at compile time.
Pro Has built-in unittest module
With built-in "unittest" module you can create test with a very readable code.
Pro Has built-in async support
Nim has "asyncdispatch" module, which allows you to write async applications.
Pro Compile-time execution
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.
Pro Really cross-platform
The same code can be used for web, server, desktop and mobile.
Pro Easy to read
Nim has a lot of common with Python in terms of syntax. Indentation-based syntax, for/while loops.
Pro Multi paradigm
Imperative, OOP, functional programming in one language.
Pro Easy to integrate with another languages
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).
Pro Garbage-collected
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.
Pro Type interferencing
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).
Pro Built-in Unicode support
You can use unicode names for variables, there is "unicode" module for operations with unicode.
Pro Supports UFCS (Unified Function Call Syntax)
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()
Pro Mature
The framework has many build-in tools, and many packages have been written targeting the framework.
Pro Cross platform
.Net Core can work on any platform.
Pro Widely used
It's pretty easy to find a job with it and there's plenty of documentation and tutorials around.
Pro Extensive documentation
There are a lot of resources available to get help.
Pro Fast
Asp.NET Core on Linux is fast accordingly to TechEmpower benchmarks.
Pro Asp.NET core provides balance between magic/agility and craftsmanship
You can get ordinary details quickly but with complete freedom to make your craft, knowing everything that is happening underneath the cloths. The highly modular system makes it possible to scale small applications to large ones with ease.
Pro It has more users than any other backend web framework
Getting your next contract is easy with this on your CV.
Cons
Con Core and full ASP.NET are bit confusing sometimes
While not in feature parity (yet) they are still apart and support sometimes funky combinations of features - full ASP.NET has all the bells and whistles but doesn't offer cross platform so you may have to do some research what you really need. That being said, it got a lot better in 2.0.
Con Expensive
You need to have the plate to maintain a site.
Alternative Products
