Official proposal for Type Unions in C#

Re:Official proposal for Type Unions in C# by vips7L on Wednesday August 07, 2024 @09:10PM (#41187125)

This is definitely all just a learning curve on how to do this. None of this is accurate at all.

- IntelliJ knows exactly what version of Java you want to run and develop against.

- Async is also trivial. Just fire off a virtual thread.

- it sounds like your company just picked a bad orm. Any good one is going to escape sql injection when binding variables. You are using binding right? If you to “write it in Java” there is also jOOQ.

The one thing I do think C# is far superior at is packaging and distribution. It’s beyond simple to package a C# application into stand alone binary, whether is be AOT or JIT.

[ Parent | on HN ]

Re:Official proposal for Type Unions in C# by sanex on Wednesday August 07, 2024 @11:48PM (#41187928)

I'm not worried about SQL invitation so much as I'd rather just query my C# objects instead of writing raw SQL. Yuck.

[ Parent | on HN ]

Re:Official proposal for Type Unions in C# by darby_nine on Thursday August 08, 2024 @09:30AM (#41191278)

Pretty much every language has some kind of monad-based query builder. The standardized syntax is nice though.

[ Parent | on HN ]

Re:Official proposal for Type Unions in C# by vips7L on Thursday August 08, 2024 @11:27AM (#41192565)

Java has that. It's just not the default choice because there is no default choice like in .NET. The options I know of: QueryDSL, jOOQ, Ebean with generated query beans.

[ Parent | on HN ]