6 ms·

Problem with C# isn't the language, it's the enterprise ecosystem. You always feel like you're going to have to pay at some point down the road for using the te

by bsaul 1y ago

Problem with C# isn't the language, it's the enterprise ecosystem. You always feel like you're going to have to pay at some point down the road for using the tech.

cgh 1y ago
Every large company I’ve ever worked at had a strict “no Microsoft on the server” policy and for better or worse, C# is closely identified with Microsoft.
- runjake 1y ago
  IOW Linux on the server?
hu3 1y ago
I don't see Java being any better in this regard. Microsoft has been historically much less aggressive with lawyers compared to Oracle.
- frontfor 1y ago
  That might be true for other Oracle products like the DB, but has that been true for Java and openjdk?
  - homebrewer 1y ago
    Sure. Here's just one example I was able to quickly find in the browser history: https://www.theregister.com/2025/05/09/users_advised_to_review_oracle_java_use/ https://www.theregister.com/2025/05/09/users_advised_to_revi... You can easily just not use the Oracle JDK, though, unless you're running commercial software which requires running on the Oracle runtime to get technical support. As others have said, the problem is not the runtime, but libraries: many major .NET libraries have been going fully commercial, you can't really trust the ecosystem anymore.
- wslh 1y ago
  I think OP means that .NET has strong connections with Microsoft technologies where it is a natural decision to use Azure instead of AWS.
- antod 1y ago
  The poster was talking about the ecosystem not the core platform. The wider Java ecosystem was heavily dominated by many Apache (and other) open source libraries vs commercial products for the C# ecosystem.
  - neonsunset 1y ago
    Most of the features that require Apache or community packages in Java ship out of box in .NET (or via extension packages). They also tend to be of higher quality and provide better performance.
- cyberax 1y ago
  Java has a strong history of OpenSource, and a great set of libraries. It also pioneered the managed dependency system early (Maven), so these libraries have been centrally available for two decades. Moreover, a lot of these libraries are well-supported to this day. For example, Hibernate (the best ORM in business) is 28 years old, and has just released a new version. I recently consulted my former client (from 15 years ago), and I still recognized most parts of the stack that I set up way back then.

by bsaul 1y ago

Problem with C# isn't the language, it's the enterprise ecosystem. You always feel like you're going to have to pay at some point down the road for using the tech.

cgh 1y ago

Every large company I’ve ever worked at had a strict “no Microsoft on the server” policy and for better or worse, C# is closely identified with Microsoft.

runjake 1y ago
IOW Linux on the server?

hu3 1y ago

I don't see Java being any better in this regard. Microsoft has been historically much less aggressive with lawyers compared to Oracle.

frontfor 1y ago
That might be true for other Oracle products like the DB, but has that been true for Java and openjdk?
- homebrewer 1y ago
  Sure. Here's just one example I was able to quickly find in the browser history: https://www.theregister.com/2025/05/09/users_advised_to_review_oracle_java_use/ https://www.theregister.com/2025/05/09/users_advised_to_revi... You can easily just not use the Oracle JDK, though, unless you're running commercial software which requires running on the Oracle runtime to get technical support. As others have said, the problem is not the runtime, but libraries: many major .NET libraries have been going fully commercial, you can't really trust the ecosystem anymore.
wslh 1y ago
I think OP means that .NET has strong connections with Microsoft technologies where it is a natural decision to use Azure instead of AWS.
antod 1y ago
The poster was talking about the ecosystem not the core platform. The wider Java ecosystem was heavily dominated by many Apache (and other) open source libraries vs commercial products for the C# ecosystem.
- neonsunset 1y ago
  Most of the features that require Apache or community packages in Java ship out of box in .NET (or via extension packages). They also tend to be of higher quality and provide better performance.
cyberax 1y ago
Java has a strong history of OpenSource, and a great set of libraries. It also pioneered the managed dependency system early (Maven), so these libraries have been centrally available for two decades. Moreover, a lot of these libraries are well-supported to this day. For example, Hibernate (the best ORM in business) is 28 years old, and has just released a new version. I recently consulted my former client (from 15 years ago), and I still recognized most parts of the stack that I set up way back then.