| ▲ | glimshe 5 hours ago |
| I love C# and in every iteration we're getting more and more features to get C-like performance in a lot of scenarios. C# does it really well because if your problem isn't performance/memory-constrained, you can ignore these features and fallback on the language's natural ease of use. |
|
| ▲ | kensai 2 hours ago | parent | next [-] |
| Do you think by now C# has left Java behind in features and performance? |
| |
|
| ▲ | hirvi74 3 hours ago | parent | prev [-] |
| I daylight as a .NET dev professionally. I completely agree with what you have wrote, but I do not think C# is particularly unique in that regard. I would say many common compiled languages are on the same path, e.g., Swift, Java, Kotlin, etc.. As time progresses, I am finding it harder to justify using C# for a greenfield project. |
| |
| ▲ | za3faran 2 hours ago | parent [-] | | > As time progresses, I am finding it harder to justify using C# for a greenfield project. Are you able to elaborate why? Just curious. | | |
| ▲ | antonymoose 2 hours ago | parent [-] | | Not OP here - but for me it’s the open source ecosystem. Java just wins in terms of scope, scale, and stability. I love C# the language, but the ecosystem is a ghetto. | | |
| ▲ | Rohansi an hour ago | parent [-] | | I see this reason a lot but what are some actual examples of what is lacking in the .NET ecosystem vs. Java? | | |
| ▲ | davewritescode an hour ago | parent | next [-] | | Large Apache ecosystem (Spark, Flink, Pinot) is completely missing and third-party SDKS (looking at you AWS) almost ALWAYS have worse SDKs. The java Kinesis consumer and producer libraries are amazing, the ones for C# are simple wrappers around the AWS APIs which means there's a few foot guns waiting for developers to run into, even if they should know better. | |
| ▲ | Amekedl an hour ago | parent | prev | next [-] | | Dev tools. The debugger is something for example that Microsoft ostensibly keeps to their own products, and how they totally slaughtered omnisharp. It killed my daily csharp vscode driver couple of years ago, only now catching back up somewhat, but still unusable for bigger solutions. That move made me gravitate towards vscodium, and avoiding csharp where possible. Microsoft's move only recently got more understandable to me, because Cursor and others basically stole vscode to establish their "empire". | |
| ▲ | free652 an hour ago | parent | prev [-] | | I mean I haven't done much in c# recently, but few examples that c# ecosystem is the subpar in quality Kafka client library sucks, I mean it was a nightmare to make it stable and there were a few of them. Pdfbox library And many other libraries. If you use c# Microsoft libraries only - then you are golden. outside of that its really bad. At this point I switched to Rust. |
|
|
|
|
