We stand on guard
Apparently, 20,000 people on the last Canadian census declared their religion to be "Jedi." According to the Vancouver Sun:
It's also a "religion" that's growing around the world. In the United Kingdom, for example, there are more Jedis than Jews: 400,000 Jedis compared to 260,000 Jews. In a 2002 Australian census, more than 70,000 people named Jedi as their faith.
Dion can understand why. "[Jedi knights] have qualities people aspire to," he said in an interview from his office Tuesday. He wasn't wearing robes at the time, merely a golf shirt and black trousers.
"They do the right thing generally. And of course myself and a lot of people I know have the same kind of aspirations. We try to do the right thing all the time. And we follow Star Wars."
By the way, of those 20,000 Canadian Jedi, over half live in British Columbia -- Canada's acknowledged drug capital and the source of "B.C. bud," a marijuana strain so intense that the U.S.'s drug czar calls it the "crack" of marijuana.
(Thanks to Slashdot for this one!)
Posted by Clive Thompson at May 15, 2003 11:37 AM
Trackback Pings
TrackBack URL for this entry: http://www.collisiondetection.net/mt3/mt-tb.cgi/352
Now if we can only get it to catch on here and get a Jedi devout president elected, we'll be all set. JFK was the first Roman Catholic president in the 60's, which for the time was truly ground-breaking. You have my vote Clive in the next election as long as you "stand on gaurd".
Posted by: Rob Toole at May 18, 2003 6:44 PM
Put me down on the next ballot as a write-in candidate!
Is that still allowed? Write-in candidates, I mean?
Posted by: Clive at May 20, 2003 1:08 AM
Posted by: Online Casino at January 16, 2004 11:56 AM
This variable is then used in various lines of code, holding values given it by variable assignments along the way. In the course of its life, a variable can hold any number of variables and be used in any number of different ways. This flexibility is built on the precept we just learned: a variable is really just a block of bits, and those bits can hold whatever data the program needs to remember. They can hold enough data to remember an integer from as low as -2,147,483,647 up to 2,147,483,647 (one less than plus or minus 2^31). They can remember one character of writing. They can keep a decimal number with a huge amount of precision and a giant range. They can hold a time accurate to the second in a range of centuries. A few bits is not to be scoffed at.
Posted by: Elizabeth at January 19, 2004 6:19 PM
Inside each stack frame is a slew of useful information. It tells the computer what code is currently executing, where to go next, where to go in the case a return statement is found, and a whole lot of other things that are incredible useful to the computer, but not very useful to you most of the time. One of the things that is useful to you is the part of the frame that keeps track of all the variables you're using. So the first place for a variable to live is on the Stack. This is a very nice place to live, in that all the creation and destruction of space is handled for you as Stack Frames are created and destroyed. You seldom have to worry about making space for the variables on the stack. The only problem is that the variables here only live as long as the stack frame does, which is to say the length of the function those variables are declared in. This is often a fine situation, but when you need to store information for longer than a single function, you are instantly out of luck.
Posted by: Catherine at January 19, 2004 6:19 PM
Inside each stack frame is a slew of useful information. It tells the computer what code is currently executing, where to go next, where to go in the case a return statement is found, and a whole lot of other things that are incredible useful to the computer, but not very useful to you most of the time. One of the things that is useful to you is the part of the frame that keeps track of all the variables you're using. So the first place for a variable to live is on the Stack. This is a very nice place to live, in that all the creation and destruction of space is handled for you as Stack Frames are created and destroyed. You seldom have to worry about making space for the variables on the stack. The only problem is that the variables here only live as long as the stack frame does, which is to say the length of the function those variables are declared in. This is often a fine situation, but when you need to store information for longer than a single function, you are instantly out of luck.
Posted by: Catherine at January 19, 2004 6:21 PM
Post a comment
Now if we can only get it to catch on here and get a Jedi devout president elected, we'll be all set. JFK was the first Roman Catholic president in the 60's, which for the time was truly ground-breaking. You have my vote Clive in the next election as long as you "stand on gaurd".
Posted by: Rob Toole at May 18, 2003 6:44 PM
Put me down on the next ballot as a write-in candidate!
Is that still allowed? Write-in candidates, I mean?
Posted by: Clive at May 20, 2003 1:08 AM
Nice site. thx.
Posted by: Online Casino at January 16, 2004 11:56 AM
This variable is then used in various lines of code, holding values given it by variable assignments along the way. In the course of its life, a variable can hold any number of variables and be used in any number of different ways. This flexibility is built on the precept we just learned: a variable is really just a block of bits, and those bits can hold whatever data the program needs to remember. They can hold enough data to remember an integer from as low as -2,147,483,647 up to 2,147,483,647 (one less than plus or minus 2^31). They can remember one character of writing. They can keep a decimal number with a huge amount of precision and a giant range. They can hold a time accurate to the second in a range of centuries. A few bits is not to be scoffed at.
Posted by: Elizabeth at January 19, 2004 6:19 PM
Inside each stack frame is a slew of useful information. It tells the computer what code is currently executing, where to go next, where to go in the case a return statement is found, and a whole lot of other things that are incredible useful to the computer, but not very useful to you most of the time. One of the things that is useful to you is the part of the frame that keeps track of all the variables you're using. So the first place for a variable to live is on the Stack. This is a very nice place to live, in that all the creation and destruction of space is handled for you as Stack Frames are created and destroyed. You seldom have to worry about making space for the variables on the stack. The only problem is that the variables here only live as long as the stack frame does, which is to say the length of the function those variables are declared in. This is often a fine situation, but when you need to store information for longer than a single function, you are instantly out of luck.
Posted by: Catherine at January 19, 2004 6:19 PM
Inside each stack frame is a slew of useful information. It tells the computer what code is currently executing, where to go next, where to go in the case a return statement is found, and a whole lot of other things that are incredible useful to the computer, but not very useful to you most of the time. One of the things that is useful to you is the part of the frame that keeps track of all the variables you're using. So the first place for a variable to live is on the Stack. This is a very nice place to live, in that all the creation and destruction of space is handled for you as Stack Frames are created and destroyed. You seldom have to worry about making space for the variables on the stack. The only problem is that the variables here only live as long as the stack frame does, which is to say the length of the function those variables are declared in. This is often a fine situation, but when you need to store information for longer than a single function, you are instantly out of luck.
Posted by: Catherine at January 19, 2004 6:21 PM