3 ms·
It's the aesthetic of programming as "solving the actual problem", vs. programming as "solving the problem of how to solve the problem". When you're solving th
by mjburgess 3y ago
It's the aesthetic of programming as "solving the actual problem", vs. programming as "solving the problem of how to solve the problem".
When you're solving the actual problem imperative is largely the right default: each line clearly relates to the actual problem; and it's clear how the actual problem is being solved.
When you're bored, or have no actual problems, it's fun that every line is a little puzzle.
- tombert 3y agoI think I disagree with this entirely. With imperative you’re actively translating the problem in terms of how things are going to be interpreted by the CPU. With functional you actual express how to solve the problem and trust that the language constructs will handle stuff like loops for you.