yeah, sometimes I ask questions and people also don't seem to understand it fully... some say you have to use a key={id} or else if you use key={index} the data on screen may show incorrect data but when everything is correct people don't know why and how to show an example of it not working. (and I later found out the data on screen won't be incorrect; it is just inefficient).
Is this so-called "declarative way" of programming instead of imperative? If you tell me use setA intersect setB and it is "declarative" and don't write a loop to do it imperatively, that I understand completely. React / Redux's way of "declarative" somehow isn't that fully understood. A lot of times, it is do this, do that, and you will have it. It is similar to Ruby on Rails and "pragmatic" way of programming: just do this and do that and it should work and people don't know why or how it works that deeply.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
=)
yeah, sometimes I ask questions and people also don't seem to understand it fully... some say you have to use a
key={id}or else if you usekey={index}the data on screen may show incorrect data but when everything is correct people don't know why and how to show an example of it not working. (and I later found out the data on screen won't be incorrect; it is just inefficient).Is this so-called "declarative way" of programming instead of imperative? If you tell me use setA intersect setB and it is "declarative" and don't write a loop to do it imperatively, that I understand completely. React / Redux's way of "declarative" somehow isn't that fully understood. A lot of times, it is do this, do that, and you will have it. It is similar to Ruby on Rails and "pragmatic" way of programming: just do this and do that and it should work and people don't know why or how it works that deeply.