I've come to the suspicion that it's not so much lack of understanding of grammar or inability to spell that's at the root of the than/then problem, but rather the inablity to hear/speak the difference. The English sounds represented by "e" and "a" are not very far apart. Many of the people might be conflating the two sounds into one. If this is the case, you can correct them until you're blue in the face and they'll never understand because they can't hear the difference. Proof reading their own work won't help because they won't hear the mistake.
I started thinking this way for two reasons: too many people saying "I could care less" when they really mean "I couldn't care less" (understandable, that t can be difficult to hear) and having Japanese students think I said "pet" when I said "pat" (I've taught English in Japan).
However, for this particular case, I've got a slightly different theory, based on my own mistakes: the writer sub-vocalizes while touch-typing and something between tongue, brain and fingers short circuited and instead of N, T was hit. The tongue is in the same place for both sounds, and when touch typing, the index finger on opposite hands is used for both letters (and the movement is rotationally symmetrical). The vast majority of my typos follow a similar pattern (and swapping N and T is very common for me). Heck, I sometimes make the same mistakes with pen and paper!
Of course most of us don't have the knowledge, but if we're motivated enough, we can obtain that knowledge. Worst case, we go to someone who does have the knowledge and say "here's $X, fix it". With closed drivers, none of that is even possible. You need $X**N to get noticed by most closed sources.
I suggest you brush up on your grammar. "projectile" is being used as an adverb, not a verb. However, "projectile" and "vomit" together form a compound verb. No different to "nose dive" or "duck walk".
Or install and enable multiarch. After a bit of futzing with the package, it works on 64bit debian sid, though you'll probably want to run xsetroot -cursor_name left_ptr after running steam (already a bug reported for that one:#2).
Ick, that's what real compilers (eg, gcc) are for: good warning messages (such as "suggest parenthesis around assignment used as truth value"), and better yet, -Werror. "if (1 == i)" is completely unnatural (for an English speaker anyway), which makes it more likely to forget to do 1 == i than it is to forget to double the equals sign. I too used to make the same mistake when I first started with C (having come from Pascal: that was fun:= became =, = became ==), but I quickly learned to double check my tests first when bug hunting. While mixing up = and == has become extremely rare for me (it helps that I usually test against some variant of 0 and thus can avoid using any operator other than !), I often mix up my other tests...
The thing with noise is it's impossible to eliminate completely. All that can be done is to knock off a few more dB, though I imagine the noise can be reduced to the point where it's sufficiently smaller than the resolution of the ADC that the bits don't shift. That said, any electrical equipment nearby will be producing a hum. Even if we can't hear it, the mic might pick it up. Then there's the magnetic fields affecting sheet metal, causing it to flex.
Short answer: epsilon.
I suspect a completely noise-free recording would raise just as many, if not more, eyebrows than a recording with a few discontinuities in the hum.
Possibly, but I suspect it might be even stronger than wood as rather than the glue adding structure to the paper, the paper is adding reinforcing to the glue. Either way, with the relative chaos in paper (compared to wood's distinct grain), the result seems to be extremely strong.
This is probably more appropriate as a response to the gp, but it also works as agreement with you: don't underestimate the strength of paper saturated with super-glue. I repaired the belt-clip of an Aiwa "walkman" by first super-gluing the parts together, then super-gluing paper across the joint (second attempt: first was just the parts, promptly re-broke). 20 years on, the repair was still solid.
Taken (with variations in the final word) from about 95% of the 2nd year junior high school English exams I marked.
In my opinion, any story using telepathy to overcome language barriers was written by either someone with no experience in just how different languages can be (eg, English vs Japanese), or someone with tongue very firmly planted in cheek (an onslaught of terrible bloody warfare). However, I do admit to a third possibility: the characters were lucky and their languages are similar enough that thinking processes readily translate, but different enough that speech doesn't.
Considering the stories I heard from my dad about the drapes fading (back in '89, I think it was), that story is far too plausible to dismiss.
There were, if I remember correctly, also worries about a population explosion due to daylight savings. The stories I hear about Queenslanders just baffle me (can anyone really be that dumb?), and I lived there for about 11 years (during which time, I heard most of the stories).
Yes, CO2 is heavier than either N2 or O2, but it is also bigger. I don't know how well it applies to gas molecules, but large balls in a sea of small balls will float to the top if you vibrate the whole lot.
No, his math is quite correct: M=d*4*pi*r^3, so M(p)/M(e) = (d*4*pi*r(p)^3)/(d*4*pi*r(e)) which simplifies to r(p)^3/r(e)^3, or (r(p)/r(e))^3, thus the ratio is the cube-root of 7: 1.913 (or 7.1: 1.922). Still, 2G would be a cow for us.
A wide is where the bowler screws up and, if the fielders screw up too (or the bowler really screwed up), the runners might run anyway. There are three ways to get out in cricket: the ball is caught off the bat, the ball hits the stumps (either because the batsman failed to block the ball as thrown by the bowler, or thrown/touched by any other fielder while the batsman is outside the wicket), or the ball (when thrown by the bowler) hits the batsman's leg, but otherwise would have hit the stumps (this is a judgment call by the referee). Otherwise, you can have two batsmen in there all day making life miserable for the fielders (odds are, if their in all day, they're really racking up runs).
Actually, I'd been working as a programmer for about 15 years before I heard of mind maps, and that was in a TESOL training course, so I suspect that not everyone knows what a mind map is.
Interesting that you bring up stutterwarp: it too had the radiation problem. After about 7.7ly (iirc, may have be pc), the charge built up on the components would collapse producing unshieldable hard-radiation (with what I'Ve since learned, probably just gamma rays at an intensity where sufficient shielding would make for an unmovable lump instead of a ship).
I don't believe FTL comms or travel will ever happen either. Sorry, I'm an engineer and rocket scientist. C isn't just a good idea, it's the law.
Anybody claiming to be any sort of scientist and then spouting that line is rather suspect in my book. Scientific laws are descriptions of observed behavior: the only reason C is "the law" is because we have yet to observe anything exceeding C.
Slashdot Mirror
Which still leaves zero as the first.
I've come to the suspicion that it's not so much lack of understanding of grammar or inability to spell that's at the root of the than/then problem, but rather the inablity to hear/speak the difference. The English sounds represented by "e" and "a" are not very far apart. Many of the people might be conflating the two sounds into one. If this is the case, you can correct them until you're blue in the face and they'll never understand because they can't hear the difference. Proof reading their own work won't help because they won't hear the mistake.
I started thinking this way for two reasons: too many people saying "I could care less" when they really mean "I couldn't care less" (understandable, that t can be difficult to hear) and having Japanese students think I said "pet" when I said "pat" (I've taught English in Japan).
However, for this particular case, I've got a slightly different theory, based on my own mistakes: the writer sub-vocalizes while touch-typing and something between tongue, brain and fingers short circuited and instead of N, T was hit. The tongue is in the same place for both sounds, and when touch typing, the index finger on opposite hands is used for both letters (and the movement is rotationally symmetrical). The vast majority of my typos follow a similar pattern (and swapping N and T is very common for me). Heck, I sometimes make the same mistakes with pen and paper!
Good grief, that joke got old back in '89 (before what's-her-name left the news, even). What's it doing still kicking around?
With support for sd cards, who needs storage other than for the OS itself?
Of course most of us don't have the knowledge, but if we're motivated enough, we can obtain that knowledge. Worst case, we go to someone who does have the knowledge and say "here's $X, fix it". With closed drivers, none of that is even possible. You need $X**N to get noticed by most closed sources.
I suggest you brush up on your grammar. "projectile" is being used as an adverb, not a verb. However, "projectile" and "vomit" together form a compound verb. No different to "nose dive" or "duck walk".
Or install and enable multiarch. After a bit of futzing with the package, it works on 64bit debian sid, though you'll probably want to run xsetroot -cursor_name left_ptr after running steam (already a bug reported for that one:#2).
Ick, that's what real compilers (eg, gcc) are for: good warning messages (such as "suggest parenthesis around assignment used as truth value"), and better yet, -Werror. "if (1 == i)" is completely unnatural (for an English speaker anyway), which makes it more likely to forget to do 1 == i than it is to forget to double the equals sign. I too used to make the same mistake when I first started with C (having come from Pascal: that was fun := became =, = became ==), but I quickly learned to double check my tests first when bug hunting. While mixing up = and == has become extremely rare for me (it helps that I usually test against some variant of 0 and thus can avoid using any operator other than !), I often mix up my other tests...
The thing with noise is it's impossible to eliminate completely. All that can be done is to knock off a few more dB, though I imagine the noise can be reduced to the point where it's sufficiently smaller than the resolution of the ADC that the bits don't shift. That said, any electrical equipment nearby will be producing a hum. Even if we can't hear it, the mic might pick it up. Then there's the magnetic fields affecting sheet metal, causing it to flex.
Short answer: epsilon.
I suspect a completely noise-free recording would raise just as many, if not more, eyebrows than a recording with a few discontinuities in the hum.
It's the wires into the high-gain mic amp that pick up the hum.
Angry Birds and Minecraft, I imagine. :/
Possibly, but I suspect it might be even stronger than wood as rather than the glue adding structure to the paper, the paper is adding reinforcing to the glue. Either way, with the relative chaos in paper (compared to wood's distinct grain), the result seems to be extremely strong.
This is probably more appropriate as a response to the gp, but it also works as agreement with you: don't underestimate the strength of paper saturated with super-glue. I repaired the belt-clip of an Aiwa "walkman" by first super-gluing the parts together, then super-gluing paper across the joint (second attempt: first was just the parts, promptly re-broke). 20 years on, the repair was still solid.
Exactly. Thus the quote :)
Taken (with variations in the final word) from about 95% of the 2nd year junior high school English exams I marked.
In my opinion, any story using telepathy to overcome language barriers was written by either someone with no experience in just how different languages can be (eg, English vs Japanese), or someone with tongue very firmly planted in cheek (an onslaught of terrible bloody warfare). However, I do admit to a third possibility: the characters were lucky and their languages are similar enough that thinking processes readily translate, but different enough that speech doesn't.
Considering the stories I heard from my dad about the drapes fading (back in '89, I think it was), that story is far too plausible to dismiss.
There were, if I remember correctly, also worries about a population explosion due to daylight savings. The stories I hear about Queenslanders just baffle me (can anyone really be that dumb?), and I lived there for about 11 years (during which time, I heard most of the stories).
Yes, CO2 is heavier than either N2 or O2, but it is also bigger. I don't know how well it applies to gas molecules, but large balls in a sea of small balls will float to the top if you vibrate the whole lot.
No, his math is quite correct: M=d*4*pi*r^3, so M(p)/M(e) = (d*4*pi*r(p)^3)/(d*4*pi*r(e)) which simplifies to r(p)^3/r(e)^3, or (r(p)/r(e))^3, thus the ratio is the cube-root of 7: 1.913 (or 7.1: 1.922). Still, 2G would be a cow for us.
You're showing a lack of knowledge of crumpets.
A wide is where the bowler screws up and, if the fielders screw up too (or the bowler really screwed up), the runners might run anyway. There are three ways to get out in cricket: the ball is caught off the bat, the ball hits the stumps (either because the batsman failed to block the ball as thrown by the bowler, or thrown/touched by any other fielder while the batsman is outside the wicket), or the ball (when thrown by the bowler) hits the batsman's leg, but otherwise would have hit the stumps (this is a judgment call by the referee). Otherwise, you can have two batsmen in there all day making life miserable for the fielders (odds are, if their in all day, they're really racking up runs).
Actually, I'd been working as a programmer for about 15 years before I heard of mind maps, and that was in a TESOL training course, so I suspect that not everyone knows what a mind map is.
There's always Earthdark :)
But yeah, I too twitched when I read that bit.
The answer is simple: why bother?
Resources? Anything down here, there's more of out there, without pesky gravity wells.
Bio-mass? If 500kg of energy isn't a problem, then converting the above resources will be more efficient.
Contact? With friends like us, who needs enemies?
Slaves? What, you think we got to (near) the top of the dung-heap without a fight?
Extermination? Well, ok, but be glad space is big, very big. Obviously nobody capable within a 60ly radius.
Interesting that you bring up stutterwarp: it too had the radiation problem. After about 7.7ly (iirc, may have be pc), the charge built up on the components would collapse producing unshieldable hard-radiation (with what I'Ve since learned, probably just gamma rays at an intensity where sufficient shielding would make for an unmovable lump instead of a ship).
I don't believe FTL comms or travel will ever happen either. Sorry, I'm an engineer and rocket scientist.
C isn't just a good idea, it's the law.
Anybody claiming to be any sort of scientist and then spouting that line is rather suspect in my book. Scientific laws are descriptions of observed behavior: the only reason C is "the law" is because we have yet to observe anything exceeding C.
So this is how Curiosity kills cats? I guess the next mission needs to be called Satisfaction.