✳flâneur — a map of the web's best reading

Imperative vs Declarative Programming

ui.dev · 2,347 words · saved by 1 readers

You won't get very far into learning React until you hear it – "React is declarative". But, what does that even mean? If you try to dive deeper, you inevitably come across a definition that looks something like this, comparing it to imperative programming. Imperative programming is how you do something, and declarative programming is more like what you do. That definition makes perfect sense... once you actually know the difference between imperative and declarative programming — but you don’t, which is why you're here. It’s like trying to answer What came first, the chicken or the egg? except everyone seems to think the chicken did, but you don’t even like eggs, and you’re confused. Combine this frustration with the bastardization of the actual word “declarative” to basically just mean good and all of a sudden your imposter syndrome is tap dancing on your confidence, and you realize you don’t even like programming that much. The hard part about this topic is, as my friend Merrick has

Imperative vs Declarative Programming Imperative vs Declarative Programming You won't get very far into learning React until you hear it – "React is declarative ". But, what does that even mean? If you try to dive deeper, you inevitably come across a definition that looks something like this, comparing it to imperative programming. 👁 Imperative vs Declarative Programming Imperative programming is how you do something, and declarative programming is more like what you do. That definition makes perfect sense... once you actually know the difference between imperative and declarative programming

Explore this link on the map →

related reading