I am a CAD draftsman and an NC programmer, jacknut.
I presume that a serious colonization effort will require engineers and fabrication programmers, no? Shit breaks, and you gotta make new parts. Not to mention designing and building new habitat structures.
It seems reasonable to believe that a COLONY expedition could use such a person.
It doesn't need to actually make really large bubbles. It just needs to cavitate the heavier rust particles suspended in the oil, creating little pockets of pure oil that move around the threads of the bolt. We don't need to volatize the oil.
Think more "ultrasonic cleaner", and less "ultrasonic heater."
We just want small cavities of the more motile oil to form behind flakes of rust between the bolt and the bolt hole. Not actual evacuated bubbles.
The device I have in mind has 3 or more transducers, offset a fraction of a wavelength. (Not a whole wavelength fraction.) The transducers need to be slightly angled, so that the standing waves are not formed at the exact center of the cavity, but instead slightly offcenter.
For breaking rust, I actually envisioned a digitally tuned frequency, that adjusts the tone to that of the bolt by looking for polyphonic abberations. (Use a peizo crystal to measure the feedback.) The idea is to increase the amount of polyphonic waveforms generated by the bolt, such that it essentially "hoolahoops" on a very tiny scale.
We want energy to be conducted away from the bolt, and into the rust+oil medium, so that cavitation occurs in that medium. We want the bolt hole to serve as a sink for the energy kicked up in the bolt, to avoid damaging the bolt. The hole will have a different resonant frequency than the bolt, so the tuned source signal will only cause heating in the material the hole is drilled in.
Due to the tiny distances involved between the bolt and the hole, we want to use a very high frequency signal, so the bolt will be at an Nth order harmonic, and not a first order one. The potential to cause microfractures across metal grain boundries inside the bolt is a noteworthy concern, and is why we want to dampen the resonation.
I was referring to the optical tweezers cited by the summary. Those would have wavelengths in the nanometer range, which should allow you to move largish molecules around.
The question was if you would need some other form of support to hold the substrate you were building up with the tweezed building blocks, or if you could use another tweezer to hold the chain.
Remember, individual atoms can be trapped in a bessel beam laser.
How nice of you to assume I don't know what I am talking about! And to be so conceited about it too!/snark
Really, it makes perfect sense as written. The bolt and the threaded hole it is inserted/rusted into will have different resonant frequencies. The interface (rust) between the bolt and the hole has a lower deformation capacity, and is much more brittle than either of the other bodies.
The screwdriver produces what is essentially a standing wave that "crawls" in a circle inside the waveguide cup, which is placed over the top of the bolt head. In addition to interaction with this standing wave, it will also be subjected to the interfereing part of the wave. This will cause the shaft to resonate. We want the phonons induced inside the bolt and in the hole to have a reliable medium over which to interact. The penetrating oil will work nicely.
The cavitations created in this interface will shatter the rust, by inducing pressure beyond the rust's structural tolerances.
The bolt won't turn very fast, if at all (very rusted, with lots of resistance), but it would break up the rust quite nicely, in exactly the same way a tissue homogenizer blends up tissue samples.
Agreed. Ideally, the RDP server would be in an "untrusted" network segment, with write permissions ONLY to that untrusted remote user account, on a seperate physical volume and server from normal corporate data storage.
Hardware keylogger could be frustrated by using a pocketed keyring. That way the attacker only gets the keyring password, and not the enterprise password. Keyring needs to be on an encrypted volume, that is always physically on your person at all times. (Literally on your keychain, or in your wallet.)
The idea is compartmentalization, and barriers to entry. Your traveling businessman needs to be aware that he won't have access to all of his data, only to his email (dangerous enough as is), and a crippled remote user account on an "unloved" server set aside exclusively for that purpose.
The remote enterprise account would have your typical office suites he needs to build powerpoint presentations, make excel spreadsheets, send and receive emails, and any special purpose enterprise aps he may need access to on a case by case basis. Otherwise it is barren wasteland. Control access to data by requiring him to request files be placed into the user's private share as needed by IT on a request only basis.
When the business trip is over, policy should dictate that the remote access server be restored from an image backup, and the password changed. A virtual server would be ideal here.
Granted, the businessman will *HATE* it, and chafe miserably under the restrictions, but angry businessmen are better than the consequences of a compromised security situation.
The RDP equipped live DVD option presumes a sanely set up enterprise backend to connect to. The backend should be presumed untrustworthy, and segregated accordingly.
The "sonic screwdriver" would work best with a penetrating oil like liquid wrench anyway. The oil would improve phonon conduction in the bolt.
It would basically be the same as gently tapping the head of the rusted bolt with a hammer after being sprayed, only more controlled, and with additional resonant effects in play.
Too strong of a transducer might fatigue the metal of the bolt though. Try to avoid the ones that can "homogenize" tissue samples, and you should be fine.:D
QEMM and EMM386.EXE both gobble down a considerable amount of conventional memory to house their EMM interupt vector routine TSR, even when you don't even NEED EMS pageframes.
If all you need is for the HMA and UMBs to be available, you can HIRAM.SYS instead. It uses only 1k of conventional memory, and can even be loaded outside conventional if needed. Personally, I prefer to use UMBPCI to enable hardware UMBs on old school pentium systems for retro gaming, and to manually configure an EMS pageframe with JEMMX, which also replaces himem.sys, and superceeds hiram.sys.
Using SHUCDX, CTMOUSE, and JEMMX will usually net you a dos machine with over 600kb free conventional. Usually in the 620kb range, unless your chipset/bios is really bitchy about the adaptor rom region.
Always manually assign the location of the EMS pageframe. Exactly where to put it is black magic voodoo that is specifc to the system being tweaked. Remember that it gobbles up a whole 64kb of the adaptor rom region! Only use EMS if you REALLY need it.
Essentially, when the electron of the absorbing substance absorbs a photon, its speed and energy increase, slightly altering the rest energy of the atom in question. When the photon is re-emitted, the state drops back down. When that happens, there is a change in kinetic movement of the atom.
All atoms are constantly moving in random patterns. Sustained exposure to a radiation source provides a sustained and consistent influence on that motion, wich results in a small, but cumulative change in the group's vector of motion.
See for instance, a radiometer. Differences in absorption/emission of photons creates a pressure differential from the re-emission. The black sides of the square tags of the radiometer's armature emit lower energy photons than they absorb. Where does the energy go? Heat! Aka, random atomic motion.
Given the "fuzzy" nature of massive particles at the quantum scale, and their "actually" being little more than a probabalistic distribution of an energy potential, I agree.
The best explanation I could give for a "physical" device is one that makes use of electrical charge repulsion forces to interact with another massive particle. (Eg, what keeps your hand from going right through the door when you knock on it.)
Photons are not massive particles, and imbue kinetic forces through a completely different mechanism.
I'm afraid you are about 25 years too late to that party, unless you are running a vintage DOS machine.
If however, you indeed are running a vintage dos machine for old retro dos games (because dosbox doesn't feel right), then there are much better FOSS memory managers from the freedos project you can use instead of that incompatability inducing horror QEMM.:)
How large/complex of a particle can they manipulate using this technology, and how fast can they move particles without risking them falling out of the "tweesers"?
I imagine the applications as a synthesis system for synthentic long chain DNA, or synthetically generated amino acid chains, to better test protein folding under laboratory conditions.
Synthetic DNA chain synthesis especially is a very intriguing potential application here. The tweeser needs to be able to hold up a fair amount of mass though to be useful for that though.
I mean, a simple tone generator, and some variable impedence circuits attached to some high power tansducers with a waveguide cup, and you are there.
All you have to do, is ensure that the tones emitted by the transducers are offset a small fraction of a wavelength of the tone frequency, such that a reinforcement peak forms and "rolls" around the inside of the cavity. Basically an ultrasonic motor, but with just the stators.
Would also work wonders for busting up rust on a rusty bolt.
Then their little good-ol-boys club should be shuttered in place of an organization with some fucking public oversight, that CAN be policed against this bullshit!
A room of wrinkled old penises whacking off to violating the public trust should never be accepted. Ever!
They *clearly* know that these measures are against the public interest, and are only desirable for reasons that are directly counter to a free and legitimate government; that the voting publics that they represent would never willingly agree to this kind of "microscope colonoscopy" type surveylence if they knew what it really meant.
That's why the fuckers do closed room and secret fucking "negotiations" to plan, orchestrate, and implemet bullshit like this.
About the only way to combat this is to make closed room negotiations so undesirable from a political career standpoint that the slimeballs treat like radioactive waste.
Something like immediate no-confidence being enacted for mere participation or something, and blacklisting from ever running for public office ever again.
Of course, such strong measures would never make it passed the slimeballs to begin with.
There are several ways around this, with increasing levels of overhead.
0) don't bring the laptop to begin with. (Hehe.. har.. yeah, who am I kidding?)
1) yank the HDD completely, boot the laptop using a custom knoppix DVD, with an RDP client. Save your work in the cloud/at the enterprise, behind a strong enterprise password. Malware magically vanishes when the laptop powers down. No local data to collect.
2) use something like black ice defender.
3) use whole disk encryption with almost reigious zeal.
Personally, I prefer the live dvd approach. It has fringe benefts of always being a fresh, clean environment, and a complete black hole for forensic data recovery. Only the rubber hose method to get you to reveal the RDP account password remains as a reliable method of intrusion, though this assumes you aren't an idiot, and weren't so stupid as to package a keyring on the live DVD. (The whole idea is to keep sensitive data OFF the system!) If you absolutey NEED a keyring, find some way to use an actual usb keyfob to store it, and always carry your keys.
Regardless of the method used, remember that allowing unauthorized persons access to the physical system is practically synonymous with being pwned. The live dvd method only gives them physical access to a terminal.
No, they should obey the terms of the warrant, and the 4th amendment.
You know, that niggle little screed the founding fathers sharted out that says the police have to have a specific list of things they are to take when exercising a warrant, and that everything else is private property and hands-off?
So, basically they are saying something like this:
"But you want us to stop those dirty, nasty people that want to sell your little angel a bag of crack, and who want nothing more than to destroy our way of life, right? Well, in order to do that any better than we alread are, because those people are adapting to the changing flow of technology, we will have to have access to those mediums!"
We should reply in kind:
"Text messages should be intercepted live, and not recorded in advance. Your convenience is not worth our privacy. Get a warrant for a wire tap, monitor the transmissions of your suspect, and either arrest or not arrest based on the messages you collect duing the surveylence window. We will *not* write you a blank cheque."
Of course, that isn't how this will pan out. My cynical nature screams at me that the police will kick their feet, balk, whine, and throw a PR hissyfit with the press about those mean, dirty people with their dirty secrets wanting to hurt innocent people and children in order to protect themselves from justice, by supressing the motion.
The whole "only those with something to hide" rhetoric.
Nevermind the famous cardinal richelou quote: "give me 5 written lines from the most pious man alive, and I will find something to hang him." (Paraphrased)
We don't demand security and privacy from the police because we are crooked ourselves, or to protect crooked people. We do it to protect the innocent from those in power, who are above the law. (Like said cardinal was.)
As long as there is a "thin blue line", they can never have what they are asking for.
Not necessarily. Some processes require sequential execution, as the input for the next function is the result of the previous. The two cannot execute in parallel, unless the people at microsoft have invented the ansible.
For other things that don't require sequential execution, multithreading just makes sense given the current trend in computing hardware. Eg, if you want to both divide and square root a number, and return both results, there is no reason that both sets of computations could not fire simultaneously, since they share a single common input, and don't change each other's data. (Or two seperate database queries, or conditional checks, etc.)
The issue here is that continuing execution past the paralleled operation requires both threads to complete.
Race conditions galore can occur with improperly structured parallel execution. Many programmers have gotten comfortable with the intrinsic inability to produce that kind of race condition within their porgrams using sequential execution. Old habbits die hard.
What this compiler does is parse the sourcecode for a sequential execution program, identify blocks of code that can execute in parallel, insert conditional checks to ensure all parallel blocks execute before returning, and restructure the compiled code approprately.
Because execution prediction is tricky, and because programmers use nasty behavior exploits in some of their programs, this compiler could blow up spectacularly in certain circumstances when trying to multithread a single thread program. (Programmer makes use of a hardware quirk in how a processor handes cached results, for instance. Code executes on a different core than intended, cache behavior is not conserved, shit hits the fan.)
As long as the compiler has metacomment flags you can put in to tell it to not attempt paralellism on certain blocks, it should be quite useful. But if it just blindly tries to mangle code, its gonna make a lot of programmers very angry.
However, one probe's sampling is insufficient to build a general soil minerology statistic from.
Imagine, aliens send a probe to a mountain on earth and discover gold nuggets. Would it be sensible for the aliens to conclude that the earth has a high soil concentration of gold? Clearly not.
Likewise, nasa scientists thought the perchlorate discovery was a very unusual anomaly.
Discovering yet more perchlorate several hundred kilometers away in a different region makes the case that the perchlorates could be a widespread feature in the surface regolith.
Your argument is immaterial. Chemists don't call it that, because polyatomic ion is more precise, and not all polyatomic ions are compounds.
The terms are not interchangable, but many are a subset of the other.
If we play a substitution game to test the logic, it makes sense.
You say: "perchlorate ion is not a compound. It is a polyatomic ion."
I respond with this substtution:
"A rabbit is not an animal. It is a mammal."
There are animals that are not mammals, but a rabbit is both an animal, and a mammal.
In the same way, perchlorate is both a polyatomic ion, and a compound.
Scientists use precise language, whenever possible. The amusing diversion that they don't use the general descriptor when dealing with a specific type of molecule does not add weight to your argument.
I will say again. The burden of proof is yours, to prove that it ISN'T a compound.
Slashdot Mirror
Excel spreadsheets!? (Riotous laughter)
I am a CAD draftsman and an NC programmer, jacknut.
I presume that a serious colonization effort will require engineers and fabrication programmers, no? Shit breaks, and you gotta make new parts. Not to mention designing and building new habitat structures.
It seems reasonable to believe that a COLONY expedition could use such a person.
It doesn't need to actually make really large bubbles. It just needs to cavitate the heavier rust particles suspended in the oil, creating little pockets of pure oil that move around the threads of the bolt. We don't need to volatize the oil.
Think more "ultrasonic cleaner", and less "ultrasonic heater."
We just want small cavities of the more motile oil to form behind flakes of rust between the bolt and the bolt hole. Not actual evacuated bubbles.
The device I have in mind has 3 or more transducers, offset a fraction of a wavelength. (Not a whole wavelength fraction.) The transducers need to be slightly angled, so that the standing waves are not formed at the exact center of the cavity, but instead slightly offcenter.
For breaking rust, I actually envisioned a digitally tuned frequency, that adjusts the tone to that of the bolt by looking for polyphonic abberations. (Use a peizo crystal to measure the feedback.) The idea is to increase the amount of polyphonic waveforms generated by the bolt, such that it essentially "hoolahoops" on a very tiny scale.
We want energy to be conducted away from the bolt, and into the rust+oil medium, so that cavitation occurs in that medium. We want the bolt hole to serve as a sink for the energy kicked up in the bolt, to avoid damaging the bolt. The hole will have a different resonant frequency than the bolt, so the tuned source signal will only cause heating in the material the hole is drilled in.
Due to the tiny distances involved between the bolt and the hole, we want to use a very high frequency signal, so the bolt will be at an Nth order harmonic, and not a first order one. The potential to cause microfractures across metal grain boundries inside the bolt is a noteworthy concern, and is why we want to dampen the resonation.
I was referring to the optical tweezers cited by the summary. Those would have wavelengths in the nanometer range, which should allow you to move largish molecules around.
The question was if you would need some other form of support to hold the substrate you were building up with the tweezed building blocks, or if you could use another tweezer to hold the chain.
Remember, individual atoms can be trapped in a bessel beam laser.
DNA nucleotide sequences are considerably larger.
But a manual tool isn't as cool, and won't rattle a doorknob apart! :D
How nice of you to assume I don't know what I am talking about! And to be so conceited about it too! /snark
Really, it makes perfect sense as written. The bolt and the threaded hole it is inserted/rusted into will have different resonant frequencies. The interface (rust) between the bolt and the hole has a lower deformation capacity, and is much more brittle than either of the other bodies.
The screwdriver produces what is essentially a standing wave that "crawls" in a circle inside the waveguide cup, which is placed over the top of the bolt head. In addition to interaction with this standing wave, it will also be subjected to the interfereing part of the wave. This will cause the shaft to resonate. We want the phonons induced inside the bolt and in the hole to have a reliable medium over which to interact. The penetrating oil will work nicely.
The cavitations created in this interface will shatter the rust, by inducing pressure beyond the rust's structural tolerances.
The bolt won't turn very fast, if at all (very rusted, with lots of resistance), but it would break up the rust quite nicely, in exactly the same way a tissue homogenizer blends up tissue samples.
Agreed. Ideally, the RDP server would be in an "untrusted" network segment, with write permissions ONLY to that untrusted remote user account, on a seperate physical volume and server from normal corporate data storage.
Hardware keylogger could be frustrated by using a pocketed keyring. That way the attacker only gets the keyring password, and not the enterprise password. Keyring needs to be on an encrypted volume, that is always physically on your person at all times. (Literally on your keychain, or in your wallet.)
The idea is compartmentalization, and barriers to entry. Your traveling businessman needs to be aware that he won't have access to all of his data, only to his email (dangerous enough as is), and a crippled remote user account on an "unloved" server set aside exclusively for that purpose.
The remote enterprise account would have your typical office suites he needs to build powerpoint presentations, make excel spreadsheets, send and receive emails, and any special purpose enterprise aps he may need access to on a case by case basis. Otherwise it is barren wasteland. Control access to data by requiring him to request files be placed into the user's private share as needed by IT on a request only basis.
When the business trip is over, policy should dictate that the remote access server be restored from an image backup, and the password changed. A virtual server would be ideal here.
Granted, the businessman will *HATE* it, and chafe miserably under the restrictions, but angry businessmen are better than the consequences of a compromised security situation.
The RDP equipped live DVD option presumes a sanely set up enterprise backend to connect to. The backend should be presumed untrustworthy, and segregated accordingly.
The "sonic screwdriver" would work best with a penetrating oil like liquid wrench anyway. The oil would improve phonon conduction in the bolt.
It would basically be the same as gently tapping the head of the rusted bolt with a hammer after being sprayed, only more controlled, and with additional resonant effects in play.
Too strong of a transducer might fatigue the metal of the bolt though. Try to avoid the ones that can "homogenize" tissue samples, and you should be fine. :D
Well, you are welcome to fact check if you like.
QEMM and EMM386.EXE both gobble down a considerable amount of conventional memory to house their EMM interupt vector routine TSR, even when you don't even NEED EMS pageframes.
If all you need is for the HMA and UMBs to be available, you can HIRAM.SYS instead. It uses only 1k of conventional memory, and can even be loaded outside conventional if needed. Personally, I prefer to use UMBPCI to enable hardware UMBs on old school pentium systems for retro gaming, and to manually configure an EMS pageframe with JEMMX, which also replaces himem.sys, and superceeds hiram.sys.
Using SHUCDX, CTMOUSE, and JEMMX will usually net you a dos machine with over 600kb free conventional. Usually in the 620kb range, unless your chipset/bios is really bitchy about the adaptor rom region.
Always manually assign the location of the EMS pageframe. Exactly where to put it is black magic voodoo that is specifc to the system being tweaked. Remember that it gobbles up a whole 64kb of the adaptor rom region! Only use EMS if you REALLY need it.
No silly. The Master uses a "laser screwdriver".
2 guesses who's working for these guys. ;)
(Lol!)
Radiation pressure.
Essentially, when the electron of the absorbing substance absorbs a photon, its speed and energy increase, slightly altering the rest energy of the atom in question. When the photon is re-emitted, the state drops back down. When that happens, there is a change in kinetic movement of the atom.
All atoms are constantly moving in random patterns. Sustained exposure to a radiation source provides a sustained and consistent influence on that motion, wich results in a small, but cumulative change in the group's vector of motion.
See for instance, a radiometer. Differences in absorption/emission of photons creates a pressure differential from the re-emission. The black sides of the square tags of the radiometer's armature emit lower energy photons than they absorb. Where does the energy go? Heat! Aka, random atomic motion.
Given the "fuzzy" nature of massive particles at the quantum scale, and their "actually" being little more than a probabalistic distribution of an energy potential, I agree.
The best explanation I could give for a "physical" device is one that makes use of electrical charge repulsion forces to interact with another massive particle. (Eg, what keeps your hand from going right through the door when you knock on it.)
Photons are not massive particles, and imbue kinetic forces through a completely different mechanism.
I'm afraid you are about 25 years too late to that party, unless you are running a vintage DOS machine.
If however, you indeed are running a vintage dos machine for old retro dos games (because dosbox doesn't feel right), then there are much better FOSS memory managers from the freedos project you can use instead of that incompatability inducing horror QEMM. :)
Just sayin.
How large/complex of a particle can they manipulate using this technology, and how fast can they move particles without risking them falling out of the "tweesers"?
I imagine the applications as a synthesis system for synthentic long chain DNA, or synthetically generated amino acid chains, to better test protein folding under laboratory conditions.
Synthetic DNA chain synthesis especially is a very intriguing potential application here. The tweeser needs to be able to hold up a fair amount of mass though to be useful for that though.
Hmm.. so, a "monkey wrench", in british parlance, would be an enormous adjustable spanner?
Would a really large pipe wrench qualify?
You could probably make one if you really wanted.
I mean, a simple tone generator, and some variable impedence circuits attached to some high power tansducers with a waveguide cup, and you are there.
All you have to do, is ensure that the tones emitted by the transducers are offset a small fraction of a wavelength of the tone frequency, such that a reinforcement peak forms and "rolls" around the inside of the cavity. Basically an ultrasonic motor, but with just the stators.
Would also work wonders for busting up rust on a rusty bolt.
Then their little good-ol-boys club should be shuttered in place of an organization with some fucking public oversight, that CAN be policed against this bullshit!
A room of wrinkled old penises whacking off to violating the public trust should never be accepted. Ever!
Sorry for the flamebait here, but goddamn!
They *clearly* know that these measures are against the public interest, and are only desirable for reasons that are directly counter to a free and legitimate government; that the voting publics that they represent would never willingly agree to this kind of "microscope colonoscopy" type surveylence if they knew what it really meant.
That's why the fuckers do closed room and secret fucking "negotiations" to plan, orchestrate, and implemet bullshit like this.
About the only way to combat this is to make closed room negotiations so undesirable from a political career standpoint that the slimeballs treat like radioactive waste.
Something like immediate no-confidence being enacted for mere participation or something, and blacklisting from ever running for public office ever again.
Of course, such strong measures would never make it passed the slimeballs to begin with.
Fox fucking owns the henhouse.
There are several ways around this, with increasing levels of overhead.
0) don't bring the laptop to begin with. (Hehe.. har.. yeah, who am I kidding?)
1) yank the HDD completely, boot the laptop using a custom knoppix DVD, with an RDP client. Save your work in the cloud/at the enterprise, behind a strong enterprise password. Malware magically vanishes when the laptop powers down. No local data to collect.
2) use something like black ice defender.
3) use whole disk encryption with almost reigious zeal.
Personally, I prefer the live dvd approach. It has fringe benefts of always being a fresh, clean environment, and a complete black hole for forensic data recovery. Only the rubber hose method to get you to reveal the RDP account password remains as a reliable method of intrusion, though this assumes you aren't an idiot, and weren't so stupid as to package a keyring on the live DVD. (The whole idea is to keep sensitive data OFF the system!) If you absolutey NEED a keyring, find some way to use an actual usb keyfob to store it, and always carry your keys.
Regardless of the method used, remember that allowing unauthorized persons access to the physical system is practically synonymous with being pwned. The live dvd method only gives them physical access to a terminal.
No, they should obey the terms of the warrant, and the 4th amendment.
You know, that niggle little screed the founding fathers sharted out that says the police have to have a specific list of things they are to take when exercising a warrant, and that everything else is private property and hands-off?
Yeah. That one.
So, basically they are saying something like this:
"But you want us to stop those dirty, nasty people that want to sell your little angel a bag of crack, and who want nothing more than to destroy our way of life, right? Well, in order to do that any better than we alread are, because those people are adapting to the changing flow of technology, we will have to have access to those mediums!"
We should reply in kind:
"Text messages should be intercepted live, and not recorded in advance. Your convenience is not worth our privacy. Get a warrant for a wire tap, monitor the transmissions of your suspect, and either arrest or not arrest based on the messages you collect duing the surveylence window. We will *not* write you a blank cheque."
Of course, that isn't how this will pan out. My cynical nature screams at me that the police will kick their feet, balk, whine, and throw a PR hissyfit with the press about those mean, dirty people with their dirty secrets wanting to hurt innocent people and children in order to protect themselves from justice, by supressing the motion.
The whole "only those with something to hide" rhetoric.
Nevermind the famous cardinal richelou quote: "give me 5 written lines from the most pious man alive, and I will find something to hang him." (Paraphrased)
We don't demand security and privacy from the police because we are crooked ourselves, or to protect crooked people. We do it to protect the innocent from those in power, who are above the law. (Like said cardinal was.)
As long as there is a "thin blue line", they can never have what they are asking for.
Not necessarily. Some processes require sequential execution, as the input for the next function is the result of the previous. The two cannot execute in parallel, unless the people at microsoft have invented the ansible.
For other things that don't require sequential execution, multithreading just makes sense given the current trend in computing hardware. Eg, if you want to both divide and square root a number, and return both results, there is no reason that both sets of computations could not fire simultaneously, since they share a single common input, and don't change each other's data. (Or two seperate database queries, or conditional checks, etc.)
The issue here is that continuing execution past the paralleled operation requires both threads to complete.
Race conditions galore can occur with improperly structured parallel execution. Many programmers have gotten comfortable with the intrinsic inability to produce that kind of race condition within their porgrams using sequential execution. Old habbits die hard.
What this compiler does is parse the sourcecode for a sequential execution program, identify blocks of code that can execute in parallel, insert conditional checks to ensure all parallel blocks execute before returning, and restructure the compiled code approprately.
Because execution prediction is tricky, and because programmers use nasty behavior exploits in some of their programs, this compiler could blow up spectacularly in certain circumstances when trying to multithread a single thread program. (Programmer makes use of a hardware quirk in how a processor handes cached results, for instance. Code executes on a different core than intended, cache behavior is not conserved, shit hits the fan.)
As long as the compiler has metacomment flags you can put in to tell it to not attempt paralellism on certain blocks, it should be quite useful. But if it just blindly tries to mangle code, its gonna make a lot of programmers very angry.
However, one probe's sampling is insufficient to build a general soil minerology statistic from.
Imagine, aliens send a probe to a mountain on earth and discover gold nuggets. Would it be sensible for the aliens to conclude that the earth has a high soil concentration of gold? Clearly not.
Likewise, nasa scientists thought the perchlorate discovery was a very unusual anomaly.
Discovering yet more perchlorate several hundred kilometers away in a different region makes the case that the perchlorates could be a widespread feature in the surface regolith.
Blagh.. you are right!
That will teach me not to rant on the internet while doing NC programming!
Still, despite the naming faux pas, the argument still holds.
Your argument is immaterial. Chemists don't call it that, because polyatomic ion is more precise, and not all polyatomic ions are compounds.
The terms are not interchangable, but many are a subset of the other.
If we play a substitution game to test the logic, it makes sense.
You say: "perchlorate ion is not a compound. It is a polyatomic ion."
I respond with this substtution:
"A rabbit is not an animal. It is a mammal."
There are animals that are not mammals, but a rabbit is both an animal, and a mammal.
In the same way, perchlorate is both a polyatomic ion, and a compound.
Scientists use precise language, whenever possible. The amusing diversion that they don't use the general descriptor when dealing with a specific type of molecule does not add weight to your argument.
I will say again. The burden of proof is yours, to prove that it ISN'T a compound.
I'll be waiting.