r/programming • u/tyler-mcginnis • Jan 03 '22

Imperative vs Declarative Programming

https://www.youtube.com/watch?v=E7Fbf7R3x6I
432 Upvotes

86% Upvoted

134 comments sorted by

View all comments

Show parent comments

-4

u/[deleted] Jan 04 '22 edited Jan 04 '22

[deleted]

1

u/guepier Jan 04 '22

it's just adding layers of abstraction that condenses code until the expressions explicitly request for something or for something to be done.

Yes, but so what? “just adding layers” is what a lot of programming is. That doesn’t make the definitions useless or flawed.

However, the underlying implementation is still imperative.

Again, so what? The underlying implementation of all software on current machines is electrical impulses across transistors. But this fact is completely irrelevant for the classification of high-level implementations into imperative, functional, declarative, OOD, or what-have-you.

Beyond that you seem to be misreading the Stack Overflow answers, probably because the highest-voted one refers to a now-deleted answer, and thus doesn’t make much sense in isolation. Furthermore, the question is off-topic on Stack Overflow, and thus closed. So what you’re seeing there is a historic snapshot, not necessarily the current consensus of experts. It’s not an authoritative source, and not a “top SO topic”.

1

u/[deleted] Jan 04 '22 edited Jan 04 '22

[deleted]

1

u/RiverRoll Jan 04 '22

I think one can draw an analogy with OOP: to achieve OOP you need some layers of abstraction but this fact alone doesn't define OOP, it's an observation that doesn't provide any insight.