Open Collective logo
Thanks to your financial contributions, we are operating on an estimated annual budget of$8,533

About

When building applications, if you take a step back and look at the forest instead of the trees, you will see that most of your code is reacting to something that changed or trying to control application state.

ReactiveUI provides you with building blocks that are particularly adept at expressing the relationship between a group of changing things and allows you to express the intent of a product feature in a single readable place which makes managing application state a piece of cake.

Applications built with ReactiveUI cope gracefully as the application gets more complicated because of the foundations of reactive programming that ReactiveUI is built upon.

You'll find ReactiveUI inside of products made by Amazon (Cloud Drive), Atlassian (Sourcetree), Slack (Mobile), GitHub (Visual Studio), Elastic (Search) and 343 Industries (Halo 5)

🎉 There is a Better Way 🎉

Instead of imperative programming, we can use a paradigm called Functional Reactive Programming which allows you to model user input as a function that changes over time, abstracting away the idea of mutable state. Reactive programming can look scary and complex at first glance, but the best way to describe reactive programming is to think of a spreadsheet:

  • Imagine three cells, A, B, and C.
  • C is defined as the sum of A and B.
  • Whenever A or B changes, C reacts to update itself.

That's reactive programming: changes propagate throughout a system automatically.

🎁 What We'll Use the Money For 🎁

Our initial goal is $x,000/month. That money will be enough to restore the imbalance of open-source , those who support you will now be supported. If ReactiveUI has no maintainers it will quickly become useless to all users and the project will die... again

  • Hire a technical writer to improve the project documentation, focusing on making reactive programming more accessible.
  • StackOverflow questions answered within 72 hours with best practices and authoritative solutions.
  • One maintainer - part-time. Open-source succeeds in every aspect except sustaining those who sustain open-source. Transitioning to semi-employed allows more time to be spent improving ReactiveUI and more time with family. As open-source software scales, projects need someone to handle things like community interaction, backlog triage, defect investigation and doing servant leadership activities to increase the productivity of maintainers, contributors and consumers. Currently, these tasks take a few hours every day which means there are minimal blocks of focused time available to work on framework features, do ambiti