pssst.... actually, "cancer" has the same exact cause.... mutated cells reproducing out of control...
No, that is the definition of cancer, not the cause. Cause != symptom. Example: a large portion of cancers, are in part, caused by a disabled p53 gene.
find something that targets and destroys these mutant cells, boom, cure for cancer... find something that cuts off the blood supply to said mutant cells, boom! cure for cancer...
Unfortunately, a cure that non-specific also targets normal stem cells, and the treatment actually curing cancer vs. killing the patient becomes a dice game that works on small cancers.
Now, what CAUSES the cells to go haywire is a good thing to target.
everyone has cancer cells (newsflash!)
No, everyone has cells that have the potential to become cancerous, and most people develop cancer cells at some point during their lives. It's a small difference, but you seem to want to be really nitpicky here...
Although, reading the other comments, my description is obviously the one least likely to be near-term useful and relevant (especially given the fact that turning off this gene doesn't eliminate other cells).
You find out what creates a something by turning it off.
For example, they E4bp4 gene is needed to make NK cells from blood stem cells. They now know that one of the steps in generating NK cells from the listed stem cells involves the protein E4bp4 gene. Using information about this and other relevant proteins (both that they have found, and that they haven't found, once they are found), they will be able to devise procedures for converting these stem cells (possibly from the original patient, eliminating or reducing rejection issues) to NK cells.
The problem with "a cure for cancer", is that cancer isn't one disease. Also there are many causes.
That being said, reliable treatments (cures) for different types of cancers can still be developed. However, no cure for cancer could ever prevent a relapse, unless it treated the genetic factors involved, and was taken regularly through a person's life. Even then, only cancers derived from the cause that the treatment targets, will be prevented.
Another possibility (not saying yours is wrong, but this "correction", is probably another factor).
[..] It makes sense evolutionarily speaking. Boys grow to be men and need to be able to not be afraid (or at least keep that fear in check) while doing stupid but impressive things to show potential mates that they are strong. [...]
I've only had problems with sprint when I'm way out in desolate areas (mostly parts of the UP of Michigan), or in area where there's significant signal blockage (my basement, where nobody's phone works well). Aside from that, most of Ohio and adjacent states work just fine for the sprint phones I've had (and the people I've known using them). Sure it's anecdotal, but at this point, even that's more than what you've provided.
Odd, I don't use Linux, and the simple choice is still EXT2. Primarily I use Windows and FreeBSD.
The thing is, ext2 doesn't have the size limit of FAT32, it handles hard links properly, and it's available on pretty much any OS (well, any *BSD, Windows, Linux, and MacOS).
And before you say windows can't use EXT2, yes it can. That's the nicer driver, there are several that let you access EXT2 with an FTP like client. This one actually lets you mount the drive.
I just make sure Linux and FreeBSD have my account on the same UID, and Windows seems to default to superuser mode.
Its funny that you shoot people, hijack cars, drive over people and do all kinds of illegal things but when theres normal activities like sex that all people do, everyone goes "oh my god things like that shouldn't be allowed!" and bring in the lawsuits.
OK, you typed that on slashdot. Please tell me you didn't have a straight face while doing so...
I would hope so, but I doubt it. Given their recent team-up with Sony (motto: Do naught but evil), I'm thinking Google's motto has changed from "do no evil" to "Evil: It's what's for dinner"...
The quote I was responding too suggested the event was so unlikely that it makes our current model suspect.
However, if there are 100,000 different things that are likely to be observed in 1 planet in a million, that, if observed significantly more frequently, would damage the model, then we can expect to observe one of these things in about 1 planet in 10.
Suddenly, observing one in the first 10 planets doesn't seem like such a model killer.
I'm not saying that they shouldn't study/analyze it and try to find flaws, I'm just saying it isn't necessarily going to break the theories because it's unlikely. It seemed to me a couple comments simply jumped the gun.
True, but the other question, the one not often asked, how many similarly unlikely occurrences could we see, that we haven't? It may be likely that we see one similarly unlikely event every few dozen planets.
That wouldn't fit with the massive loss seen by TFS. Anecdotal, yes, but my old notebook ran ~3 hours on Windows or FreeBSD (sorry, don't know about Linux), using defaults for windows, and BSD compiled without extra drivers. I would expect FreeBSD to have a similar loss to Linux in that case (journaled file system). Also, the shared partition that both Windows and FreeBSD accessed was EXT3.
Where I used to work (~5 years ago), we used an erasure tool that wrote random data over the entire drive (10 times), then introduced the drive to "Mr. Band Saw" in the machine shop, to quarter the platters, on any DoD/DoE stuff
With $1000 enthusiast CPUs, the price isn't horrible by comparison.
Still, you can get Intel CPUs that'll run at similar clock speeds for similar prices (except use more electricity), and right now, Intel has the performance/clock ratio advantage over AMD.
So I wouldn't call it/expensive/ in the grand scheme of things, it's just not that impressive either.
What do you think their vacations to southeast Asia are for?
yep, and this was also stated.
I feel obnoxious quoting myself, but please put 2 and 2 together and get 4 instead of 14.
No, that is the definition of cancer, not the cause. Cause != symptom. Example: a large portion of cancers, are in part, caused by a disabled p53 gene.
Unfortunately, a cure that non-specific also targets normal stem cells, and the treatment actually curing cancer vs. killing the patient becomes a dice game that works on small cancers.
Now, what CAUSES the cells to go haywire is a good thing to target.
No, everyone has cells that have the potential to become cancerous, and most people develop cancer cells at some point during their lives. It's a small difference, but you seem to want to be really nitpicky here...
Although, reading the other comments, my description is obviously the one least likely to be near-term useful and relevant (especially given the fact that turning off this gene doesn't eliminate other cells).
That's how genetics works.
You find out what creates a something by turning it off.
For example, they E4bp4 gene is needed to make NK cells from blood stem cells. They now know that one of the steps in generating NK cells from the listed stem cells involves the protein E4bp4 gene. Using information about this and other relevant proteins (both that they have found, and that they haven't found, once they are found), they will be able to devise procedures for converting these stem cells (possibly from the original patient, eliminating or reducing rejection issues) to NK cells.
The problem with "a cure for cancer", is that cancer isn't one disease. Also there are many causes.
That being said, reliable treatments (cures) for different types of cancers can still be developed. However, no cure for cancer could ever prevent a relapse, unless it treated the genetic factors involved, and was taken regularly through a person's life. Even then, only cancers derived from the cause that the treatment targets, will be prevented.
Another possibility (not saying yours is wrong, but this "correction", is probably another factor).
[..] It makes sense evolutionarily speaking. Boys grow to be men and need to be able to not be afraid (or at least keep that fear in check) while doing stupid but impressive things to show potential mates that they are strong. [...]
I've only had problems with sprint when I'm way out in desolate areas (mostly parts of the UP of Michigan), or in area where there's significant signal blockage (my basement, where nobody's phone works well). Aside from that, most of Ohio and adjacent states work just fine for the sprint phones I've had (and the people I've known using them). Sure it's anecdotal, but at this point, even that's more than what you've provided.
Odd, I don't use Linux, and the simple choice is still EXT2. Primarily I use Windows and FreeBSD.
The thing is, ext2 doesn't have the size limit of FAT32, it handles hard links properly, and it's available on pretty much any OS (well, any *BSD, Windows, Linux, and MacOS).
And before you say windows can't use EXT2, yes it can. That's the nicer driver, there are several that let you access EXT2 with an FTP like client. This one actually lets you mount the drive.
I just make sure Linux and FreeBSD have my account on the same UID, and Windows seems to default to superuser mode.
Hey, it's appropriate for both the comment and the sig, how could I pass it up?
Warum tun wir das?
OK, you typed that on slashdot. Please tell me you didn't have a straight face while doing so...
Completely OT (mods, have fun!!), but I was looking at your sig, and I was bothered about it for some reason... It took me a second to place it.
Who the hell can imagine the state even fractionally sacred without suffering an aneurysm?
I would hope so, but I doubt it. Given their recent team-up with Sony (motto: Do naught but evil), I'm thinking Google's motto has changed from "do no evil" to "Evil: It's what's for dinner"...
Not exactly.
The quote I was responding too suggested the event was so unlikely that it makes our current model suspect.
However, if there are 100,000 different things that are likely to be observed in 1 planet in a million, that, if observed significantly more frequently, would damage the model, then we can expect to observe one of these things in about 1 planet in 10.
Suddenly, observing one in the first 10 planets doesn't seem like such a model killer.
I'm not saying that they shouldn't study/analyze it and try to find flaws, I'm just saying it isn't necessarily going to break the theories because it's unlikely. It seemed to me a couple comments simply jumped the gun.
shouldn't "hot" be replaced with "heavy", and "cold" be replaced with "light"?
True, but the other question, the one not often asked, how many similarly unlikely occurrences could we see, that we haven't? It may be likely that we see one similarly unlikely event every few dozen planets.
Lamest "fixed that for you" joke ever. That, and you didn't even do it right.
*applaud*
Congratulations on your brand new EPIC FAIL.
That wouldn't fit with the massive loss seen by TFS. Anecdotal, yes, but my old notebook ran ~3 hours on Windows or FreeBSD (sorry, don't know about Linux), using defaults for windows, and BSD compiled without extra drivers. I would expect FreeBSD to have a similar loss to Linux in that case (journaled file system). Also, the shared partition that both Windows and FreeBSD accessed was EXT3.
Maybe they can't shut it down, but it is hillarous that someone pirated The Pirate Bay.
Maybe he's using one of those hackable Mac keyboard with all the spare storage and processing?
Only after Satan takes notes and makes his upgrades. Prior to that, a living hell will be an improvment.
Where I used to work (~5 years ago), we used an erasure tool that wrote random data over the entire drive (10 times), then introduced the drive to "Mr. Band Saw" in the machine shop, to quarter the platters, on any DoD/DoE stuff
$200-$400 seems to be Intels "mid range", so they are probably comparing it to that.
With $1000 enthusiast CPUs, the price isn't horrible by comparison.
Still, you can get Intel CPUs that'll run at similar clock speeds for similar prices (except use more electricity), and right now, Intel has the performance/clock ratio advantage over AMD.
So I wouldn't call it /expensive/ in the grand scheme of things, it's just not that impressive either.