3 ms·

> Orleans builds on the developer productivity of .NET As someone who has developed with .NET (using VB, C#, F#) for almost 15 years, I am not sure if I would

> Orleans builds on the developer productivity of .NET As someone who has developed with .NET (using VB, C#, F#) for almost 15 years, I am not sure if I would still advertise .NET as something focused on developer productivity, when in the context of introducing bleeding edge tech. It is a great framework, but I've found much more productivity with Elixir after just 1 year of using it. C# still suffers from statefulness, null references, and boilerplate code, even after newer versions of the language provide some tools to reduce those. F# is a good alternative to C# if you want to stay in the .NET ecosystem and reap the benefits of functional programming, but I found the compiler to be very slow, 3rd libraries poorly documented, the language excessively complex, and 3rd party IDE support to be limited (as of version 2.0 anyway). Is developer productivity still a focus of .NET?

lwansbrough 6y ago
Asking developers to learn an entirely new language or ecosystem isn't exactly my idea of productive. ;)
x0n 6y ago
I think maybe you stepped out of .net at the wrong time. Pattern matching, records, discriminated unions (c# 10) etc are here and on they way. Lots of functional features being integrated into C# with every update.
- ricksharp 6y ago
  I’ve been using C# since 2003, but I’m still 5 times faster in typescript & react. Besides that the typescript type system is insane. It’s cool to hear about discriminated unions though.
  - x0n 6y ago
    The more haste, the less speed! Yeah, I get ya. Love me some typescript.
- atraac 6y ago
  I'm using new c#/.net core professionally and I still think it's far less productive than elixir/phoenix in general. Also c#'s pattern matching is nothing when compared to elixir ones. They are very different languages though and that's fine, most people are familiar with OO, not with FP so for them, it might be more productive(at least in certain types of applications).
tasogare 6y ago
> null references This is addressed since C# 8.

lwansbrough 6y ago

Asking developers to learn an entirely new language or ecosystem isn't exactly my idea of productive. ;)

x0n 6y ago

I think maybe you stepped out of .net at the wrong time. Pattern matching, records, discriminated unions (c# 10) etc are here and on they way. Lots of functional features being integrated into C# with every update.

ricksharp 6y ago
I’ve been using C# since 2003, but I’m still 5 times faster in typescript & react. Besides that the typescript type system is insane. It’s cool to hear about discriminated unions though.
- x0n 6y ago
  The more haste, the less speed! Yeah, I get ya. Love me some typescript.
atraac 6y ago
I'm using new c#/.net core professionally and I still think it's far less productive than elixir/phoenix in general. Also c#'s pattern matching is nothing when compared to elixir ones. They are very different languages though and that's fine, most people are familiar with OO, not with FP so for them, it might be more productive(at least in certain types of applications).

tasogare 6y ago

> null references This is addressed since C# 8.