← Back to context

Comment by owlstuffing

8 hours ago

In isolation, yes, I agree with you. But in the context of the cornucopia of other "carefully evaluated" features mixed into the melting pot, C# is a nightmare of language identities - a jack of all trades, master of none, choose your dialect language. No thanks.

9 comments

owlstuffing

Reply
LunicLynx  7 hours ago

If it’s not for you I guess that is ok. But from your comment I would also deduct that you never professionally used it. After so many different languages it’s the only one I always comeback to.

The only things that I wish for are: rusts borrow-checker and memory management. And the AOT story would be more natural.

Besides that, for me, it is the general purpose language.

  • owlstuffing  7 hours ago

    General purpose != multiple dialects, that is the trouble with languages like this - C# is a tower of babel.

wvenable  4 hours ago

> C# is a nightmare of language identities - a jack of all trades, master of none, choose your dialect language.

I honestly have no idea where you would get this idea from. C# is a pretty opinionated language and it's worst faults all come from version 1.0 where it was mostly a clone of Java. They've been very carefully undoing that for years now.

It's a far more comfortable and strict language now than before.

  • CharlieDigital  3 hours ago

    I can see where he's coming from. For example, `dynamic` was initially introduced to support COM interop when Office add-in functionality was introduced. Should I use it in my web API? I can, but I probably shouldn't.

    `.ConfigureAwait(bool)` is another where it is relevant, but only in some contexts.

    This is precisely because the language itself operates in many runtime scenarios.

    • wvenable  2 hours ago

      I guess that's a good point. I admit haven't used or seen `dynamic` in so long that I completely forgot about it.

      But I'm not sure that's really a problem. Does the OP expect everyone to use an entirely different languages every single context? I have web applications and desktop applications that interact with Office that share common code.

      Even `dynamic` is pretty nice as far as weird dynamic language features are concerned.

      Interestingly enough `.ConfigureAwait(bool)` is entirely the opposite of `dynamic` -- it's not a language feature at all but instead a library call. I could argue that might instead be better as a keyword.

      2 replies →

DeathArrow  7 hours ago

>a jack of all trades

Yes, C# is a jack of all trades and can be used at many things. Web, desktop mobile, microservices, CLI, embedded software, games. Probably is not fitted for writing operating systems kernels due to the GC but most areas can be tackled with C#.