5 ms·

C# is open source

lnxg33k1 3y ago
Its very dependent on a corporation, maybe I could rephrase it as only choose software not tightly coupled with a single corp
- RyeCombinator 3y ago
  Love the idea. I'm not sure if anyone has found a sustainable model yet. Looking at the current CNCF landscape, majority of the graduated projects have huge backing from single corps - promoted with the open source labelling. https://www.cncf.io/projects/ https://www.cncf.io/projects/ i.e. argo by Intuit, Cilium by Cisco, SPIFFE/SPIRE by VMware/HPE
  - weikju 3y ago
    And this is why I keep coming back to Common Lisp
    - RyeCombinator 3y ago
      Underrated comment
      - lnxg33k1 3y ago
        The fact that there are many projects depending on a single corp doesn't mean there aren't projects who are supported by community or a group of corp, I don't know take rust, take podman
- neonsunset 3y ago
  It's unlikely to ever happen that MSFT just says "we're not maintaining this anymore, we're making our own private fork". This seems like a huge blow to reputation and no financial upside. Kind of like Google abandoning Go (but then again, it's not like Google does not have a reputation for killing products). The main conundrum is the sheer cost of maintaining dotnet and its surrounding infrastructure, and the teams to keep it moving forward fast. But should unthinkable happen, it is MIT licensed so one or more companies can just carry on with their fork or maybe even transfer existing org/repos to some newly formed foundation.
  - lnxg33k1 3y ago
    I would use Go more confidently than C#, C# depends on Microsoft for everything, from the tooling to asp.net, entity framework, c# is mit licensed but you can’t get anywhere without microsoft. Now I understand there's little chance microsoft kills it, but I would assume people would have thought that of their perpetual licenses or plans for VMWare, they maybe thought they're not going to kill their clients, they're not going to kill sales partners because XYY, the truth is, there are good technologies very dependent on corporations deciding their directions, but those technologies aren't that level better than open ones to justify the risk
    - neonsunset 3y ago
      Who develops Go? :)
      - lnxg33k1 3y ago
        Yeah I understood that, but I said "I would rather" , not "I will" , I think the ecosystem of Golang is much less dependent on Google than C#, there are a lot of tools in Go that aren't related to Google and in case they'd give up the language, it would be much easier for the community to keep maintaining it, I think
        neonsunset 3y ago
        Unity, games written with Monogame or Godot, frameworks for distributed actors like Akka.NET, all kinds of message buses, AWS lambda for serverless that works on top of NativeAOT, Dapper and DapperAOT, AvaloniaUI (while people bash .NET for GUI story, they don’t bash Go because it just doesn’t have any good options at all) and Uno platform. No, it doesn’t seem to be the case. And C# mostly does not need multiple back-end frameworks because the out of box option (which is just a part of dotnet foundation ecosystem of repositories) provides the best performance out of all alternatives like Servicestack. This does not mean someone won’t implement another one in the future to sacrifice even more ASP.NET Core style features to minimize the overhead even further or to address specialized scenarios.

C# is open source

Its very dependent on a corporation, maybe I could rephrase it as only choose software not tightly coupled with a single corp

RyeCombinator 3y ago
Love the idea. I'm not sure if anyone has found a sustainable model yet. Looking at the current CNCF landscape, majority of the graduated projects have huge backing from single corps - promoted with the open source labelling. https://www.cncf.io/projects/ https://www.cncf.io/projects/ i.e. argo by Intuit, Cilium by Cisco, SPIFFE/SPIRE by VMware/HPE
- weikju 3y ago
  And this is why I keep coming back to Common Lisp
  - RyeCombinator 3y ago
    Underrated comment
    - lnxg33k1 3y ago
      The fact that there are many projects depending on a single corp doesn't mean there aren't projects who are supported by community or a group of corp, I don't know take rust, take podman
neonsunset 3y ago
It's unlikely to ever happen that MSFT just says "we're not maintaining this anymore, we're making our own private fork". This seems like a huge blow to reputation and no financial upside. Kind of like Google abandoning Go (but then again, it's not like Google does not have a reputation for killing products). The main conundrum is the sheer cost of maintaining dotnet and its surrounding infrastructure, and the teams to keep it moving forward fast. But should unthinkable happen, it is MIT licensed so one or more companies can just carry on with their fork or maybe even transfer existing org/repos to some newly formed foundation.
- lnxg33k1 3y ago
  I would use Go more confidently than C#, C# depends on Microsoft for everything, from the tooling to asp.net, entity framework, c# is mit licensed but you can’t get anywhere without microsoft. Now I understand there's little chance microsoft kills it, but I would assume people would have thought that of their perpetual licenses or plans for VMWare, they maybe thought they're not going to kill their clients, they're not going to kill sales partners because XYY, the truth is, there are good technologies very dependent on corporations deciding their directions, but those technologies aren't that level better than open ones to justify the risk
  - neonsunset 3y ago
    Who develops Go? :)
    - lnxg33k1 3y ago
      Yeah I understood that, but I said "I would rather" , not "I will" , I think the ecosystem of Golang is much less dependent on Google than C#, there are a lot of tools in Go that aren't related to Google and in case they'd give up the language, it would be much easier for the community to keep maintaining it, I think
      - neonsunset 3y ago
        Unity, games written with Monogame or Godot, frameworks for distributed actors like Akka.NET, all kinds of message buses, AWS lambda for serverless that works on top of NativeAOT, Dapper and DapperAOT, AvaloniaUI (while people bash .NET for GUI story, they don’t bash Go because it just doesn’t have any good options at all) and Uno platform. No, it doesn’t seem to be the case. And C# mostly does not need multiple back-end frameworks because the out of box option (which is just a part of dotnet foundation ecosystem of repositories) provides the best performance out of all alternatives like Servicestack. This does not mean someone won’t implement another one in the future to sacrifice even more ASP.NET Core style features to minimize the overhead even further or to address specialized scenarios.