命令式和声明式描述了两种相反的编程风格。命令式是传统的“循序渐进”方法，而声明式则更多地是“这就是我想要的，现在你来研究如何去做”。

这两种方法贯穿于整个编程过程——即使使用相同的语言和相同的程序。一般来说，声明式方法被认为是更可取的，因为它使程序员不必指定如此多的细节，同时也减少了出现错误的机会(如果您描述了您想要的结果，并且一些经过良好测试的自动流程可以从该结果向后工作以定义步骤，那么您可能希望事情比手工指定每个步骤更可靠)。

另一方面，命令式方法为您提供了更多的低级控制——这是编程的“微观管理方法”。这可以让程序员利用有关问题的知识来给出更有效的答案。因此，程序的某些部分以声明式的风格编写并不罕见，但对速度至关重要的部分则更加必要。

as you might imagine, the language you use to write a program affects how declarative you can be - a language that has built-in "smarts" for working out what to do given a description of the result is going to allow a much more declarative approach than one where the programmer needs to first add that kind of intelligence with imperative code before being able to build a more declarative layer on top. so, for example, a language like prolog is considered very declarative because it has, built-in, a process that searches for answers.

so far, you'll notice that i haven't mentioned functional programming. that's because it's a term whose meaning isn't immediately related to the other two. at its most simple, functional programming means that you use functions. in particular, that you use a language that supports functions as "first class values" - that means that not only can you write functions, but you can write functions that write functions (that write functions that...), and pass functions to functions. in short - that functions are as flexible and common as things like strings and numbers.

it might seem odd, then, that functional, imperative and declarative are often mentioned together. the reason for this is a consequence of taking the idea of functional programming "to the extreme". a function, in it's purest sense, is something from maths - a kind of "black box" that takes some input and always gives the same output. and that kind of behaviour doesn't require storing changing variables. so if you design a programming language whose aim is to implement a very pure, mathematically influenced idea of functional programming, you end up rejecting, largely, the idea of values that can change (in a certain, limited, technical sense).

如果你这样做——如果你限制变量的改变方式——那么你几乎会意外地迫使程序员编写更具声明性的程序，因为命令式编程的很大一部分是描述变量如何改变，而你再也不能这样做了!因此，函数式编程——特别是用函数式语言编程——倾向于给出更多的声明性代码。

总结一下:

命令式和声明式是两种相反的编程风格(鼓励这些风格的编程语言使用相同的名称) 函数式编程是一种编程风格，其中函数变得非常重要，因此，更改值变得不那么重要。在值中指定更改的有限能力迫使使用更声明性的风格。

因此，“函数式编程”通常被描述为“声明式的”。

当务之急:如何实现我们的目标

   Take the next customer from a list.
   If the customer lives in Spain, show their details.
   If there are more customers in the list, go to the beginning

声明性:我们想要达到的目标

   Show customer details of every customer living in Spain

对于这些并没有明确客观的定义。以下是我对它们的定义:

命令式——重点是计算机应该采取什么步骤，而不是计算机将会做什么(例如C, c++， Java)。

声明性——重点是计算机应该做什么，而不是它应该如何做(例如SQL)。

函数式——声明性语言的子集，非常注重递归

我认为你的分类是不正确的。有两种相反的类型，命令式和声明式。函数式只是声明式的一个子类型。顺便说一句，维基百科也说了同样的事实。

命令式——表达式描述要执行的动作序列(关联的)

声明性——表达式是对程序行为做出贡献的声明(关联、交换、幂等、单调)

函数式表达式的值仅为效果;语义支持等式推理

命令式编程:告诉“机器”如何做某事，结果你想发生的事情就会发生。

声明式编程:告诉“机器”你想要发生什么，然后让计算机想出如何去做。

命令式的例子

function makeWidget(options) {
    const element = document.createElement('div');
    element.style.backgroundColor = options.bgColor;
    element.style.width = options.width;
    element.style.height = options.height;
    element.textContent = options.txt;

    return element;
}

声明性的例子

function makeWidget(type, txt) {
    return new Element(type, txt);
}

注:区别不在于简洁、复杂或抽象。如前所述，区别在于如何做和做什么。