I have been too used to Imperative Programming which is the usual way of telling the computer to perform step by step the procedure to get the final result. On the other han
Another useful explanation I found in the Pro XAML with C#:
In declarative programming, the source code is written in a way that expresses the desired outcome of the code with little or no emphasis on the actual implementation.
Imperative programming is the opposite of declarative programming. If declarative programming can be thought of as declaring what the desired outcome is, imperative programming can be viewed as writing lines of code that represent the instructions of how to achieve the desired outcome.