MobileBlazorBindings
.NET Runtime
Our great sponsors
MobileBlazorBindings | .NET Runtime | |
---|---|---|
15 | 605 | |
1,186 | 14,047 | |
0.6% | 2.2% | |
2.3 | 10.0 | |
5 months ago | 3 days ago | |
C# | 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.
MobileBlazorBindings
-
MAUI going to all in on Blazor Hybrid.
It's difficult to imagine. But if the rumour has any merit, perhaps it simply means that there will be a push to consolidate on some blazor tech using stuff like https://github.com/dotnet/MobileBlazorBindings
-
What are your gripes with XAML?
There's Blazor Mobile Bindings but it's essentially experimental at the moment and isn't exactly active. From playing around with it though, it is pretty neat as you get the Blazor programming model but with native controls.
-
Clippy goes full cross-platform thanks to Avalonia UI framework
The benefit at least with the approach instead of embedding Avalonia inside Maui is you could potentially use non xaml frameworks for ui as long as they support Maui as a target. Stuff like Comet or Blazor mobile bindings would be possible aside from xaml. Especially if they're coming from Blazor web or code based ui frameworks like flutter which makes it appealing.
-
MAUI's potential hindered by inadequate maintainership
This is one reason I'd really love for them to push through on making alternatives to XAML like Blazor mobile bindings.
-
Is .net MAUI appropriate for a bachelor's thesis?
I'd say Blazor mobile bindings is also pretty interesting imo, unlike Hybrid it doesn't use Html and uses MAUI controls directly but still keeps the Blazor programming style and still uses razor to tie in C# and components.
-
Roundup of .NET MAUI. - Week of July 18, 2022
Oleksandr has been contributing to the official experiment project, and singlehandedly updated it to support .NET MAUI. He even now has documentation on his fork.
-
Anyone been trying out .NET MAUI?
I really hope Blazor Mobile Bindings takes off imo. I still care for native controls and if Mobile bindings does become a valid target, then you'll have an alternative to XAML when writing native components but using Razor syntax (which imo is less verbose). It'll be like how React does it (which is still pretty popular) where you have React web and also React Native which uses the platform's native controls underneath. Both aren't exactly the same but since the framework is similar (React, Blazor) it should be easy to swap between the two.
-
.NET MAUI Release Candidate – Ready for cross-platform app development
Yeah I really hope they'll productize Blazor Mobile Bindings (currently experimental), it's essentially using Xaml controls via Razor as the markup format instead and can use C# expressions (so less need for converters).
-
Blazor Mobile Bindings: Including Javascript files via <script> tag
For example, in Android there's this file: https://github.com/dotnet/MobileBlazorBindings/blob/main/templates/BlazorHybrid-app/NewApp.Android/wwwroot/index.html
-
Does MAUI support web somehow?
It means you can use Blazor's syntax to write MAUI apps, as an alternative to XML-like XAML syntax.
.NET Runtime
-
Java 23: The New Features Are Officially Announced
If you care about portable SIMD and performance, you may want to save yourself trouble and skip to C# instead, it also has an extensive guide to using it: https://github.com/dotnet/runtime/blob/69110bfdcf5590db1d32c...
CoreLib and many new libraries are using it heavily to match performance of manually intensified C++ code.
-
Locally test and validate your Renovate configuration files
DEBUG: packageFiles with updates (repository=local) "config": { "nuget": [ { "deps": [ { "datasource": "nuget", "depType": "nuget", "depName": "Microsoft.Extensions.Hosting", "currentValue": "7.0.0", "updates": [ { "bucket": "non-major", "newVersion": "7.0.1", "newValue": "7.0.1", "releaseTimestamp": "2023-02-14T13:21:52.713Z", "newMajor": 7, "newMinor": 0, "updateType": "patch", "branchName": "renovate/dotnet-monorepo" }, { "bucket": "major", "newVersion": "8.0.0", "newValue": "8.0.0", "releaseTimestamp": "2023-11-14T13:23:17.653Z", "newMajor": 8, "newMinor": 0, "updateType": "major", "branchName": "renovate/major-dotnet-monorepo" } ], "packageName": "Microsoft.Extensions.Hosting", "versioning": "nuget", "warnings": [], "sourceUrl": "https://github.com/dotnet/runtime", "registryUrl": "https://api.nuget.org/v3/index.json", "homepage": "https://dot.net/", "currentVersion": "7.0.0", "isSingleVersion": true, "fixedVersion": "7.0.0" } ], "packageFile": "RenovateDemo.csproj" } ] }
-
Chrome Feature: ZSTD Content-Encoding
https://github.com/dotnet/runtime/issues/59591
Support zstd Content-Encoding:
- Writing x86 SIMD using x86inc.asm (2017)
-
Why choose async/await over threads?
We might not be that far away already. There is this issue[1] on Github, where Microsoft and the community discuss some significant changes.
There is still a lot of questions unanswered, but initial tests look promising.
-
Redis License Changed
https://github.com/dotnet/dotnet exists for source build that stitches together SDK, Roslyn, runtime and other dependencies. A lot of them can be built and used individually, which is what contributors usually do. For example, you can clone and build https://github.com/dotnet/runtime and use the produced artifacts to execute .NET assemblies or build .NET binaries.
-
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...
-
Common Sorting Algorithms in C# - From My Experience
Orderby Linq Code Reference
-
The Mechanics of Silicon Valley Pump and Dump Schemes
The math of the above is really simple. Microsoft has 13,000 stars on their GitHub profile for their flagship product. SupaBase has 63,000 stars on their GitHub project for their flagship product. 27% of all software developers in the world are using .Net. SupaBase has 4.5 times as many likes as the .Net Core runtime, so they must be 4.5 times as large, right? 4.5 multiplied by 27% becomes 130%. Implying 130% of all software developers that exists on earth are using SupaBase (apparently!)
-
OpenD, a D language fork that is open to your contributions
> The amount of unsafe code used to implement C# vastly outweighs the amount in Rust's standard library.
According to bing.com chat, https://github.com/dotnet/runtime has 3.5M LOC, and https://github.com/rust-lang/rust has 6M LOC. The left panel of https://github.com/dotnet/runtime says 80% of the .NET runtime is written in C#.
This makes me wonder, do you happen to have a link for your “vastly outweighs” statement?
What are some alternatives?
Microsoft.Maui.Graphics - An experimental cross-platform native graphics library.
Ryujinx - Experimental Nintendo Switch Emulator written in C#
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.
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.
TwokaB - Blazor WebView control for WPF, Android, macOS, iOS. Run Blazor on .NET Core and Mono natively inside a Webview.
WASI - WebAssembly System Interface
toast_ui.blazor_calendar - Toast UI Calendar Wrapper For Blazor
CoreCLR - CoreCLR is the runtime for .NET Core. It includes the garbage collector, JIT compiler, primitive data types and low-level classes.
MetroLog - A lightweight logging system targeting .Net 6 and beyond.
vgpu_unlock - Unlock vGPU functionality for consumer grade GPUs.