Official proposal for Type Unions in C#

Re:Official proposal for Type Unions in C# by CharlieDigital on Wednesday August 07, 2024 @03:37PM (#41184588)

    A very common modern setup is PostgreSQL, C#/.NET, Linux & using JetBrains Rider for the IDE

You just described the startup I'm at. All devs are on Arm64 MacBooks and we deploy to Arm64 AWS T4g Linux instances. I'm all VS Code, others are primarily Rider.

.NET is a highly underrated platform for backend; it always puzzles me when teams think about moving from TypeScript to Rust or Go instead of C# because it seems a much smaller leap from TypeScript.

[ Parent | on HN ]

Re:Official proposal for Type Unions in C# by CBarkleyU on Wednesday August 07, 2024 @04:11PM (#41184902)

I'm itching to try and deep dive into go as a C# dev. I'm getting sick of enterprise C#, even if it is .NET8

I guess the grass is always greener somewhere

[ Parent | on HN ]

Re:Official proposal for Type Unions in C# by HideousKojima on Wednesday August 07, 2024 @04:56PM (#41185417)

Worst part for me about Go is how exceptions are usually basically handled the way that they would be with a Result<T> in Rust, but without an actual Result<T> type. That and how nulls are handled, feels like the worst of both worlds.

[ Parent | on HN ]

Re:Official proposal for Type Unions in C# by CharlieDigital on Wednesday August 07, 2024 @04:58PM (#41185439)

Maybe startup C# feels very different; it feels much more like TypeScript and I more or less write C# like I would write TypeScript.

[ Parent | on HN ]