Reactive Extensions for .NET - Rx[dot]NET v7 and Futures | by Ian Griffiths
https://endjin.com/what-we-think/talks/reactive-extensions-for-dotnet-rxdotnet-v7-and-futures
Reactive Extensions for .NET - Rx[dot]NET v7 and Futures | by Ian Griffiths
https://endjin.com/what-we-think/talks/reactive-extensions-for-dotnet-rxdotnet-v7-and-futures
The State of Rx.NET in 2025
https://www.youtube.com/watch?v=SZpmj0fSfFI
tl;dw:
- Still living in dependency hell. They won't release Rx7.0 before solving those issues first. Everything else has lower priority.
- AsyncRx.NET will be developed over time.
- Ix.NET will not be developed as a part of the Rx project anymore. All LINQ to IAsyncEnumerable stuff will be moved to the core dotnet libraries.
#rx #rxnet #reactive #reactiveextensions #reactiveprogramming #dotnet #csharp #fsharp
Anyone know a good intro to #ReactiveProgramming / #ReactiveExtensions for web/API developers on #DotNet?
I've read IntroToRX.com as well as the documentation to #ReactiveUI, but I clearly don't grasp it, since I keep shooting myself in the foot (e.g., keep causing the UIs to freeze).
Much appreciated. ❤️
Rx.NET v6.0 has been released!
This update brings several improvements & focuses on enhancing compatibility, supporting the latest versions of .NET, and addressing common pain points for developers.
More on #InfoQ: https://bit.ly/3NBBiUC
Last month, the team behind Rx.NET announced the release of the 6.0 version. The latest version of the library brings several improvements and aligns itself with the current .NET ecosystem. While the update doesn't introduce significant new functionality, it focuses on enhancing compatibility, supporting the latest versions of .NET, and addressing common pain points for developers.