Oh, yes, it happens. Not frequently, but look at how Agrobacterium tumefaciens originally got the properties that makes it great a great tool for GM. There are genes with a clear plant origin inside that bacterium, and as it can infect different species, it can transfer material between them as well.
There are also traces of an animal myoglobin/hemoglobin-related protein in some plant species. The sequences are so alike that the most logical explanation is that it's been transferred long after the original split in our heritage (which would be 1 billion years ago). Horizontal gene transfer isn't frequent. But even if a new gene only enters the gene pool of a species every 1000th generation, or once every million years, or anything, that would mean that just about every species on earth is the result of horizontal gene transfer. If horizontal gene transfer would create a great risk for ecosystem devastation, we should be able to track those cases down, as they should have already happened now, many times over.
And what about Netscape plugins? This is not "download ActiveX controls on demand" which was chastised and basically isn't around anymore. This is the fact that some apps on your machine say "hey, I know how to handle some data on the net, just load this dynamic library of mine and hand it the data, and I'll render it neatly in the browser".
Do you read the PDF in Adobe Reader to compare them? Acrobat does its own anti-aliasing (which I find inferior to the Windows one, even though it can get a lot better if you adjust the settings). However, I'm a bit reluctant to the new fonts as well, I just want to point out one thing I think is quite relevant when evaluating them.
Yes, but a modern OS doesn't use that crap. It uses some space in the flash ROM, possibly mapped into some RAM, but no call should ever use it. Just about everything should be done by drivers, so the only thing affected is the first few seconds of the boot. Those are not irrelevant, but it doesn't define the performance of the whole OS.
In order to move an object from point A to point B, both placed on equal height, you need no energy at all (or, well, you need to borrow some, but you can pay most of it back when you're done). Evacuated tunnels are maybe not a realistic option, but this shows that aerodynamics and surface contact is everything. And then we haven't even started discussing the actual engine.
7200 RPM gives you a hard wall. Faster rotation is a pain, and arm movement is not (generally) the limiting factor. The only thing I can imagine is putting two heads there, right opposite each other. That creates a nice scheduling problem, but I guess it would be doable. You wouldn't only get RAID 0, because, with two heads free, you could actually cut the time before the right sector is under either head in half. One thing that comes to mind is whether a construction with two arms would be much more (i.e. more than twice as) susceptible to a head crash; if a disc currently actually sometimes tilts ever so slightly, and wouldn't be able to do so with a two-arm arrangement. But, again, that's just wild speculation.
It only appears to affect full copying with GUI. xcopy, that actually uses quite a bit of the underlying API, seems not to be affected. Although it IS possible to script jobs through COM objects and the shell, I don't think any sanely configured server will have it done that way.
A key fallacy of your argument is that it would be hard to prove that most kinds of intellectual property creates an information asymmetry in the economical sense. A very real asymmetry is created by the fact that you might avoid certain transactions (or creating certain products) just due to the fear of what patents migth already exist, but the presence of a patent in itself is not creating an asymmetry of that kind.
The fact that intellectual property is based on ownership of "information", in some form, doesn't mean that it's an important ground for information asymmetry. In many cases, it can be quite the opposite. If you know a reliable and acceptable mean to eliminate the asymmetry, even if it means paying, you reduce the consequences vs. the case where the information would be hoarded and hidden more secretively.
Nah, I'm not so sure. At least put some work in the docs. A guide to the design/architecture and some simple howtos to use the system. If those are missing, people might never even realize whether there is anything to gain from cleaning up the code. Asymptotically, all worthwhile projects will be found and improved upon, but we do not have infinite time, nor an infinite number of monkey^H^H^H^H^H^Hcontributors.
Yeah, rewrite the ending of the season 3 final (it is the final, isn't it?) so the mind-body switch failed, and Kirk retained his command in the new body. Fantastic!
Oh, no, they realized. It was meant to be two different versions, but Shatner fooled on purpose in the "non-finished kiss" one, so only the one with the kiss remained. (And, BTW, it was a forced kiss.)
ATI has also stated that some features won't be implementable, exactly due to patent issues, by just following those specs. That's one of the reasons for why they release specs and redo the driver in an "external cleanroom", rather than releasing an open-source driver themselves. (Yeah, cleanroom applies to reverse engineering and copyright, but it would be a good practice to protect the company in a patent suit as well.)
Also, for check numbers, as well as facial features, we expect a quite specific structure. This means that the set of possible original images is not uniform, so it's quite possible to detect a remarkable level of detail (like the specific check number, if the font is well-defined), even when a lot of information has been lost.
Well, I wonder why it's not a Vista issue. Is it because you get a UAC prompt before opening the stuff, or something else? (Yeah, I'm being ignorant right now.) The main point is that it's possible to register URI handlers in many ways. IF you choose to do it on the command line, you need to be extremely careful. As the GP said, there is no way to tell that the URL is really invalid. What could be done would be to specify an escpaing scheme to be used, but that's "only" a design error, not a bug, and anyone implementing an URI handler should consider and test how escaping is(n't) handled, to implement the unescaping properly on the receiving end (AND to consider security implications).
Slashdot Mirror
And 0.01 % thinks that he is sexier than open software on open hardware... leaving none to agree with him!
It is a Voyager episode, the doctor is cardassian and it's B'Elanna being treated. Not all Voyager episodes were bad...
There are also traces of an animal myoglobin/hemoglobin-related protein in some plant species. The sequences are so alike that the most logical explanation is that it's been transferred long after the original split in our heritage (which would be 1 billion years ago). Horizontal gene transfer isn't frequent. But even if a new gene only enters the gene pool of a species every 1000th generation, or once every million years, or anything, that would mean that just about every species on earth is the result of horizontal gene transfer. If horizontal gene transfer would create a great risk for ecosystem devastation, we should be able to track those cases down, as they should have already happened now, many times over.
Genesis was no failure. Dr. Marcus was indeed very proud over it.
And what about Netscape plugins? This is not "download ActiveX controls on demand" which was chastised and basically isn't around anymore. This is the fact that some apps on your machine say "hey, I know how to handle some data on the net, just load this dynamic library of mine and hand it the data, and I'll render it neatly in the browser".
No, he asked for memory usage. You just gave the numbers for the code pages in RAM.
Why do you use anti-alias in Fedora, but not XP?
Do you read the PDF in Adobe Reader to compare them? Acrobat does its own anti-aliasing (which I find inferior to the Windows one, even though it can get a lot better if you adjust the settings). However, I'm a bit reluctant to the new fonts as well, I just want to point out one thing I think is quite relevant when evaluating them.
Yeah, because the code size is the most relevant metric, right?
Yes, but a modern OS doesn't use that crap. It uses some space in the flash ROM, possibly mapped into some RAM, but no call should ever use it. Just about everything should be done by drivers, so the only thing affected is the first few seconds of the boot. Those are not irrelevant, but it doesn't define the performance of the whole OS.
Several data areas: DS, GS, FS(, SS)
x86, yummy!
You don't need to restore the complete shadow copy to get access to it. The interface in XP really sucks, but the actual support is there.
In order to move an object from point A to point B, both placed on equal height, you need no energy at all (or, well, you need to borrow some, but you can pay most of it back when you're done). Evacuated tunnels are maybe not a realistic option, but this shows that aerodynamics and surface contact is everything. And then we haven't even started discussing the actual engine.
7200 RPM gives you a hard wall. Faster rotation is a pain, and arm movement is not (generally) the limiting factor. The only thing I can imagine is putting two heads there, right opposite each other. That creates a nice scheduling problem, but I guess it would be doable. You wouldn't only get RAID 0, because, with two heads free, you could actually cut the time before the right sector is under either head in half. One thing that comes to mind is whether a construction with two arms would be much more (i.e. more than twice as) susceptible to a head crash; if a disc currently actually sometimes tilts ever so slightly, and wouldn't be able to do so with a two-arm arrangement. But, again, that's just wild speculation.
It only appears to affect full copying with GUI. xcopy, that actually uses quite a bit of the underlying API, seems not to be affected. Although it IS possible to script jobs through COM objects and the shell, I don't think any sanely configured server will have it done that way.
The fact that intellectual property is based on ownership of "information", in some form, doesn't mean that it's an important ground for information asymmetry. In many cases, it can be quite the opposite. If you know a reliable and acceptable mean to eliminate the asymmetry, even if it means paying, you reduce the consequences vs. the case where the information would be hoarded and hidden more secretively.
Nonono, the Enceladusans!
Nah, I'm not so sure. At least put some work in the docs. A guide to the design/architecture and some simple howtos to use the system. If those are missing, people might never even realize whether there is anything to gain from cleaning up the code. Asymptotically, all worthwhile projects will be found and improved upon, but we do not have infinite time, nor an infinite number of monkey^H^H^H^H^H^Hcontributors.
Yeah, rewrite the ending of the season 3 final (it is the final, isn't it?) so the mind-body switch failed, and Kirk retained his command in the new body. Fantastic!
Yeah, all (reasonably) current scifi is a real piece of gosa.
Oh, no, they realized. It was meant to be two different versions, but Shatner fooled on purpose in the "non-finished kiss" one, so only the one with the kiss remained. (And, BTW, it was a forced kiss.)
Google also seems to have a real policy of not keeping external productified versions of technology they want for their internal use.
ATI has also stated that some features won't be implementable, exactly due to patent issues, by just following those specs. That's one of the reasons for why they release specs and redo the driver in an "external cleanroom", rather than releasing an open-source driver themselves. (Yeah, cleanroom applies to reverse engineering and copyright, but it would be a good practice to protect the company in a patent suit as well.)
Also, for check numbers, as well as facial features, we expect a quite specific structure. This means that the set of possible original images is not uniform, so it's quite possible to detect a remarkable level of detail (like the specific check number, if the font is well-defined), even when a lot of information has been lost.
Well, I wonder why it's not a Vista issue. Is it because you get a UAC prompt before opening the stuff, or something else? (Yeah, I'm being ignorant right now.) The main point is that it's possible to register URI handlers in many ways. IF you choose to do it on the command line, you need to be extremely careful. As the GP said, there is no way to tell that the URL is really invalid. What could be done would be to specify an escpaing scheme to be used, but that's "only" a design error, not a bug, and anyone implementing an URI handler should consider and test how escaping is(n't) handled, to implement the unescaping properly on the receiving end (AND to consider security implications).