3 ms·

We used Segment for application analytics and exception reporting in an enterprise setting. Their .NET libraries were abysmal and had some show-stopper bugs tha

We used Segment for application analytics and exception reporting in an enterprise setting. Their .NET libraries were abysmal and had some show-stopper bugs that we wrestled with, particularly broken dependencies. I eventually had to fork the Analytics.NET repo and fix them myself. It was months before I heard any response to the issues or PRs, although they did eventually get merged in. It was just disappointing overall. I don't know why they'd release .NET tooling but have it be broken out-of-the-box, or maintain an open source project but not respond to any contributions.

ivolo 9y ago
Hey, this is Ilya - i'm one of the co-founders and original author of the .NET library - I'm really sorry that happened. In the early days, I was the author of 5 of our open source libraries and also a student of the .NET platform. Today we have a larger team working on our libraries - .NET in particular has 200+ customers (mostly on our business tier) and we're processing 21B+ API calls/mo originating from .NET. If you could send me an email at ilya@segment.com, I'd love to chat live and collect any other feedback you have from the experience. Thanks again for leaving the note.
rjbwork 9y ago
Usually these kind of startups that produce native libraries for use in other software produce poor .NET libraries. (see sendgrid) I wouldn't place the blame totally on them - you often have 1 person supporting multiple libraries in multiple languages, and .NET is not often used at these sorts of startups. On the other hand, a few thousand dollars for a consultant to get their situation in order would not be a bad investment to get them out of the situation, because a bad experience like this festers in the community for years.