I don't understand why the dotnet team doesn't invest more resources and time into tools: doctests and documentation generation, better and faster unit tests that I can write next to the actual code, easy access to the source code, no need to decompile a Dll to see it after pressing F12, a central place for packages and documentation like in pkg.go.dev or docs.rs . Most packages in nuget have no documentation at all, or only in readme format on GitHub, or a short Wiki on this page. Other environments like Rust, Golang, Java, Python are light years ahead when it comes to these aspects.
They are working on servo implementation, but it's long time to go.
Tauri has problem on Linux, webkit2gtk has lower performance etc. I know I have problems with three.js, others with svg
Additionaly communication speed between backend and frontend is bottleneck (serialisation to string) and you must use custom protocols to effectively communicate/send large data, zero copy binary protocol isn't possible at the moment
I don't know what to think about it. Half-baked idea: use free functions only in one file in project is meh..
Modern Kotlin, Scala, F# can and use free functions and reduce boilerplates to minimum. C# developers wants attract newbies, juniors, fans of J's, python etc and simultaneously don't disturb old users, fans of c#/java and enterprise development.
"It's only for quick scripts, prototyping, for teaching". Choose a side, don't pretend that you are modern and cool.
Modern c# is fine, but some features are only sugar, and yet i still waiting for proper sum types with exhausting pattern matching. Slow progressing java have this in 17 version..
No, i like Rust very much. But Rust require from me to deep dive with language, it's not productive language, it's correct from start to end language.
Language with optional GC, value types like Nim or D are better for small hobby projects. But community and library ecosystem and tooling are weak.
On other hand there are Ocaml and F#. But Ocaml for windows is weak, community is small etc F# inherits problems from c#
This have huge impact for go popularity. Alternative to Go:
- java and JVM language are heavy gorilla languages that's need more resources/ no value types. graal native is not straightforward alternative.
- C# is good alternative, but again jitted, and there are no alternative for Microsoft products in open source community,people choose go as default alternative to java few years ago..
-no sum types, Java 17, kotlin, scala, f#, typescript, rust, Swift, nim, ocaml etc all can modeling types better than C#
- no option, no result, exceptions are invisible for caller (ex. Tracking effects in nim)
-NRT doesn't resolve all problems, "required" is better, but I don't know if c# 10 will get it
- no let/val like kotlin, scala, rust. only readonly
- no expression based like kotlin/scala (or required initialization like in rust)
- no exhausting pattern matching
- most community are consumers of Microsoft libraries. Want small rest API framework? use asp.net core, want full stack? Use asp.net core. No other framework, even for rails is Sinatra.
- i would like to see better documentation frameworks with top level comments, doc tests, runnable examples like in rust, nim, d, and unit framework like in d or rust.
- no free functions, top level for only one file in project is too restrictive.
- no easy repl based work ( or community accepted)
From my newbie perspective c# is still good for few things, enormous resources for everything, only java from 'application' languages have more, generics, records, value types etc
C# has nothing like that, xml comments and raw documentation that has no value