CSharpRepl
runtimelab
CSharpRepl | runtimelab | |
---|---|---|
14 | 53 | |
2,505 | 1,335 | |
- | 0.9% | |
8.3 | 4.6 | |
5 days ago | 2 days ago | |
C# | ||
Mozilla Public 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.
CSharpRepl
- Is .NET just miles ahead or am I delusional?
-
The best C# REPL is in your terminal
The C# REPL I'm talking about is simply called... C# REPL. It's an open-source project created by Will Fuqua, and as of today, it has over 2k GitHub stars. It is distributed as a .NET tool and is cross-platform. In this blog post, I'm going to show you how to install it on Windows Terminal, but you can install it on any terminal emulator you prefer.
-
It's 2023, so of course I'm learning Common Lisp
> The repl driven workflow is amazing and the lisp images are rock solid and highly performant.
do people not realize that basically everything vm/interpreted language has a repl these days?
https://www.digitalocean.com/community/tutorials/java-repl-j...
https://github.com/waf/CSharpRepl
https://pub.dev/packages/interactive
not to mention ruby, python, php, lua
hell even c++ has a janky repl https://github.com/root-project/cling
- How is C# interactive compared to F# REPL?
-
Short video on LINQPad AI
Let me introduce you to my lord and savior https://github.com/waf/CSharpRepl
-
Anyway to run LinqPad 7 with .net 8?
Not the answer you’re looking for, but I haven’t been able to run LinqPad since I moved to Mac OS. Polyglot notebooks plug-in for VS Code comes very close to LinqPad, or if you don’t mind Terminal/CommandLine csharprepl is amazing.
- Run C# Straight from Command line! (C# REPL)
- Run C# Straight from Commandline! (C# REPL)
- Best REPL for a language
-
On Repl-Driven Programming
For REPLs, there are options like (my own) https://github.com/waf/CSharpRepl which stand on top of the Roslyn compiler infrastructure, which is quite extensive and can easily evaluate standalone functions and statements.
It's still nowhere close to the REPLs of lisp and smalltalk, but it's a step in a more flexible direction.
runtimelab
- Green Thread Experiment in .NET
-
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.
What are some alternatives?
Cocona - Micro-framework for .NET console application. Cocona makes it easy and fast to build console applications on .NET.
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
replay-csharp - An editable C# REPL (Read Eval Print Loop) powered by Roslyn and .NET Core
DNNE - Prototype native exports for a .NET Assembly.
Gui.cs - Cross Platform Terminal UI toolkit for .NET
.NET-Obfuscator - Lists of .NET Obfuscator (Free, Freemium, Paid and Open Source )
rcf - RCF – a REPL-first, async test macro for Clojure/Script
FrameworkBenchmarks - Source for the TechEmpower Framework Benchmarks project
gui.cs - Cross Platform Terminal UI toolkit for .NET [Moved to: https://github.com/gui-cs/Terminal.Gui]
csharplang - The official repo for the design of the C# programming language
clojerl - Clojure for the Erlang VM (unofficial)