Slashdot Mirror
Sniffing Out Cancer
Makarand writes "Researchers at the Univeristy of Rome are developing an
electronic nose that
can sniff out cancer by sampling people's breath. The instrument uses sensors
that respond to the presence of chemical compounds in the patient's breath.
For example, lung cancer patients exhale alkanes and benzene derivatives
which the electronic nose will try to detect. The sensors are quartz crystal
sensors coated with a substance that binds to a range of organic chemicals.
If certain molecules in the breath bind to this surface coating they change
the natural vibration frequency of the crystal."
One step closer to having Dr. Beverly Crusher become real.
smells like cat cancer.
--
Freeper Logic
Would YOU like to:
Trade segregation stories with Strom Thurmond ?
Share stalking tips with Marko?
Laugh at the preteen antics of Unterderbrucke?
Keep up to date with the latest Perl stylings of Sexual Asspussy?
Then come on down to Goatse Info. Where we're stretching the limits of crap flooding!
is here on the new Ebay Tech News.
That is one fine woman.
Are you bright? witty? Do you have friends that laugh at your jokes? We at lrse hosting" are looking for a select few individuals to join our ranks at the internet's premier source of wit and style.
Do YOU have what it takes? Register TODAY and FIND OUT!!!!
Yes, but can you sniff out the cancer in my ass?
Would YOU like to:
Trade segregation stories with Strom Thurmond ?
Share stalking tips with Marko?
Laugh at the preteen antics of Unterderbrucke?
Keep up to date with the latest Perl stylings of Sexual Asspussy?
Then come on down to Goatse Info. Where we're stretching the limits of crap flooding!
Me either.. I was really going for a +1 funny :).
[ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It'
sniffing is better than smoking, if you remember to remove the icecubes from the coke first