• @EnderMB@lemmy.world
    link
    fedilink
    261 year ago

    IMO C# is at the point where Java can probably just die. I don’t see a point in keeping Java when C# is a viable option in many use cases.

    • @grue@lemmy.world
      link
      fedilink
      English
      241 year ago

      I’m sure Microsoft will be happy to know their EEE strategy is finally paying off, only two decades late.

      • @EnderMB@lemmy.world
        link
        fedilink
        91 year ago

        It’s attitudes like this that made me choose C# as the language I wanted to use professionally after graduation.

        Having grown up in the Slashdot era where people would be childish, post about Micro$oft, and parrot EEE, all while the .NET Foundation consistently put out great tooling with a mature community that actively wanted to help you learn the language/framework, the choice was simple.

    • @GissaMittJobb@lemmy.ml
      link
      fedilink
      201 year ago

      I don’t think this line of reasoning is strictly speaking correct, but assuming it was, then I think it would follow that Kotlin exists and as such C# does not need to be kept around.

    • Compiled Java is still cross-platform. It’s been a few years for me, but when I last worked in C# it was a giant PITA to work on it in Linux or MacOS. I hope it’s gotten better.

      • @vithigar@lemmy.ca
        link
        fedilink
        71 year ago

        .NET (not .NET Framework) is cross platform and can be compiled into native binaries on a variety of platforms. There is however the wrinkle of not all the libraries within .NET being supported on all platforms. Most notably, everything involving a graphical UI is Windows only.

        The most well known cross platform .NET project you probably have heard about is Jellyfin.