ASP.NET Core vs V
When comparing ASP.NET Core vs V, the Slant community recommends V for most people. In the question“What are the best programming languages for concurrent programming?” V is ranked 8th while ASP.NET Core is ranked 12th. The most important reason people chose V is:
V is easier than C and fast like C.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Fast and getting faster
Thanks to breakthroughs in ROSLYN compiler and the efforts of the .NET COre developer team, code written in C# can reach speeds just a step behind C++.
Pro Multi platform
Can run on Windows, Linux and Mac (also Visual Studio Code editor).
Pro Hosting
Ability to host on IIS, Nginx, Apache, Docker, or self-host in your own process.
Pro Ease of Use
Pro Security
It is a very secure platform.
Pro Built-in middleware
Built-in middleware featuring: Authentication, Cookie policy, Health Check, MVC, Session etc.
Pro Tooling
Both VS and VSCode are powerful free IDEs that are well integrated with ASP.net Core. VS Community also allows for commercial use for projects with less than 5 developers.
Pro JSON optimization
In .NET Core 2.1 and 3.0, new APIs are added that make it possible to write JSON APIs that require less memory, using Span<T> and UTF8 strings, and improve throughput of applications like Kestrel, ASP.NET Core web server. See also Utf8JsonReader.
Pro Tutorials and documentation quality
Both microsoft and 3rd party tutorials are mostly of high quality and encourage you to use the industry best-practices.
Pro Fast like C
V is easier than C and fast like C.
Pro Simplicity
V is simple and powerful.
Pro Generics
V has generics.
Pro Sum types
V has Sum Types.
Pro Single paradigm
Follows the philosophy that there should be only one way to do something, as opposed to multi-paradigm languages like C++.
Pro Closures
V has closures, which gives the user additional options and usefulness.
Pro Safety
V is very safe.
Pro C Interop
Can import C libraries, structs, and headers.
Pro Supports concurrency and channels
Can run functions concurrently that communicate over channels.
Pro Cross-platform
Compile to many OSes.
Pro Clear syntax
Highly understandable language.
Pro Can create multi-OS GUIs
Multi-OS GUI creation is more integrated into the language than others.
Pro Inline assembly
Can add Assembly code.
Cons
Con Microsoft environment
Con The author of the language is an expert con artist
The only reason Vlang has any kind of funding is that it has a lot of dummy repositories that promise a lot of performance to the user (like Gitly, UI, Vinix, Viscord, Vbrowser, DOOM written in V, gg ...), when there is nothing to deliver in the first place. The author of V has a history of overpromising things, has claimed that the language has insane features when it didn't. Having a plain look at their README will give the right idea for someone with programming experience.
Con V 1.0 release was planned for December 2019
Con Highly questionable "Fake it till you make it" marketing
Large parts of what they describe as their "key features" on their website is actually goals, not something they currently deliver. It's also something they never will deliver, because it's impossible to do so. The goals themselves are hyped and unrealistic, and until they have a working prototype delivering the claims (which is largely considered to be impossible by the community), the claims are just lies.
Built By the Slant team
Lustre recommends the best products at their lowest prices – right on Amazon.