3 ms·
> Brainfuck is a sufficient example. How so? It's both very verbose and not very maintainable. > Abstraction is not clutter. Most of the overhead in non-func
by lmm 5y ago
> Brainfuck is a sufficient example.
How so? It's both very verbose and not very maintainable.
> Abstraction is not clutter.
Most of the overhead in non-functional languages is not abstraction.
> FP adds new abstractions which have variable syntax across languages or even within the same language.
What are you talking about? Generally FP languages have less special-case syntax and less special-case concepts, e.g. fewer control flow keywords, exceptions are less prominent, coroutines don't use special keywords or new concepts, mutable variables aren't needed.... I guess do notation is more common in functional languages, but it's a very lightweight piece of syntax sugar that obviates a bunch of what would be special-case syntax in less functional languages: http://philipnilsson.github.io/Badness10k/escaping-hell-with-monads/ http://philipnilsson.github.io/Badness10k/escaping-hell-with... .
> A program can be written in a conceptually non-fp language, that is composed of functions without side effect.
Static doesn't mean side-effect free, and a binary distinction between "side effect" and "not side effect", while somewhat useful, is very crude. But the biggest issue is that it's not practical to write without side effects unless the language's standard library, ecosystem, and most of all culture support it.
> People try FP-centric languages, but unless someone pays them, generally people stay away from it except in spurts (eg map, fluent chaining, etc). This should give some pause, as to what that means.
On the contrary, popular programming culture creeps slowly in the FP direction every year. Five or ten years ago map was some wacky far-out functional thing.