C# already provides many tools for your performance-critical code though. You can use pointers in unsafe. You can allocate unmanaged memory with Marshal. You can avoid copy with Span. You can even manually vectorise with Vector.IsHardwareAccelerated and such.
You can also distribute apps without .NET runtime with NativeAOT.
I'm sure there are people who want a C# without GC, but for me it's just... sufficient enough.
buybackofftoday at 8:26 PM
For C# as is, what I really would appreciate is a frozen GC mode. Not zero GC, similar to Epsilon GC in Java. After initial state loading and forced GC, I would like to be able to apply a SustainedNoGC mode, that just does not even try to collect, no scanning, no pauses at all, it can only allocate. And notifications (an event) after some X bytes allocated, or just a reliable way to monitor the allocated size. The existing modes such as SustainedLowLatency or NoGCRegion are good but not enough. For some low latency workloads it's OK to allocate many GBs and then pause explicitly.
Random forced pauses are the only problem that comes from GC, otherwise it's great for throughput and just a nice feature, as a sibling comment says. No GC languages do not make code magically faster, they still have malloc/free. However, GC is surrendering control over when a program may be paused.
bob1029today at 4:34 PM
The GC is a feature. Not a bug to be eliminated.
GC is not surrendering control. That seems to be HN's #1 bug bear. The sensation that someone or something is taking control away from you. The proper way to frame this is that you can actually focus on the original problem you set out to solve. Risking memory leaks is crazy when it's not something the customer is demanding. Even in gaming I think the GC is fine. There are ways to spread the impact across frames and bound the amount of time spent collecting.
If your clever scheme wouldn't work with a GC-managed heap, it probably won't work with one managed by hand either.
YuechenLitoday at 5:16 PM
So... What does this have over using NativeAOT which already exists?
Keep in mind a large portion of time NativeAOT is actually SLOWER than going through RyuJIT with the only definitive benefit being smaller binaries, and it's not like you can't do Span<T> and ref structs in modern C# for manual low level memory control already.
So my question is just... why?
hollowonepltoday at 4:37 PM
I’m not sure, the whole point of this language, standard libraries and runtime is built around GC. Nobody from C# world is educated or prepared to manually manage memory. This is just bare metal C++ with a lot of it stripped away and just nicer/cleaner syntax that does not inherit so much from C and POSIX archeology.
Nice POC, especially on MS-DOS but nothing truly relevant in the long run, I’m afraid
Dwedittoday at 5:46 PM
You really don't want to use C# with the "Bflat/Zero" runtime library. Even something very basic like strings is unsupported. It becomes C code with funny syntax that doesn't align well with the language.
I have not yet tested out Beef, but it seems to be more in line with what you'd want from a native C#-like language.
SuperV1234today at 8:15 PM
Cool project, I don't understand all the hate. This is great for gamedev and similar domains where latency matters
StilesCrisistoday at 4:40 PM
Why did they eliminate reflection? That doesn't need huge runtime support or garbage collection.
exceptionetoday at 6:36 PM
It builds on top of bflat, so there is a real non-vibed base there. Nice to see people take those type of bare metal efforts even further.
Pannoniaetoday at 5:31 PM
This thread feels like a bit of the old Dropbox thread ;)
"what is this useful for" - You want to write native code without a runtime or GC but you also don't want to deal with C++ with its arcane rules, edge cases, an awful dependency management story and complexity in general.
Rust is a good candidate for this as well, although it has quite a learning curve.
"you can already do this in standard C#" - Yes but the ecosystem assumes GC so you need to write everything yourself. There are some low allocation APIs but definitely not for everything. The concept of "C# but even lower level" is something which has a place, IMO. Just like how you can technically add assembly to C#, either by linking it with nativeAOT or emitting at runtime but it's not built-in support for inline assembly, you know.
Yeah, this is just a bunch of AI slop, but, ehhm... I really don't get all the CLR GC hate? Sure, if you're running a 24-months-ago Mono build, and your game performs like crap, I can sort-of sympathize, but otherwise?
Look, I'm all-in on CLR/C#, and one of my 'apps' is a 24/7 industrial camera monitoring system, and it has been running for the past, like, 3 months, on .NET 10 with "GCSettings.LatencyMode = GCLatencyMode.SustainedLowLatency" and "stackalloc" where needed, and...
Its performance, handling 8x ~800Mb/s streams has been... absolutely okay: 0 bytes over-allocated in the past 90 days (which is the last time my CoreOS-deployment auto-rebooted: all nodes are behind a VPN and outbound-only, so the latest OMG-CRITICAL-CVE doesn't really apply), so...
"If it works, it works"
ameliustoday at 4:22 PM
The "without any GC" part has me worrying. Is this advocating to just accumulate your garbage and throw it out only once every blue moon?
Also, does it ship with GUI libraries?
kvujtoday at 4:42 PM
Doesn't C# already support AOT compilation?
dosshelltoday at 4:29 PM
I like arena allocators, but some how i fel like reference counting would have been a better match for C# philosophy, like swift.
andyfilms1today at 4:13 PM
Finally, C--
jayd16today at 4:51 PM
Does this need a fork? Just pause the GC and use these patterns?
DeathArrowtoday at 5:38 PM
If you take GC out of C# and add arenas, why not use C or Zig already? If it's about the syntax, C's syntax is already similar.
pipeline_peaktoday at 5:14 PM
I’ve always wondered what C# would be like without GC. Yet without Reflection, there really isn’t anything meaningful here. It’s just nice syntax leftover.
luxuryballstoday at 5:06 PM
vote for calling it C# Zero or hmm Z#?
CAP_NET_ADMINtoday at 5:10 PM
In the age of LLMs and agentic coding - does the syntax even matter?
Do you even look at the code anymore?