Our great sponsors
-
-
Roslyn
The Roslyn .NET compiler provides C# and Visual Basic languages with rich code analysis APIs.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
you can write pure TS: https://github.com/microsoft/TypeScript/issues/14833
"Everything is mutable" not really, to me this is more like a library problem like EF-core rely on property to be mutable so you can't use record for EF. This is C# rationality on deciding to not support immutable/readonly var, and there is (proposal)[https://github.com/dotnet/csharplang/issues/188] for readonly var already, we just don't know if it's ever became a feature; for me it's more like a programming discipline anyway; The lambda with property are just syntactic sugar, nothing more. I get it you like it short, but C# are much older than Kotlin, it can't have all the nice, nifty trivial syntax kotlin has. (x) => x.Prop is a little bit more verbose, but clean enough in my opinion, and their support can be added later (though not necessary). Despite C# is old, it has nullable type as well, begin with nullable struct since net framework 2 (2005). Nowadays C# has nullable for reference type as well, although it's just compiler service since ref type are nullable, but you can absolutely make C# null safety just as strict as Kotlin. I do that too. Saying C# "what's a struct and what's a class" is weak.
"Everything is mutable" not really, to me this is more like a library problem like EF-core rely on property to be mutable so you can't use record for EF. This is C# rationality on deciding to not support immutable/readonly var, and there is (proposal)[https://github.com/dotnet/csharplang/issues/188] for readonly var already, we just don't know if it's ever became a feature; for me it's more like a programming discipline anyway; The lambda with property are just syntactic sugar, nothing more. I get it you like it short, but C# are much older than Kotlin, it can't have all the nice, nifty trivial syntax kotlin has. (x) => x.Prop is a little bit more verbose, but clean enough in my opinion, and their support can be added later (though not necessary). Despite C# is old, it has nullable type as well, begin with nullable struct since net framework 2 (2005). Nowadays C# has nullable for reference type as well, although it's just compiler service since ref type are nullable, but you can absolutely make C# null safety just as strict as Kotlin. I do that too. Saying C# "what's a struct and what's a class" is weak.
Gleam might be the language for you then