At MVP Summit, the community met with Microsoft and with their support and encouragement the community forked control of System.Reactive. Over the last couple weeks some of the smartest brains from multiple ecosystems have united in our Slack instance to plan for the future.
One of the items that everyone agreed upon almost instantaneously was that reactive programming on dotnet needed to have a stronger branding/marketing presense. We need to signal that
System.Reactive is part of .NET and that living under the existing Reactive-Extensions GitHub organization did not convey that message.
Today the community, in conjunction with Microsoft shipped the first milestone on our initial roadmap.
This is big news because
System.Reactive for .NET is the OG and original implementation of the Reactive Extensions. Sadly it's potential was artificially limited over the years while other ecosystems saw massive growth. It's time to put that narrative to bed though. It's time to move on. Thank you Jon Galloway, Phil Carter, Bart de Smet, Immo Landwerth for your help with advancing the community past this historical narrative.
Our new home under the .NET organization on GitHub provides better discoverability and visibility. It provides CI systems that keep up with the rapid evolution that's happening in .NET. The new location is closer to .NET development itself and components from System.Reactive which are logical base class library extensions now have shorter integration paths into corefxlabs. A great demonstration of this is how System.Reactive's (Ix)
IAsyncEnumerable is graduating into a first-class citizen in C# v8.
It also means that the Reactive Extensions will now automatically show up in data exports of opensource activity on GitHub for Microsoft execs. This is a big deal as Microsoft is heavily driven by data. If the community shines bright, is open/inclusive, stays on track then the future is very very 🚀
This is a new era. Join the conversation over at https://reactiveui.net/slack and ask how you can help.