Skip to main content
Fix poor Isaac's name
Source Link
DavidW
  • 142.6k
  • 34
  • 608
  • 750

To quote IssacIsaac Asimov's laws of robotics, emphasis mine:

To quote Issac Asimov's laws of robotics, emphasis mine:

To quote Isaac Asimov's laws of robotics, emphasis mine:

Rolled back added commentary and incorrect grammar and punctuation; corrected the two instances where the editor was actually correvt.
Source Link
Gnemlock
  • 2k
  • 1
  • 21
  • 34

The rules are not an absolute fact. They are not there to say "robots will never harm a human, and will always save the day, when present". We know this by how the movie plays out. The rules are simply the rules used to govern the actions of the robots, in-verse. As a programmer, this is something that is blatantly obvious to me; but I am confidantconfident that it is not as so for others that are not familiar with how strictly adherent any computer system is.

The point is, the rule does not state anything about it "not counting" because the robot is "already saving someone". As such, only considering this explicit rule (as any computer or robot would interpret, at least), there is no allowance for a situation where the robot can only save one of two people in danger. In actual computer science, only considering the explicit rule, such an event would likely cause an infinite loop. The robot would stop where it was, and continue to process the catch-22 forever; or atleastat least, until its logic kicked it out of the thought process. At this point, the robot would dump its memory of the current event, and move on. In theory.

The rules are not an absolute fact. They are not there to say "robots will never harm a human, and will always save the day, when present". We know this by how the movie plays out. The rules are simply the rules used to govern the actions of the robots, in-verse. As a programmer, this is something that is blatantly obvious to me; but I am confidant that it is not as so for others that are not familiar with how strictly adherent any computer system is.

The point is, the rule does not state anything about it "not counting" because the robot is "already saving someone". As such, only considering this explicit rule (as any computer or robot would interpret, at least), there is no allowance for a situation where the robot can only save one of two people in danger. In actual computer science, only considering the explicit rule, such an event would likely cause an infinite loop. The robot would stop where it was, and continue to process the catch-22 forever; or atleast, until its logic kicked it out of the thought process. At this point, the robot would dump its memory of the current event, and move on. In theory.

The rules are not an absolute fact. They are not there to say "robots will never harm a human, and will always save the day, when present". We know this by how the movie plays out. The rules are simply the rules used to govern the actions of the robots, in-verse. As a programmer, this is something that is blatantly obvious to me; but I am confident that it is not as so for others that are not familiar with how strictly adherent any computer system is.

The point is, the rule does not state anything about it "not counting" because the robot is "already saving someone". As such, only considering this explicit rule (as any computer or robot would interpret, at least), there is no allowance for a situation where the robot can only save one of two people in danger. In actual computer science, only considering the explicit rule, such an event would likely cause an infinite loop. The robot would stop where it was, and continue to process the catch-22 forever; or at least, until its logic kicked it out of the thought process. At this point, the robot would dump its memory of the current event, and move on. In theory.

Rollback to Revision 4
Source Link
Gnemlock
  • 2k
  • 1
  • 21
  • 34

The rules are not an absolute fact. They are not there to say "robots will never harm a human, and will always save the day, when present". We know this by how the movie plays out. The rules are simply the rules used to govern the actions of the robots, in-verse. As a programmer, this is something that is blatantly obvious to me; but I am confidentconfidant that it is not as so for others that are not familiar with how strictly adherent any computer system is.

The point is, the rule does not state anything about it "not counting" because the robot is "already saving someone". As such, only considering this explicit rule (as any computer or robot would interpret, at least), there is no allowance for a situation where the robot can only save one of two people in danger. In actual computer science, only considering the explicit rule, such an event would likely cause an infinite loop. The robot would stop where it was, and continue to process the catch-22 forever; or at leastatleast, until its logic kicked it out of the thought process. At this point, the robot would dump its memory of the current event, and move on. In theory.

In verse, the rules are a lot more complicated; at least, internal to the robot. There would likely be a whole lot of special cases, when processing the core rules, to determine how to act in such situations. As a result, the robot is still able to act, and takes the most logical outcome. It only saves Will, but it does save someone.

In regards to how the robot would actually process these rules, it would not be breaking the rules, at all. There would be a far more complex series of "if..." and "else..." logic, where the robot'srobots logic would would allow it to go against these base rules in situations where logic dictates that no matter what option, a human would still come to harm.

The rules are not an absolute fact. They are not there to say "robots will never harm a human, and will always save the day, when present". We know this by how the movie plays out. The rules are simply the rules used to govern the actions of the robots, in-verse. As a programmer, this is something that is blatantly obvious to me; but I am confident that it is not as so for others that are not familiar with how strictly adherent any computer system is.

The point is, the rule does not state anything about it "not counting" because the robot is "already saving someone". As such, only considering this explicit rule (as any computer or robot would interpret, at least), there is no allowance for a situation where the robot can only save one of two people in danger. In actual computer science, only considering the explicit rule, such an event would likely cause an infinite loop. The robot would stop where it was, and continue to process the catch-22 forever; or at least, until its logic kicked it out of the thought process. At this point, the robot would dump its memory of the current event, and move on. In theory.

In verse, the rules are a lot more complicated; at least, internal to the robot. There would likely be a whole lot of special cases, when processing the core rules, to determine how to act in such situations. As a result, the robot is still able to act and takes the most logical outcome. It only saves Will, but it does save someone.

In regards to how the robot would actually process these rules, it would not be breaking the rules, at all. There would be a far more complex series of "if..." and "else..." logic, where the robot's logic would allow it to go against these base rules in situations where logic dictates that no matter what option, a human would still come to harm.

The rules are not an absolute fact. They are not there to say "robots will never harm a human, and will always save the day, when present". We know this by how the movie plays out. The rules are simply the rules used to govern the actions of the robots, in-verse. As a programmer, this is something that is blatantly obvious to me; but I am confidant that it is not as so for others that are not familiar with how strictly adherent any computer system is.

The point is, the rule does not state anything about it "not counting" because the robot is "already saving someone". As such, only considering this explicit rule (as any computer or robot would interpret, at least), there is no allowance for a situation where the robot can only save one of two people in danger. In actual computer science, only considering the explicit rule, such an event would likely cause an infinite loop. The robot would stop where it was, and continue to process the catch-22 forever; or atleast, until its logic kicked it out of the thought process. At this point, the robot would dump its memory of the current event, and move on. In theory.

In verse, the rules are a lot more complicated; at least, internal to the robot. There would likely be a whole lot of special cases, when processing the core rules, to determine how to act in such situations. As a result, the robot is still able to act, and takes the most logical outcome. It only saves Will, but it does save someone.

In regards to how the robot would actually process these rules, it would not be breaking the rules, at all. There would be a far more complex series of "if.." and "else.." logic, where the robots logic would allow it to go against these base rules in situations where logic dictates that no matter what option, a human would still come to harm.

Reminder of Asimov's later introduction of the Zeroth Law of Robotics. This might have relevance in some of the other situations used to elicit analogies.
Source Link
Edlothiad
  • 77.8k
  • 32
  • 397
  • 383
Loading
Reminder of Asimov's later introduction of the Zeroth Law of Robotics. This might have relevance in some of the other situations used to elicit analogies.
Source Link
Loading
ofcourse I was using code format as quote format <.<
Source Link
Gnemlock
  • 2k
  • 1
  • 21
  • 34
Loading
Reformatted quote. Quotes should use quote formatting, code blocks wreak havoc with screen readers and other accessibility devices.
Source Link
Loading
could not emphasis; formatting did not want to work.
Source Link
Gnemlock
  • 2k
  • 1
  • 21
  • 34
Loading
Source Link
Gnemlock
  • 2k
  • 1
  • 21
  • 34
Loading