[Mono-dev] System.Json string handling

Edward Ned Harvey (mono) edward.harvey.mono at clevertrove.com
Sat Sep 20 19:00:30 UTC 2014

> From: mono-devel-list-bounces at lists.ximian.com [mailto:mono-devel-list-
> bounces at lists.ximian.com] On Behalf Of Miguel de Icaza
> It is not easy to add people.   We can only add people that have shown the
> practices and skills that come with reviewing patches and working through
> the system.
> If we had more of those, we would add them.

Tru dat.  However, when broken stuff doesn't get fixed, it drives users away.  I'll cite myself as an example:  We've had a pull request outstanding since April https://github.com/mono/mono/pull/1004, prior to which, SslStream is simply unusable (mono SslStream server is incompatible with mono SslStream client).  So we have to distribute our product using *only* our custom patched version of mono, cannot tell our customers to use any standard mono version, and since it's been ignored so long, the decision is long since concluded that we must bite the bullet and find some other SSL package.  It's too late for us - even if that pull request were to be merged today, the lack of attention demonstrates that those classes are poorly maintained, and we have to assume, possibly unstable or insecure in ways that we haven't yet discovered.  So for us the decision to get off is already done.  Hopefully the train won't keep its momentum in this direction.

More information about the Mono-devel-list mailing list