h5
SharpKit
| h5 | SharpKit | |
|---|---|---|
| 5 | 1 | |
| 188 | 183 | |
| 5.3% | 0.0% | |
| 7.8 | 10.0 | |
| 3 months ago | over 3 years ago | |
| C# | C# | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
h5
-
.NET Blazor
Or similar for c# with https://h5.rocks (disclaimer: author here)
-
The compiler
A compiler is a program that can turn code written in one programming language into code written in another programming language. Like you say, they're used to convert code into machine code so that your computer can run it, but it's not limited to just that. They can be used to convert your code into any other programming language, even high-level ones. So you can totally compile your C# code into JavaScript if you're insane enough to do that.
- What is the development status of Bridge.net?
-
Has anyone had any luck with a C# to JavaScript transpiler?
It was recently forked into new project called h5: https://github.com/theolivenbaum/h5
SharpKit
-
.NET Blazor
At the very end of the blogpost the author asks why not compile C# to JavaScript, like F# (Fable) does? The author thinks that would be the best solution overall, and is surprised it has not happened yet.
In fact that has happened, see JSIL (http://jsil.org/, which compiles .NET bytecode to JS) and also SharpKit (https://github.com/SharpKit/SharpKit which is built on Roslyn).
But this will not necessarily be any better than compiling to wasm. It avoids the .NET interpreter, which decreases the download, but it will still need to bundle a lot of library support code. And getting the language semantics exactly right - including features like C# finalizers which do not have direct support in JS - is tricky, unlike with wasm. And it won't benefit from the speed of the wasm implementation in AOT mode (which Blazor supports), which can be much faster than JS.
Compiling to JS definitely still makes sense in some cases, but it isn't an idea that Microsoft or the .NET community has somehow overlooked. It has been done and it has its own tradeoffs.
What are some alternatives?
Bridge.NET - :spades: C# to JavaScript compiler. Write modern mobile and web apps in C#. Run anywhere with Bridge.NET.
BlazorDiffusionVue - Blazor Diffusion with Server Rendering and Vue
YantraJS - JavaScript Engine for .NET Standard Completely rewritten in C#
openapi-generator - OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)
tweetinvi - Tweetinvi, an intuitive Twitter C# library for the REST and Stream API. It supports .NET, .NETCore, UAP (Xamarin)...
sdk - Core functionality needed to create .NET Core projects, that is shared between Visual Studio and CLI
Telegraph - Telegraph app for desktop.
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
Sambal - A simple educational Win32 compiler project which makes EXE
Roslyn - The Roslyn .NET compiler provides C# and Visual Basic languages with rich code analysis APIs.
SimplCommerce - A simple, cross platform, modulith ecommerce system built on .NET