runtimelab
maui-linux
Our great sponsors
runtimelab | maui-linux | |
---|---|---|
52 | 31 | |
1,329 | 789 | |
1.1% | - | |
5.1 | 0.0 | |
1 day ago | 6 days ago | |
C# | ||
MIT License | 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.
runtimelab
-
Is .NET just miles ahead or am I delusional?
There was a "green thread" experiment for dotnet a while ago, here is the conclusion: https://github.com/dotnet/runtimelab/issues/2398
-
Why choose async/await over threads?
Experiment result write-up: https://github.com/dotnet/runtimelab/blob/e69dda51c7d796b812...
TLDR: The green threads experiment was a failure as it found (expected and obvious) issues that the Java applications are now getting to enjoy, joining their Go colleagues, while also requiring breaking changes. It, however, gave inspiration to subsequent re-examination of current async/await implementation and whether it can be improved by moving state machine generation and execution away from IL completely to runtime. It was a massive success as evidenced by preliminary overhead estimations in the results.
-
Garnet – A new remote cache-store from Microsoft Research
Yeah, it kind of is. There are quite a few of experiments that are conducted to see if they show promise in the prototype form and then are taken further for proper integration if they do.
Unfortunately, object stack allocation was not one of them even though DOTNET_JitObjectStackAllocation configuration knob exists today, enabling it makes zero impact as it almost never kicks in. By the end of the experiment[0], it was concluded that before investing effort in this kind of feature becomes profitable given how a lot of C# code is written, there are many other lower hanging fruits.
To contrast this, in continuation to green threads experiment, a runtime handled tasks experiment[1] which moves async state machine handling from IL emitted by Roslyn to special-cased methods and then handling purely in runtime code has been a massive success and is now being worked on to be integrated in one of the future version of .NET (hopefully 10?)
[0] https://github.com/dotnet/runtime/issues/11192
[1] https://github.com/dotnet/runtimelab/blob/feature/async2-exp...
-
Java virtual threads hit with pinning issue
Unlike these folks from dotnet, which tested directly on ASP for real workload
https://github.com/dotnet/runtimelab/issues/2398?darkschemeovr=1
-
Ask HN: Do we have evidence that green threading is faster than OS threads?
[1] https://github.com/dotnet/runtimelab/issues/2398
-
JEP Draft – Derived Record Creation (Preview) – Java
The only way to avoid it is to not build on top of Java or not adding any features on top of Java.
> To give another example with C#, there has been a lot of recent discussion about finding potential alternatives to their async-await concurrency model. They cite the level of effort it takes to maintain the async await style code and the costs that come from this.
I had a very different take-away. They did PoC with virtual threads and decided it's not worth the switch now and async-await that they have is good enough.
https://github.com/dotnet/runtimelab/issues/2398
> Some of the languages it gets compared too aren't even that old yet.
C# is old enough to drink and Scala just had its 20th birthday this week :)
-
.NET 8 – .NET Blog
It was tried and the dotnet team decided to drop it: https://github.com/dotnet/runtimelab/issues/2398
-
.NET Green Thread Experiment Results
Technical details here: https://github.com/dotnet/runtimelab/blob/feature/green-thre...
-
Thread-per-Core
Just last month .NET ended a green threading experiment, mainly because the overhead it adds to FFI was too high:
https://github.com/dotnet/runtimelab/issues/2398
Rust had green threads until late 2014, and they were removed because of their impact on performance.
Everyone has done the basic research: green threading is a convenient abstraction that comes with certain performance trade offs. It doesn't work for the kind of profile that Rust is trying to target.
- Green Thread Experiment Results
maui-linux
-
What's New in Final RC for .NET 8, .NET MAUI, Asp.net Core and EF8
While this is the quite endorsed by the community: https://github.com/dotnet/maui/discussions/339
I think the fundamental issue is that desktop Linux is way too fragmented. Not only just GTK2/3 and Qt but you have GNOME, KDE, XFCE, Cinnamon and then you have X11, Xorg, Wayland...
To be honest, all those craps are why desktop Linux never took off. I'm very safe to say MAUI for Linux will eventually renders components off its own using framebuffer and hardware acceleration APIs such as OpenGL or Vulkan just because of the market fragmentations...
If desktop Linux truly wants to get the attention, it will need to unify. Fixing dependency hell using Flatpak is the right direction.
There is an existing old fork of MAUI for Linux that uses GTK: https://github.com/jsuarezruiz/maui-linux
-
Tauri Mobile – Develop Mobile Apps with JavaScript and Rust
There is work being done to address desktop linux, but I agree that is one of the deficiencies.
https://github.com/jsuarezruiz/maui-linux/pull/37
The lack of a WASM target is another, although UNO project in the past provided such a target for MAUI's very closely-related predecessor (Xamarin.Forms).
-
Announcing .NET 7 Release Candidate 1
That's more on the fact that there's no official set of native UI in Linux since MAUI uses the platform's native UI instead of drawing everything themselves like Flutter, there have been some community works around this via this repo using GTK as the native UI to target. This is the same case for say React Native where most Linux implementation will likely use Electron as a shell since there's no standard set of platform UI components to choose.
- .NET MAUI on Linux Makes Progress
-
"Microsoft and Canonical announce native .NET availability in Ubuntu 22.04 hosts and containers" – yeah, very nice, but there's still no cross-platform way to build graphical .NET apps, right?
There's even a senior engineer at Microsoft who's done some exploratory work on Linux bindings already: https://github.com/jsuarezruiz/maui-linux
- Will we ever get a new CLR language to replace C# Like Kotlin did for Java?
-
Dont u just love ur job as a dev in c#
https://github.com/jsuarezruiz/maui-linux exists but appears to be inactive lately
-
What options exist for creating (simple) GUI applications on Linux?
The applications I'm trying to make all require relatively simple GUI, only needing images, text-boxes, buttons, and basic configuration menus. I have heard of maui-linux however I'm very new to all of this and not sure how to make use of it at all.
- How quickly and efficiently do you believe Linux will get support for MAUI apps?
-
Introducing .NET MAUI – One Codebase, Many Platforms
Kudos to Microsoft and the teams (.Net, etc.) that made this possible! This is really big! What's the team's plan to extend MAUI to Linux? This is key, considering it was the platform that set the cross-platform (xPlat) .Net in motion, where Mono, MonoDevelop (now Visual Studio for Mac), among others, were bred. For example, is it possible to officially support an MAUI implementation for Linux modelled around Gtk? Like what has already been started here? Linux had so much love during the Mono/Xamarin days and has continued to enjoy same as .Net Core (now .Net all across) matures into being genuinely cross-platform. Linux's support will really be a game-changer! MAUI will then be "One Codebase, Many Platforms", indeed! Thanks once again for all the work on MAUI. It's awesome!
What are some alternatives?
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
Introducing .NET Multi-platform App UI (MAUI) - .NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.
DNNE - Prototype native exports for a .NET Assembly.
Avalonia - Develop Desktop, Embedded, Mobile and WebAssembly apps with C# and XAML. The most popular .NET Foundation community project.
.NET-Obfuscator - Lists of .NET Obfuscator (Free, Freemium, Paid and Open Source )
Uno Platform - Build Mobile, Desktop and WebAssembly apps with C# and XAML. Today. Open source and professionally supported.
FrameworkBenchmarks - Source for the TechEmpower Framework Benchmarks project
Eto.Forms - Cross platform GUI framework for desktop and mobile applications in .NET
csharplang - The official repo for the design of the C# programming language
managed-midi - [Past project] Cross-platform MIDI processing library for mono and .NET (ALSA, CoreMIDI, Android, WinMM and UWP).
Cocona - Micro-framework for .NET console application. Cocona makes it easy and fast to build console applications on .NET.
QtSharp - Mono/.NET bindings for Qt