Some Things

[xqb-dpx]

Hello everyone,

I’m still a beginner in C#, so please take this as a friendly discussion rather than criticism.

There are a few thoughts I’ve been reflecting on, and I’d love to hear your opinions:

---

1. Performance and Abstraction Level

C# is often described as a high-level language that’s relatively slower compared to newer system-level languages like Rust or Go.
However, with modern technologies like .NET JIT, AOT, and NativeAOT, performance has improved dramatically — though it still consumes more memory due to the Garbage Collector.

That said, I wonder if C# could evolve further by:

Optimizing core APIs and frameworks for lightweight execution, and

Simplifying syntax (e.g., allowing Write() instead of Console.Write() in simple contexts).

It’s more about improving developer flow without losing clarity.

---

2. Framework Accessibility

Frameworks like Blazor Hybrid are powerful but come with steep learning curves and significant setup requirements.
While this complexity makes sense given its full-stack nature, it sometimes feels less practical compared to frameworks in other ecosystems — like Rocket in Rust, which prioritizes speed and simplicity.

Maybe the C# ecosystem could benefit from lighter, modular frameworks that lower the entry barrier while maintaining performance and productivity.

---

3. Modular C# Ecosystem

Personally, I think it would be exciting if C# evolved into more domain-focused “flavors,” for example:

C# Hardware (Arduino, IoT, embedded modules)

C# Web (full-stack, cloud-native)

C# Quantum (Q#, simulation, Azure Quantum)

C# Game (Unity, Unreal, high-performance rendering)

C# App (WF, WPF, cross-platform UI)

C# Network (socket-level, distributed computing)

Each could be an optimized environment with specific libraries and templates preconfigured, helping developers dive directly into their domain.

---

4. About QDK (Quantum Development Kit)

Why was QDK support removed from Visual Studio?
It used to be an interesting gateway to quantum programming. I hope it returns.

[DrkWzrd]

C# being slower than python? Let me doubt about that.

[DrkWzrd]

Simplifying syntax (e.g., allowing Write() instead of Console.Write() in simple contexts).

Are you really asking for saving 7 keystrokes? Furthermore, you add ambiguity with this. There are so many classes that have "Write" method and family (streams, writers, pipes...)

You have to remember that you can write a single (executable by a simple console/bash dotnet run xxx.cs) .cs file app without any of the ceremony of creating a class and a 'Main' method.
These things would have been unthinkable 4? years ago.

Java is dreaming about it, right now, in 2025. And this is the closer they can reach:

class HelloWorld {
    void main() {
        System.out.println("Hello, world!");
    }
} //look what they need to mimic a fraction of our power!

Excuse me, but right now, writing c# simple apps is easier than ever, and is (in my opinion) easier than scripting in python. At least, here we have ; and we don't have to be bothered by the identation (fully personal opinion).

PS.: this should be in discussions.

[huoyaoyuan]

C# and .NET have evolved quickly in recent years. It's really not sufficient to discuss C# without more knowledge.

C# is often described as a high-level language that’s relatively slower compared to newer system-level languages like Rust or Go.

This is a misunderstanding that I don't understand why people are continuously posting. Go is not new (2011), nor system-level (requires GC), nor fast.

though it still consumes more memory due to the Garbage Collector.

No, GC won't always consume more memory. It would only consume more if the strategy were set to maximize performance, but it can also consume less because of the ability to move objects and compact the memory between them.

Optimizing core APIs and frameworks for lightweight execution

This has been happening for every release. We are always attentive about startup performance. The .NET 10 SDK introduces single-file mode without project file, and a gradual upgrade path to full project.

Simplifying syntax (e.g., allowing Write() instead of Console.Write() in simple contexts).

This has already been enabled in C# 6 (2015), with using static. C# 10 (2021) further optimizes this. It's just the SDK that decides to not provide this in-box.

Frameworks like Blazor Hybrid are powerful but come with steep learning curves and significant setup requirements.
While this complexity makes sense given its full-stack nature, it sometimes feels less practical compared to frameworks in other ecosystems — like Rocket in Rust, which prioritizes speed and simplicity.

Blazor Hybrid is complex by its nature - the "hybrid" in its name means combination with browser and native contents. Rocket in Rust is a pure backend server. It should be compared with ASP.NET.

Personally, I think it would be exciting if C# evolved into more domain-focused “flavors,

Each could be an optimized environment with specific libraries and templates preconfigured, helping developers dive directly into their domain.

Each domain has its specific requirement and community. There's nothing much to do in the base runtime and common libraries, and up to each environment to provide optimization.

4. About QDK (Quantum Development Kit)

This is an unrelated topic. Q# is not a native CLR language.