CODEWITHSUNDEEP
c#.netsystem.reactivereactive
James Cane
James Cane

Reputation: 143

Has the Reactive Extensions library been discontinued?

Screenshot of Reactive Extensions documentation website in a browser

The documentation for much of the Reactive Extensions library on Microsoft's website says "We're no longer updating this content regularly. Check the Microsoft Product Lifecycle for information about how this product, service, technology, or API is supported."

Furthermore, searching for some basic Reactive Extensions class names (such as "Subject") in the main documentation site returns no hits. The only hits come in the "Previous Versions" section of the site.

There is no mention of Reactive Extensions in the linked "Product Lifecycle" page.

Does this mean that Microsoft are no longer supporting Reactive Extensions, or have I missed something?

Upvotes: 10

Views: 2187

Answers (1)

Panagiotis Kanavos
Panagiotis Kanavos

Reputation: 131189

No, it hasn't. You're looking at a page under the Previous Version heading. That's why the warning is shown.

Reactive Extensions is a separate OSS project, and only the .NET implementation can be found under the dotnet organization. The ReactiveX org contains many other implementations. If you check its Github repo you'll see the latest commit was yesterday. The latest version 4.3.2 was released to NuGet 20 days ago

The project's documentation page is http://reactivex.io/.

The project covers many languages, not just .NET. In fact, Reactivex.JS is probably THE most active edition, and most JavaScript developers don't even know Rx was created by Microsoft.

Rx is not deployed as part of .NET but then, neither is EF, EF Core, or any of a number of libraries people think as part of .NET. Lately, even Microsoft.Data.SqlClient became a separate package.

Since 4.x, many libraries became packages to reduce the runtime size and allow independent development.

Upvotes: 8

Related Questions