News for hackers. Stuff that matters.
Re:The unreasonable effectiveness of declarative programming by lbarrow on Tuesday May 19, 2020 @11:26AM (#23235882)
Compared with SQL it's definitely imperative. It's definitely using higher-level abstractions than a `for` loop, but it still specifies the order of operations.
Re:The unreasonable effectiveness of declarative programming by barrkel on Tuesday May 19, 2020 @12:38PM (#23236916)
Actually it doesn't unless you're assuming eager evaluation and that 'arr' is something like an array, rather than something which monadically collects functions for evaluation later.

In C#, the functions being passed could be passed as analyzable syntax trees, and the implementation could actually be in SQL.

Re:The unreasonable effectiveness of declarative programming by sriram_malhar on Tuesday May 19, 2020 @02:50PM (#23238605)
nope. Sequencing and imperative have an overlap, but they are not the same thing.

Sequencing is a fundamental computing construct. Data flow graphs allow you to specify sequences, just as shell pipelines do. SQL has sequentiality built-in with nested queries. None of these are imperative environments.

Re:The unreasonable effectiveness of declarative programming by nicoburns on Tuesday May 19, 2020 @11:36AM (#23236010)
> it still specifies the order of operations

Yes, although not necessarily all of them. Some languages will process this eagerly, some lazily.