• "Functional scalability: The ability to enhance the system by adding new functionality at minimal effort." (Wikipedia)

Our main aim with BetSoftware is to make it an example of functional scalability.

This means new functionality can be added by writing "to-the-point" modules dealing with very defined parts. Allowing an easy "chaining" of them.

For instance, it doesn't only aims to split new coding into parts, but reusing as much of other code as possible, without having to modify single line of code in order mix and reuse.

The functionality of BetSoftware becomes the sum of many independent parts.

The goal:  Click, click, click = a tracker.

Click, click, click = a clicker.

Click, click, click, click = a different tracker, made by the user with just a click of difference, on his own without having to edit anything code-wise.

The true "Long-term Gold" of BetSoftware being providing users the ability to compound features coded by different programmers without touching a single line of code.

This being done without requiring programmers to communicate or cooperate in coordination with each other, but obtained as a natural side product of the development of BetSoftware-compatible code. Each programmer does his/her thing, publishes, then the sum of the parts is enriched, for the benefit of everyone involved.