That's why WebAssembly was created

[sujonkumar6300]

WebAssembly
Increasingly, JavaScript has been playing two distinct roles: one as a programming language, and one as a transpilation target — that is, if you have code in language X and you want to run it in the browser, you use a transpiler that “translates” your code into JavaScript. As you can imagine, this is not an optimal solution.

which consists of a new binary code format that works as a compilation target for other languages ​​and can be executed by the browser's JavaScript engine. The advantage of having a code format expressly designed for this purpose is that it allows it to be extensively optimized so that its execution is very fast. So you can have JavaScript bolivia consumer email list code that can transparently interact with components programmed in other languages ​​(for example C++ or Rust) that have very high performance and take advantage of low-level hardware capabilities. Currently WebAssembly is supported in Chrome and Firefox, and it is expected to be supported in Safari and Edge before the end of the year.

NET Core 2 y .NET Standard 2
Microsoft officially released version 2 of the .NET Core SDK, and jointly released version 2.0 of .NET Standard.

If you’re not clear on what this means, here’s a breakdown: In 2016, in an effort to enable developers to use the .NET Framework to build apps for different platforms, Microsoft decided to support different implementations of .NET, including the .NET Framework (Windows), .NET Core (cross-platform and open source), and Xamarin (mobile-focused). To facilitate portability, an abstract layer called .NET Standard was defined that basically specifies the APIs that should be supported across different .NET implementations. Initially, .NET Standard defined less than 10 thousand APIs (extracted from the .NET Framework on Windows) that should be supported, and this has grown until version 2.0 of the .NET Standard specifies around 32 thousand APIs.