Rx.net has been an open framework for reactive programming for years.

It always strikes me that Multicharts.net is rather slow to use here and there - especially when it comes to backtesting, optimizing and describing the database.

In traditional programming it works something like this:

You go to the newsagent and ask (each time you run the program) whether there is a new newspaper. And it will not be uncommon for the current newspaper not to be available. So you've wasted your time and have to try again later. During this time you were unable to perform any other tasks.

This is where reactive programming comes in, you no longer have to go to the newsagent's shop, you can be notified when the latest newspaper is available and have it delivered directly. You can determine in advance which types of newspaper you are interested in and which are not (filter ).
So you will receive the newspaper immediately when it is available without costly detours. Rx.net is also multi-threaded and is constantly being developed further (advantages of the open source principle).

Microsoft Excel is a good example of reactive programming: as soon as you change the value of a cell, the values ​​of all other cells that are subscribed to the changed cell are also changed.

Reactive programming is a significant advantage, especially for time-critical actions such as data and time series in the financial industry!

Thanks to the Linq-like syntax, reactive is not particularly difficult to learn.
Without the internal structures of mutlicharts. net in detail, it can be assumed that the (gradual conversion) to Rx.net structures should improve performance overall.