/explore
|
You are here 
|
sookocheff.com | ||
| | | | |
degoes.net
|
|
| | | | | Functional programming has a bit of jargon, but that doesn't have to stop you from understanding core concepts | |
| | | | |
danielpecos.com
|
|
| | | | | Purpose of this post is to providea glimpse of the new features included in Java 8 that shiftthis language towards a more Functional Programming paradigm. But before, let's define what we understand for Functional Programming (FP). Functional programming key characteristics include: Higher Order Functions Pure Functions and Immutability Tail Call Recursion Higher Order Functions for a FP language means that functions are considered first class citizens, allowing the programmer to use them as any other value the language defines, for example, a Function value: | |
| | | | |
sreekar.ch
|
|
| | | | | But first What is functional programming Functional programming is a programming paradigm in which most computation is treated as evaluation of functions. It emphasizes on expression evaluation instead of command execution. Wikipedia When did it all start In the 90s, there was a war between declarative programming and imperative programming. Declarative programming then represented by logic programming languages like Prolog and early functional languages like Erlang. And imperative languages were r... | |
| | | | |
krakendev.io
|
|
| | | Subclassing can suck. There are so many ways to get it wrong and it's so easy to fall into anti-patterns when you create such a tight coupling between two classes. Most of the time, the need for subclassing can actuallybe replaced by abstraction through protocol-oriented, value-oriented, and functional programming. In fact, I may even argue that doing it that way can far outweigh the "benefits" of subclassing the majority of the time. | ||
