Modern "food" turkeys have such huge breasts that they are physically unable to breed without human help.
Even if they escaped their pens, they'd be doomed to extinction.
Modern bananas have been bred totally seedless, like various grape varieties. They spread entirely by grafting.
So they too would soon die off.
The article mocks Poodles, but I wonder a bit about that. They're actually considered one of the
smartest breeds of dog there is, and that must be worth something when a major change in lifestyle is called for.
I have spent the last five years trying to finish Descent3.
I'm not exaggerating. Every now and then I'll slog through another
half a level or so, invariably getting killed a few times. What with its full
6-degrees of freedom and insanely squirrely foes, it has got to be the most difficult
FPS game I've encountered.
Some years back when mayhem was happening to a local 2m NBFM repeater, I got into the habit
of leaving an allmode radio monitoring the input, in USB mode. That lets you hear exactly what
the FM carrier is doing.
All FM radios have a different keyup chirp. That is, when you key up they start on some frequency and drift
off to their final frequency over a short period of time. Some do it quickly, some slowly, but all start off on
and end on a different pair of frequency. Some would also have a tendency to AM on top of their FM,
and others would have other artifacts.
After listening for a few weeks I could recognize all the regulars as soon as they'd key up.
Have you actually measured a "two by four"? Its dimensions are nowhere near 2 by 4. They're around 1 and 1/2 inches by 3 and 7/16 inches.
Try it yourself if you don't believe me.
It's far more accurate to call it a "four by nine", using centimeters, than "two by four" in inches.
"Two by four inches" is off the truth by a whopping ~25%, while "four by nine" in cm is within 5% of the truth.
In case you're curious, it has to do with trimming: a "two by four" is the size coming off the first sawmill. After that it's
trimmed down and sanded to the size that actually gets used in construction, which is around 4x9 cm. "Two by four" today is
really just a designation.
The problem as I understand it is that the RGB sensors in the retina (cone cells) are tuned to slightly
different frequencies for every person. It never quite matches the RGB phosphor in a CRT.
This becomes most obvious when you set up grey scale. Everybody has their own idea of when it looks "grey".
One guy in our shop in particular must have had his eyes' green sensors quite a bit tuned off, because he always
liked to crank up the green. I was often accused of using too much blue.
I have been to two different opthalmologists over the past few years,
and both of them wear regular glasses. They don't even use contact lenses.
Their explanation in both cases was the same: we really don't know the
long-term effects of PRK/LASIK/LASEK. It could have side effects (triggering
glaucoma, etc) that would render you near blind in 30 years. Is it really
worth that risk?
So I'm sticking with glasses. For one thing, I'm over 40 and while I'm
still nearsighted, normal age-related presbyopia is setting in. I can
deal with it by simply removing my glasses to look at things that are up
close. If I had LASIK, I'd need to carry reading glasses with me all
the time, so there's not much of a win.
An interesting aside: as reported by Bruce Schneier, al Qaeda members avoid Echelon by using shared Hotmail accounts. Rather than sending email, they create drafts and save them, and have a running conversation in the draft before deleting it. Not sending the email means the email doesn't trigger midpoint monitoring.
Interesting point. But, the same draft being repeatedly saved,
especially from very different IP addresses, should also be very easy
to spot. Deleting it after many edits would stick out even more.
But, if https is being used, this would require cooperation from the
server people to detect. I wonder if hotmail, yahoo and gmail are
already doing this?
Have you ever used morse code? It is it's own language. There are so many abbreviations and prosigns that you can communicate through it if you don't share a common language with the guy on the other end.
I have used morse code, since 1990 in fact. But strictly speaking, Morse code is just an encoding.
Here, watch this:
FB OM UR 599 HR ES TX FER FB QSO K
There is no morse code there. There are no dots and dashes.
What you are looking at is ASCII encoding of a lot of prosigns
and abbreviations that are commonly used on CW.
Note there is nothing stopping you from sending,
using Morse Code:
OK FRIEND I GOT ALL THAT, YOUR SIGNAL REPORT IS 599 HERE, AND THANK YOU FOR THE NICE CONVERSATION, OVER TO YOU
...except that the person on the other end would get impatient.
Anyway, that's the difference between encoding and language.
The confusion arises because the language of Q prosigns
and abbreviations are mostly used while doing Morse code.
Note that people do use many of those same prosigns and
abbreviations while using RTTY or PSK31, and there is
obviously no Morse Code involved there at all.
A dSLR like a Canon EOS line can be as "pro-sumer" intricate as you might want, but it
can also be set to full auto P&S mode. And it does an awesome job. In fact, I find it a bit
depressing how in full auto mode it far too often tends to set everything just how I wanted it anyway.
You point and squeeze. It uses 9 sensing points, cleverly figures out which ones you probably wanted
from the framing, perhaps pops up the flash automatically to fire off a few blips of light to fine
tune the focus and figure out what a good ISO and shutter/exposure setting would be given the scene and
if it really will need the flash, guesses a reasonable white balance and - kaclick - squeezes off yet
another impressively good picture.
Yet all you did was point and click. The camera turn-on lag is a tiny fraction of a second,
and it typically shoots at a rate of around 5 frames per second, which easily
matches or beats a film SLR. In full auto it's like a machine gun.
Really the only drawbacks are that they're bulky and expensive.
Devices using the new chip should reach consumers by late 2007 and will feature high-speed, high-megapixel digital photography capabilities normally found in more expensive, single-lens reflex cameras.
Uh, what makes the single-lens reflex cameras so good is not
so much the big sensor, but the fancy-ass $800 lenses,
through-lens multi-point sensing, precision alignment, etc.
It's pointless to put an 8 megapixel sensor behind a cheap lens.
The image will still be just as blurry, colour-fringed,
barrel distorted, and unevenly exposed. It's just that now
the defects will be 20 pixels wide instead of 2.
I haven't seen anybody around here except you claim that
Java is a "multithreading-safe language". I can't even imagine
what such a concept is.
The only claims I've seen by others is that it is easy to do
multithreaded coding in Java, because the language was
designed with it in mind. For example, consider this:
synchronized (myMutex) {... }
"myMutex" can be any object. "synchronized"
is syntax. Only the thread that "won" the myMutex object
will be running the code inside the braces; any other thread
trying to synchronize on myMutex will block. Note that if the
code in that block indirectly tries to synchronize on myMutex
again, it will quietly succeed, which is nice. Also, if
you get something like a null pointer exception inside that
block, you can still rest assured that myMutex will be
automatically un-owned when you exit the block.
There are loads of other features too of course (somebody
else already mentioned that it'll actually show you deadlocks),
but really the point is just that it's awfully easy to do the basics.
You are perfectly free to use a single object as a mutex,
shared between as many classes or threads as you want in Java.
And of course, this includes making a single global lock if you
want to. It's trivial to do.
I have certainly never felt that java has "encouraged" me in any
way to make lots of mutexes.
I read books from the 1800's and 1900's regularly, and while the language may sometimes seem
a bit stilted and quirky I have never found a case where they have done something as
stupid and evil as use an incorrect homophone just because it was shorter to type.
What you're suggesting means that Google's principle "Do No Evil" could mean "Do Know Evil".
Or maybe it means "Do Know e-Ville"?
Spelling matters. I'm tired of cryptic email that is so full of typos, misspellings and
mangled grammar that it could mean ten different things.
What's the actual Norwegian phrase? I speak Swedish, but "häng honom, inte vänta tills jag kommer"
sounds as strange as the English example. It would have to be "vänta inte" to make sense.
a paint fleck on one extremity would have at least sent it spinning and significantly altered its course
Low earth orbit velocity is 7800m/s. The most likely, and worst way, to get hit by a paint fleck is to get hit
by one in the same orbit but in the opposite direction, which would be a delta vee of 2*7800m/s.
Let's be really generous and say a paint fleck weighs 1g and hits the suitsat (say 100kg) dead on.
By conservation of momentum, the suit's velocity will decrease from 7800m/s to... 7799.844 m/s.
In other words, it'll still be at 99.998% of it's original velocity. I won't bother calculating how little
the fleck could have affected the spin, because it's not like the suit was spin stabilized to begin with.
Spin fade was expected to begin with. The only significance of the fleck is that it would cause the
suit to (slowly) depressurize, but more importantly possible trash the equipment if it was in the way.
My guess is that since the equipment wasn't really designed for this kind of orbital abuse:
the nasty temperature shift between night and day just caused caused some circuitry to fail
from thermal expansion. Or perhaps the suit leaked; the equipment wasn't designed to work
in a hard vacuum.
There are lots of extra analogue controls on the throttle;
look at the website.
For collective, you could either use the thumb slider,
or either of those two round rotary buttons. Those are all
analogue controls. The thumb slider is probably your best bet
since it's the easiest to adjust.
That joystick has a total of 11 axes and 34 buttons.
Slashdot Mirror
Here ya go. A SanDisk Ultra II SD Plus card.
I have one. An SD card that is also a USB drive.
Modern "food" turkeys have such huge breasts that they are physically unable to breed without human help. Even if they escaped their pens, they'd be doomed to extinction.
Modern bananas have been bred totally seedless, like various grape varieties. They spread entirely by grafting. So they too would soon die off.
The article mocks Poodles, but I wonder a bit about that. They're actually considered one of the smartest breeds of dog there is, and that must be worth something when a major change in lifestyle is called for.
"Bastu" is a perfectly good and quite old Swedish word, originally coming from "bad stuga", which basically means "bath house".
The word is around 500 years old, for crying out loud.
It is an abbreviation for "hear, all ye good people, hear what this brilliant and eloquent speaker has to say!" .
I don't normally nitpick, but "here here" doesn't even make sense. "Hear, hear" does.
If you tell us what this is hiding, will they have to kill you?
I have spent the last five years trying to finish Descent3.
I'm not exaggerating. Every now and then I'll slog through another half a level or so, invariably getting killed a few times. What with its full 6-degrees of freedom and insanely squirrely foes, it has got to be the most difficult FPS game I've encountered.
Well, I'm certainly getting my money's worth.
Let met put it this way: it is untrue that it is not the case that the Wii will fail to not be region-locked. Clear?
Eh? Blu-ray is 50G, while HD-DVD is 30G (double sided, in both cases). In other words, Blu-ray currently holds 67% more data than HD-DVD.
The theoretical limits are 200G vs 60G respectively (see here).
I'd call that pretty significant.Some years back when mayhem was happening to a local 2m NBFM repeater, I got into the habit of leaving an allmode radio monitoring the input, in USB mode. That lets you hear exactly what the FM carrier is doing.
All FM radios have a different keyup chirp. That is, when you key up they start on some frequency and drift off to their final frequency over a short period of time. Some do it quickly, some slowly, but all start off on and end on a different pair of frequency. Some would also have a tendency to AM on top of their FM, and others would have other artifacts.
After listening for a few weeks I could recognize all the regulars as soon as they'd key up.
Ah, the irony.
Have you actually measured a "two by four"? Its dimensions are nowhere near 2 by 4. They're around 1 and 1/2 inches by 3 and 7/16 inches. Try it yourself if you don't believe me.
It's far more accurate to call it a "four by nine", using centimeters, than "two by four" in inches. "Two by four inches" is off the truth by a whopping ~25%, while "four by nine" in cm is within 5% of the truth.
In case you're curious, it has to do with trimming: a "two by four" is the size coming off the first sawmill. After that it's trimmed down and sanded to the size that actually gets used in construction, which is around 4x9 cm. "Two by four" today is really just a designation.
The problem as I understand it is that the RGB sensors in the retina (cone cells) are tuned to slightly different frequencies for every person. It never quite matches the RGB phosphor in a CRT.
This becomes most obvious when you set up grey scale. Everybody has their own idea of when it looks "grey". One guy in our shop in particular must have had his eyes' green sensors quite a bit tuned off, because he always liked to crank up the green. I was often accused of using too much blue.
You can also crank up "Informative" if you wish.
Their explanation in both cases was the same: we really don't know the long-term effects of PRK/LASIK/LASEK. It could have side effects (triggering glaucoma, etc) that would render you near blind in 30 years. Is it really worth that risk?
So I'm sticking with glasses. For one thing, I'm over 40 and while I'm still nearsighted, normal age-related presbyopia is setting in. I can deal with it by simply removing my glasses to look at things that are up close. If I had LASIK, I'd need to carry reading glasses with me all the time, so there's not much of a win.
Linux supports many winmodems. You can see if yours is supported here.
Interesting point. But, the same draft being repeatedly saved, especially from very different IP addresses, should also be very easy to spot. Deleting it after many edits would stick out even more.
But, if https is being used, this would require cooperation from the server people to detect. I wonder if hotmail, yahoo and gmail are already doing this?
I have used morse code, since 1990 in fact. But strictly speaking, Morse code is just an encoding. Here, watch this:
FB OM UR 599 HR ES TX FER FB QSO K
There is no morse code there. There are no dots and dashes. What you are looking at is ASCII encoding of a lot of prosigns and abbreviations that are commonly used on CW.
Note there is nothing stopping you from sending, using Morse Code:
OK FRIEND I GOT ALL THAT, YOUR SIGNAL REPORT IS 599 HERE, AND THANK YOU FOR THE NICE CONVERSATION, OVER TO YOU
...except that the person on the other end would get impatient.
Anyway, that's the difference between encoding and language. The confusion arises because the language of Q prosigns and abbreviations are mostly used while doing Morse code.
Note that people do use many of those same prosigns and abbreviations while using RTTY or PSK31, and there is obviously no Morse Code involved there at all.
You point and squeeze. It uses 9 sensing points, cleverly figures out which ones you probably wanted from the framing, perhaps pops up the flash automatically to fire off a few blips of light to fine tune the focus and figure out what a good ISO and shutter/exposure setting would be given the scene and if it really will need the flash, guesses a reasonable white balance and - kaclick - squeezes off yet another impressively good picture.
Yet all you did was point and click. The camera turn-on lag is a tiny fraction of a second, and it typically shoots at a rate of around 5 frames per second, which easily matches or beats a film SLR. In full auto it's like a machine gun.
Really the only drawbacks are that they're bulky and expensive.
Uh, what makes the single-lens reflex cameras so good is not so much the big sensor, but the fancy-ass $800 lenses, through-lens multi-point sensing, precision alignment, etc.
It's pointless to put an 8 megapixel sensor behind a cheap lens. The image will still be just as blurry, colour-fringed, barrel distorted, and unevenly exposed. It's just that now the defects will be 20 pixels wide instead of 2.
Or you could compare it to a DVD of "Dumb and Dumber", which at 4.7G is 188 times bigger than your 25M quarter-million line code project.
In short, bulk? Don't go there.
The only claims I've seen by others is that it is easy to do multithreaded coding in Java, because the language was designed with it in mind. For example, consider this:
"myMutex" can be any object. "synchronized" is syntax. Only the thread that "won" the myMutex object will be running the code inside the braces; any other thread trying to synchronize on myMutex will block. Note that if the code in that block indirectly tries to synchronize on myMutex again, it will quietly succeed, which is nice. Also, if you get something like a null pointer exception inside that block, you can still rest assured that myMutex will be automatically un-owned when you exit the block.There are loads of other features too of course (somebody else already mentioned that it'll actually show you deadlocks), but really the point is just that it's awfully easy to do the basics.
I have certainly never felt that java has "encouraged" me in any way to make lots of mutexes.
I read books from the 1800's and 1900's regularly, and while the language may sometimes seem a bit stilted and quirky I have never found a case where they have done something as stupid and evil as use an incorrect homophone just because it was shorter to type.
What you're suggesting means that Google's principle "Do No Evil" could mean "Do Know Evil". Or maybe it means "Do Know e-Ville"?
Spelling matters. I'm tired of cryptic email that is so full of typos, misspellings and mangled grammar that it could mean ten different things.
What's the actual Norwegian phrase? I speak Swedish, but "häng honom, inte vänta tills jag kommer" sounds as strange as the English example. It would have to be "vänta inte" to make sense.
Low earth orbit velocity is 7800m/s. The most likely, and worst way, to get hit by a paint fleck is to get hit by one in the same orbit but in the opposite direction, which would be a delta vee of 2*7800m/s.
Let's be really generous and say a paint fleck weighs 1g and hits the suitsat (say 100kg) dead on. By conservation of momentum, the suit's velocity will decrease from 7800m/s to... 7799.844 m/s.
In other words, it'll still be at 99.998% of it's original velocity. I won't bother calculating how little the fleck could have affected the spin, because it's not like the suit was spin stabilized to begin with. Spin fade was expected to begin with. The only significance of the fleck is that it would cause the suit to (slowly) depressurize, but more importantly possible trash the equipment if it was in the way.
My guess is that since the equipment wasn't really designed for this kind of orbital abuse: the nasty temperature shift between night and day just caused caused some circuitry to fail from thermal expansion. Or perhaps the suit leaked; the equipment wasn't designed to work in a hard vacuum.
For collective, you could either use the thumb slider, or either of those two round rotary buttons. Those are all analogue controls. The thumb slider is probably your best bet since it's the easiest to adjust.
That joystick has a total of 11 axes and 34 buttons.