JSIL VS Eto.Forms

JSIL

JSIL is an open source compiler that turns .NET applications, written in C# or VB.NET, into fast readable JavaScript.

Eto.Forms

Cross platform, .NET-based desktop and mobile user interface framework.

Landing page //
2022-12-09

Landing page //
2023-09-09

JSIL

Website: jsil.org
$ Details: -

Edit details

Eto.Forms

Website: github.com
$ Details

Edit details

JSIL features and specs

No features have been listed yet.

Eto.Forms features and specs

Cross-Platform Support
Eto.Forms allows developers to create single-source code for building cross-platform desktop applications that run on Windows, Mac, Linux, and mobile platforms using Xamarin.
Native Look and Feel
The framework uses native controls on each platform, providing a native look and feel and better performance compared to other cross-platform solutions that emulate GUI components.
Easy Integration
Eto.Forms can be easily integrated with existing projects. It allows mixing of Eto.Forms interfaces with platform-specific code when needed.
Active Community
The project is open-source and has a community of users and contributors who actively maintain and enhance the framework, ensuring it stays updated with current technologies.
Customizable
The framework allows for extensive customization and styling of UI components, enabling developers to tailor applications to specific design requirements.

Possible disadvantages of Eto.Forms

Learning Curve
Developers not familiar with the Model-View-Presenter (MVP) pattern or cross-platform GUI paradigms might experience a steeper learning curve when starting with Eto.Forms.
Limited Resources
Compared to more popular frameworks, Eto.Forms has limited tutorials, examples, and third-party libraries, which might make it harder for developers to find solutions or resources.
Lack of Advanced Features
Some advanced GUI features provided by other frameworks might not be available in Eto.Forms, which can limit the development of highly complex interfaces.
Platform-Specific Limitations
There can be differences in functionality or appearance due to reliance on native controls, potentially leading to additional platform-specific tweaks or workarounds.
Performance Overhead
While using native controls improves performance, the abstraction layer introduced by Eto.Forms could add a slight overhead compared to using platform-specific code directly.

Category Popularity

0-100% (relative to JSIL and Eto.Forms)

Eto.Forms

Development Tools

52 52%

Development Tools

48% 48

Website Builder

45 45%

Website Builder

55% 55

No Code

47 47%

No Code

53% 53

Application Builder

100 100%

Application Builder

0% 0

User comments

Share your experience with using JSIL and Eto.Forms. For example, how are they different and which one is better?

Social recommendations and mentions

Based on our record, JSIL seems to be more popular. It has been mentiond 2 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.

JSIL mentions (2)

.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... - Source: Hacker News / almost 2 years ago
.NET Blazor
There actually are several C# to JavaScript transpilers out there but none are well-maintained with a strong following (compared to Fable). Some examples are... https://github.com/theolivenbaum/h5 https://www.infoq.com/news/2015/02/duocode-csharp-javascript/ http://jsil.org I wonder if the community just isn't interested in this approach. - Source: Hacker News / almost 2 years ago