Can those be generic?
Paired with current and previous fields is kinda weird.
Pairwise() : Observable<Pairwised<T>>
Pair<T> is not ideal as a public type with fields Current and Previous
Pairwised doesn't improve that.
Observable<Timestamp<T>> timestamp(this Observable<T> source, IScheduler scheduler) in C#
See
Replay<TSource>(IObservable<TSource>, Int32)
Returns a connectable observable sequence that shares a single subscription to the underlying sequence replaying bufferSize notifications.
Another interesting you could sometimes use is
Replay<TSource, TResult>(IObservable<TSource>, Func<IObservable<TSource>, IObservable<TResult>>, Int32)
Returns an observable sequence that is the result of invoking the selector on a connectable observable sequence that shares a single subscription to the underlying sequence replaying bufferSize notifications.
You call it with source.Replay((src) => { ... }, 1)(src) => { ... } here is the selector function and inside there nyouy can use src as many times as you want and it will replay the latest value each time you subscribe to it, but after Replay you have a normal Observable instead of ConnectableObservable that you need to connect to etc.
For example source.Replay(src => src.concat(src)) will emit source like normal, but replay the last value on complete.
What is the status of reactive programming in c#/.net?
- Is there a "native" reactive technology that goes beyond System.Observable, and which is fully supported, maintained and actively being developed by Microsoft?
- One could get the impression that https://github.com/dotnet/reactive is the current and active repo on Github, but on that page it say "Join the conversation" and links to: http://reactiveui.net/slack.
Ones there the latest message is from 2015 and the the channel is called "#dont-talk-in-here". - When you check out Microsofts documentation for Reactive Extensions) it is from 2011 and has huge warning that the content is no longer updated.
- On ReactiveUI.net there's a blog post from 2018 indicating that System.Reactive is abandoned by Microsoft, and superseded by something called "Reactor".
All these things combined makes my customers confused about the status of reactive programming in .NET and unless I find and point them to clear, concise and unambiguous resources which ensures that Microsoft is behind the technology, actively developing and supporting it and that is has a road-map where it show that it is a core part of the .NET Framework for many versions to come.
They were burned by Microsoft abandoning both Silverlight and LightSwitch.