Why Game of Thrones is less realistic than you think

And somehow they got onto the internet.

It was a long and winding road, but here I am. Now deal with it.
"If it doesn't kill you, I will make you suffer"




Anyway. As the links in the article show, most of GoT is based on real events but just because it is "based" doesn't mean it is true.

("based" == true) = true
but
("based" === true) != true *

It's a bit like people believing that the names in Fargo has really been changed at the request of the survivors.




* Programmer joke. Expecting somebody to point out a null exception at any moment.
 
("based" == true) = true
but
("based" === true) != true *

* Programmer joke. Expecting somebody to point out a null exception at any moment.

The first expression won't work. You can't use the left-hand side of an assignment as a boolean expression. In JavaScript "based" == true will probably evaluate to false as the value comparison isn't the same (as opposed to "true" == true), but both ( "based" ) and (true) will evaluate to true individually. So ("based" == true) == false.

The last expression will evaluate to true, as the type and value comparison of ("based" === true) == false, which is the same as != true. So the whole expression evaluates to "true".
 
Not quite sure if everyone is being serious in this thread, but it seems Rhymelark is the only one who understood the article. :p
 
The first expression won't work. You can't use the left-hand side of an assignment as a boolean expression. In JavaScript "based" == true will probably evaluate to false as the value comparison isn't the same (as opposed to "true" == true), but both ( "based" ) and (true) will evaluate to true individually. So ("based" == true) == false.

The last expression will evaluate to true, as the type and value comparison of ("based" === true) == false, which is the same as != true. So the whole expression evaluates to "true".

It's written in pseudo pseudo-code, the X-mas gifts of programming: It's the thought that counts.
 
Back
Top