It's too easy to run into a situation where the 'official' API supports Java/Python/Go as a first class citizen and the .NET library is a sad afterthought.
Let's look at general distributed messaging abstractions.
The most modern-featureful one for dotnet I know of is MassTransit: https://masstransit.io/documentation/concepts. You can see it supports a handful of queues and some interesting patterns.
Compare this to the list of features in Apache Camel: https://camel.apache.org/components/4.4.x/eips/enterprise-in...
Additionally, the _support_ of the libraries for common open-source (and closed-source infra) is usually vastly different:
- https://pulsar.apache.org/client-feature-matrix/
- Small features being first party like https://github.com/awslabs/amazon-sqs-java-extended-client-l... vs https://github.com/raol/amazon-sqs-net-extended-client-lib
- Missing features or those that lag behind: https://github.com/confluentinc/confluent-kafka-dotnet/issue...
- Usually manually wired and configured vs the spring boot "starter" pattern of having libraries that automatically do some of the manual setup work for you: https://github.com/spring-projects/spring-boot/blob/main/spr...
I wish more client library sets had the feature-matrix that the pulsar one does, because in practice most end up being the same: Java supports everything because it's either built in the same codebase or is the most used client and gets the most support, while the dotnet client codebase has many feature-requests or performance improvement issues, often leading to a "third-party client" being created.
We need a couple more Apache Struts and Log4J incidents for the public to realize there may be better technologies and ecosystems. Spring is very slow anyways.
As for Pulsar, there is a nice and optimized client (written in F#!) https://github.com/fsprojects/pulsar-client-dotnet
Avalonia being the most recent example.
Thus UNIX first shops rather focus on other ecosystems.
Edit: Okay, they know, I'm sorry :) Does not make it less sad and perhaps very unfortunate decision. Also, Hibernate sucks.
There's two kinds of Mono on Linux from what I understand...
The older one is packaged with a particular piece of security software, and the packages have more problems than I can count
edit: I got got! TIL that proper .NET on Linux exists. I'm more mad at Mono/this software now
It's security software - to be less vague, it's software made by Crowdstrike
Also, not liking what is now MIT FOSS stack does not make sense. It is the unified set of repositories going forward, with Mono currently serving exotic targets like WASM and being a part of dotnet/runtime. Completely not surprising for it is the most standard myopic response you usually hear from Linux communities (which, checks notes, are supposed to advocate for OSS?) the moment .NET is mentioned.
I mostly glue existing stuff together, not make new stuff. My frustration with .NET is dated, really due to Mono.
> which, checks notes, are supposed to advocate for OSS?
I'm not sure how much to unpack here; my complaints are more with what I was given than anything philosophical
Changing the underlining OS for 1000's of hosts is not a trivial task.
My title wasn't "architect", but it was "Staff Software Engineer" by the end. Does that qualify?
Where my heart lies aside, I also think it's rather dumb. My understanding of the system talked about in this job post is that it's quite mature and works very well, and my default stance for any rewrite is "don't be dumb, don't do it", and that would apply here.