Bflat: C# as you know it but with Go-like tooling

Re:Bflat: C# as you know it but with Go-like tooling by GiorgioG on Friday June 25, 2021 @03:35PM (#27635271)

The reason you don't see many projects written in C# is that there are far fewer open source C# projects than Java/Go/etc. Most C# is written in-house (enterprises, some startups (admittedly relatively few.))

I've been a .NET Dev for 20 years. C# keeps trucking along adding features at neck-breaking pace. That can be good and bad. Personally I wish F# had more resources assigned to it at MS. Having said that C# seems to be getting more and more F# features as time goes on.

I did a small amount of Java in my career, and learned golang on my own time. Neither clicked with me or swayed me to consider a move to full-time employment using those langs. I've been learning Rust most recently and I'm considering looking for a job doing Rust.

[ Parent | on HN ]

Re:Bflat: C# as you know it but with Go-like tooling by ska on Friday June 25, 2021 @03:40PM (#27635333)

> Personally I wish F# had more resources assigned to it at MS.

This absolutely. Or that they had avoided the usual NIH MS is prone to, and just supported another ML variant (thus reducing the load to match the resourcing).

[ Parent | on HN ]

Re:Bflat: C# as you know it but with Go-like tooling by tasogare on Friday June 25, 2021 @11:47PM (#27638906)

Other ML aren't compatible with the CLR type system. That was the main point of porting Ocaml to .NET.

[ Parent | on HN ]

Re:Bflat: C# as you know it but with Go-like tooling by ska on Saturday June 26, 2021 @02:18PM (#27644406)

Same problem with CL. But I can think of a better way to fix it :)

[ Parent | on HN ]