runtimelab
Flee
Our great sponsors
runtimelab | Flee | |
---|---|---|
51 | 2 | |
1,323 | 587 | |
1.6% | - | |
5.1 | 0.0 | |
about 19 hours ago | about 2 years ago | |
C# | ||
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
-
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...
-
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.
- Java 21 makes me like Java again
-
The compact overview of JDK 21’s “frozen” feature list
Green Threads Experiment if anyone is interested in what they've done in .NET: https://github.com/dotnet/runtimelab/issues/2057
Personally Asyc/Await is the only thing keeping me from the C# ecosystem.
-
Question about NativeAOT platform support
There is a compiler being developed by the community (which is experimental and not supported by Microsoft) which supports full AOT: https://github.com/dotnet/runtimelab/tree/feature/NativeAOT-LLVM
Flee
-
.NET's AngouriMath now can be used from C++! (proof of concept version)
If I understand it correctly, can it replace this library ?
-
How to parse a string to source code inline
Off the top of my head, NCalc, Jace, and Flee. Probably others, but these are the ones I know of.
What are some alternatives?
DynamicExpresso - C# expressions interpreter
ncalc - Mathematical Expressions Evaluator for .NET
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
DNNE - Prototype native exports for a .NET Assembly.
FrameworkBenchmarks - Source for the TechEmpower Framework Benchmarks project
.NET-Obfuscator - Lists of .NET Obfuscator (Free, Freemium, Paid and Open Source )
csharplang - The official repo for the design of the C# programming language
Jace - Jace.NET is a calculation engine for the .NET platform.
Cocona - Micro-framework for .NET console application. Cocona makes it easy and fast to build console applications on .NET.
CoreWCF - Main repository for the Core WCF project
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.
Graal - GraalVM compiles Java applications into native executables that start instantly, scale fast, and use fewer compute resources 🚀