concept abstraction in category functional programming

This is an excerpt from Manning's book Functional Programming in C#: How to write better C# code.
Other languages (including Haskell and Scala) support so-called “higher-kinded types,” so it’s possible to represent these more general interfaces with typeclasses, but in C# (and F#) we must content ourselves with a lesser level of abstraction and follow a pattern-based approach.[3]
7This classification isn’t exhaustive because you can envisage more categories where the application of a function would cause you to jump by several levels of abstraction or would take you from one type of abstraction to another. But these are probably the most usual kinds of functions you’ll encounter, so the classification is still useful.
Functions of the second kind remain within the abstraction. So, for instance, the following function is a clear match:
(IEnumerable<int> ints) => ints.OrderBy(i => i)Its signature is in the form A<T> → A<R>. But we should also include in this category any function in which we start with an A<T>, have some additional arguments, and ultimately end up with an A<R>. That is, any function whose application keeps us within the abstraction; its signature will be in the form (A<T>, ...) → A<R>. This includes many HOFs we’ve looked at, such as Map, Bind, Where, OrderBy, and others.
This idea of working at different levels of abstraction is important. If you always deal with regular values, you’ll probably be stuck with low-level operations such as for loops, null checks, and so on. Working at such a low level of abstraction is inefficient and error-prone.

This is an excerpt from Manning's book Functional Programming in JavaScript.
In addition, functional composition raises the level of abstraction so that you can clearly outline all the steps performed in this code without being exposed to any of its underlying details. Because compose accepts other functions as arguments, it’s known as a higher-order function. But composition isn’t the only way to create fluent, modular code; in this book, you’ll also learn how to build sequences of operations by connecting operations in a chain-like manner.
In this section, I’ll introduce a reactive library called Reactive Extensions for JavaScript (RxJS) that you can use to elegantly combine asynchronous and event-based programs (refer to the appendix for installation information). RxJS works in ways similar to the functional promise-based examples you saw earlier in this chapter, but it provides a higher degree of abstraction and many more powerful operations. Before we get started, you must understand the concept of observables.

This is an excerpt from Manning's book Functional Programming in Java: How functional techniques improve your Java programs.
A very important part of functional programming consists in pushing abstraction to the limit. In the rest of this book, you’ll learn how to abstract many things so you never have to define them again. You will, for example, learn how to abstract loops so you won’t have to write loops ever again. And you’ll learn how to abstract parallelization in a way that will allow you to switch from serial to parallel processing just by selecting a method in the List class.