ReactiveUI was created by Anaïs Betts whilst working in Office Labs at Microsoft, and released in early 2011. Since that time, ReactiveUI has become a mature framework trusted by Slack, GitHub, Amazon, Elastic and Microsoft, has become a member of the Dot Net Foundation, and actively maintained by the open-source community on GitHub. The work we do is sponsored by our wonderful Backers on OpenCollective.Read more...
The ReactiveUI team has been urging consumers for some time now to move away from the
ReactiveCommand abstract class for properties. There are some slight nuiances with type constraints that can sometimes cause run time bugs. Because your property can resolve to an abstract base implementation doesn't mean you should define it that way. We are very adamante about creating a type safe environment where consumers don't have to worry about hidden runtime issues with the framework. RFC: Remove ReactiveCommand abstract base class was raised to address this exact issue.
ReactiveUI has released several minor versions since 8.0. Some of the most recent versions have been released without Geoff having to push code, or prep issues. This is thanks to members of the core team, and community members who have stepped up to move the project forward. Glenn Watson has started to play a large role in the maintenance of ReactiveUI. There have been other's getting involved in enhancing some of the platform logic, and documentation. Community members have been identifying and resolving issues that help make our framework better. What does this mean for ReactiveUI succession? It's happening. What does that mean for you? It means we are working on ways to improve ReactiveUI and make it easier to consume. We have several initiatives on the team and there are a few RFC's planned for the 9.0 release that might be of interest.Read more...
With the coming 8.6.1 release,
ReactiveList will be marked as deprecated. ReactiveList is being replaced by Roland Pheasants Dynamic Data
Moments ago we merged a contribution by Grzegorz Kotfis that adds another layer of protection before the project moves towards automated continuous delivery. The pull-request added a new project called
ReactiveUI.LeakTests which allows the maintainers to specify tests that can determine memory leaks by checking memory usage for objects of a particular type, or tests that track memory traffic and fail in case the traffic exceeds some threshold.