This is an AC/DC converter, of sorts. Add a high voltage capacitor between Vcc and ground on the DC side, and that's the flicker reduced... Of course, by doing that, you've instantly increased the bulk and cost of the mod.
Drill through the sides of the case to get to the wires without tripping the "don't authenticate me" switch. I've designed tamper-proof systems like this, and it would be extremely hard to get them to work against this sort of approach with your standard coil-and-cone speakers. When you get down to it, you could get by with a current clamp around the appropriate cable.
So why not save the document as a sequence of events since "blank document" state? That way, you could arrange to know the final state fairly easily, while being able to back the document state up to any stage in its development. As an added bonus, you could throw in the option to generate a "snapshot" file, with only the current state saved, and no backup information.
Although, now I actually look into it, it would appear that the DSU-15/B proximity fuse on the Sidewinder uses an IR laser for target ranging, although by the point you'd detect it, it's a little late to be worrying about that.
That does bring up an interesting point, though. Anyone happen to know how the laser proximity fuse stops itself from being fooled by, say, being painted with a random IR stream from the target designed to make the target appear much closer than it actually is?
And in order to take advantage of this, what does the average developer (who doesn't deal in assembly day-to-day) do? They use their funky new compiler. That was the conclusion that I came to after reading the fabled article, anyway...
My point is that, given that there just isn't going to be a radical change in architecture, making the x86 architecture more powerful will inevitably require added complexity because of the way it was initially designed and the complex way that it has grown.
Personally, I'd love to see the x86 arch die a long, slow, horrible death, somewhere a long way away from my development environment, but given the phenomenal market momentum, I just can't see that happening, so anything that can make the same source code more powerful has to be a good thing.
I'm not underestimating the development effort required by a change such as this. However, most of that effort will be expended by the chip designers working on the next revision anyway. This is a valid option for them to look at, given that they are going to be undergoing expensive and hard processes no matter what changes they make.
I also think you might be overestimating the difficulty of implementing this. True, it's a fundamental change to the way that the registers are accessed, but it's not a particularly complex one. It's a software-mediated lookup table into a generic register bank. Not that hard, relative to implementing, say, MMX or SSE.
The true "quick and easy" part comes when you look at the sum total of effort over all of the developers that this change would touch. For the vast majority of coders, there would be *absolutely no* code change needed to take advantage of this, other than a recompile. There's very little market force opposing it, other than compiler writers complaining...
No, but when you sell someone a tank, you generally give them the spec so that they can perform their own maintenance and modifications on it. If someone is buying something outright, they are buying the right to modify, and the responsibility for those modifications. Of course, certain provisos apply...
Same argument goes for the Athenians, back in the day...
By the way, I'd argue that having a solid navy isn't the key to winning, it's just the key to not getting utterly thumped. The Spanish put together a truly enormous sea force for the Armada, but it wasn't all that successful.
How's about strapping a vortex combustor to the back, and a reconfigurable nosecone to the front? You'd have a perfect blockade weapon.
Imagine that there's a harbour somewhere that you don't want to be used, for whatever reason. From a remote position, you could dump a load of these into the water, and they'd autonomously navigate to form a cordon around the entrance to the harbour. When they reach their intended position, they go passive, and listen. If they detect a ship coming within their sensor range, they convert their nosecone to a flatter configuration (think aerospike), fire up the motor, and become supercavitating torpedos.
At a guess, I'd say it's because they'd need to carry the oxygen supply. Submarines already need to have air on board, so they aren't adding much, but these would need extra tanks and stuff. Having said that, I've got no idea at what kind of rate a saltwater battery uses the oxygen up, or produces hydrogen, but I can't imagine it being that convenient to deal with.
I don't think anyone would disagree with that, but that's not the issue. What he's saying is, given that we've got to stick with x86 for historical and commercial reasons, this would be a relatively quick and easy way to allow the compilers to produce *much* groovier code.
So, if the missile used LIDAR, then the answer would be yes. Anyone happen to know what wavelengths common SA missiles use, if that kind of information is available?
Yeah, we get that in London, too. Except it's not as cheap. Every so often, some politician or other tries to bring the idea of a 24-hour tube service to the table, only to have it swept away by the next scandal.
The Taliban swept in in 1996 largely because of support from Pakistan's ISS and because the Afghan people were tired of the corruption and constant fighting of the Mujahadeen warlords, and thought the Taliban would create stability and relatively good governance. As they discovered, the Taliban weren't that great either.
Need to dredge my memory here, but as far as I remember the arms pipeline set up by the ISS and the CIA for the mujaheddin was reinstated under Pakistani control for the Taliban's benefit. Whether there was any CIA involvement at that point is open to debate, but I doubt it, somehow.
Interestingly, initially the Taliban did create stability and did manage to get rid of corruption and violence in large areas, usually by getting rid of whoever was causing the problem, and then handing power straight back to whoever was the legitimate local leader. To start off with, they had no interest in national leadership. However, at some point between 1994 and 1996, this changed, along with a load of new faces in the upper levels. There is a fair amount of suspicion around the place that this change was entirely due to ISS infiltration, rather than merely their support. Now, it is interesting to speculate whether there was CIA involvement in the ISS-Taliban arms pipeline, and thence in the (possible) ISS infiltration, given that the Taliban *were* a stabilising factor in an unstable region that some very large US firms were trying to invest in.
Uh... The americium only acts as a radiation source. The smoke alarm still needs a battery (or mains connection) to actually do anything useful with the detected radiation levels.
The deep space probes have used radioactive fuel cells driving thermopiles - it's the grey cylinder sticking out of the side in this picture. On a smaller scale, there's this little wonder, which just about fills your gap.
If the signal is being transmitted by radio, that heavily implies that it's serialised, and the easiest way to serialise an image is frame by frame. Without reading the article, that's why I'd guess that there is a base frame rate here. Of course, the Nyquist frequency of a conductive electrode in the eye is going to be an order of magnitude higher than the persistence of a rod or cone in the retina would be designed for, and that's before the signal hits the processing in the optic nerve.
I genuinely think that this is going to happen, one way or another. Even normal-sighted people are going to get some variant on this idea - apart from anything else, it would make IR goggles a fair bit simpler, because you don't need half of the imaging optics, and there's no reason that the signal sent to the chip needs to originate with an optical device. Can you imagine seeing the sound in a club? Or how about flying a submarine with active (or passive) sonar? See what the whales see. Cool or what? It may even be plausible to see with passive microwave pickup - the headset might be a little large, though.
I'm there right now - have been for the last year or so. I have been known to down a can of coke to get to sleep at night. The initial rush doesn't have much of an effect, and the subsequent down sends me swiftly to the land of nod...
An espresso isn't too shoddy in that respect, either.
The US robotwars truly sucks. The UK version is much better.
Only having seen the UK version, can I just say that I find this utterly depressing? Robot Wars is truly an opportunity missed. It could genuinely be a really good programme, if they got rid of a few irritating elements. Like Craig Charles. And the house robots. And the audience. Oh, and let's not forget the stupid, stupid teams with their silly songs.
Slashdot Mirror
19th century soap opera. I have very little time for Dickens myself, but that's just me.
This is an AC/DC converter, of sorts. Add a high voltage capacitor between Vcc and ground on the DC side, and that's the flicker reduced... Of course, by doing that, you've instantly increased the bulk and cost of the mod.
That's assuming they don't ever take their pictures except when they're directly over their targets...
Drill through the sides of the case to get to the wires without tripping the "don't authenticate me" switch.
I've designed tamper-proof systems like this, and it would be extremely hard to get them to work against this sort of approach with your standard coil-and-cone speakers.
When you get down to it, you could get by with a current clamp around the appropriate cable.
So why not save the document as a sequence of events since "blank document" state? That way, you could arrange to know the final state fairly easily, while being able to back the document state up to any stage in its development. As an added bonus, you could throw in the option to generate a "snapshot" file, with only the current state saved, and no backup information.
I know, I know. That was (kind of) my point.
Although, now I actually look into it, it would appear that the DSU-15/B proximity fuse on the Sidewinder uses an IR laser for target ranging, although by the point you'd detect it, it's a little late to be worrying about that.
That does bring up an interesting point, though. Anyone happen to know how the laser proximity fuse stops itself from being fooled by, say, being painted with a random IR stream from the target designed to make the target appear much closer than it actually is?
And in order to take advantage of this, what does the average developer (who doesn't deal in assembly day-to-day) do? They use their funky new compiler. That was the conclusion that I came to after reading the fabled article, anyway...
My point is that, given that there just isn't going to be a radical change in architecture, making the x86 architecture more powerful will inevitably require added complexity because of the way it was initially designed and the complex way that it has grown.
Personally, I'd love to see the x86 arch die a long, slow, horrible death, somewhere a long way away from my development environment, but given the phenomenal market momentum, I just can't see that happening, so anything that can make the same source code more powerful has to be a good thing.
I'm not underestimating the development effort required by a change such as this. However, most of that effort will be expended by the chip designers working on the next revision anyway. This is a valid option for them to look at, given that they are going to be undergoing expensive and hard processes no matter what changes they make.
I also think you might be overestimating the difficulty of implementing this. True, it's a fundamental change to the way that the registers are accessed, but it's not a particularly complex one. It's a software-mediated lookup table into a generic register bank. Not that hard, relative to implementing, say, MMX or SSE.
The true "quick and easy" part comes when you look at the sum total of effort over all of the developers that this change would touch. For the vast majority of coders, there would be *absolutely no* code change needed to take advantage of this, other than a recompile. There's very little market force opposing it, other than compiler writers complaining...
No, but when you sell someone a tank, you generally give them the spec so that they can perform their own maintenance and modifications on it. If someone is buying something outright, they are buying the right to modify, and the responsibility for those modifications.
Of course, certain provisos apply...
Same argument goes for the Athenians, back in the day...
By the way, I'd argue that having a solid navy isn't the key to winning, it's just the key to not getting utterly thumped. The Spanish put together a truly enormous sea force for the Armada, but it wasn't all that successful.
How's about strapping a vortex combustor to the back, and a reconfigurable nosecone to the front? You'd have a perfect blockade weapon.
Imagine that there's a harbour somewhere that you don't want to be used, for whatever reason. From a remote position, you could dump a load of these into the water, and they'd autonomously navigate to form a cordon around the entrance to the harbour. When they reach their intended position, they go passive, and listen. If they detect a ship coming within their sensor range, they convert their nosecone to a flatter configuration (think aerospike), fire up the motor, and become supercavitating torpedos.
Homing mines 8^)
At a guess, I'd say it's because they'd need to carry the oxygen supply. Submarines already need to have air on board, so they aren't adding much, but these would need extra tanks and stuff. Having said that, I've got no idea at what kind of rate a saltwater battery uses the oxygen up, or produces hydrogen, but I can't imagine it being that convenient to deal with.
This is much more generalised, implemented in hardware, taken advantage of by an appropriate compiler, and ignored by an inappropriate one.
I don't think anyone would disagree with that, but that's not the issue. What he's saying is, given that we've got to stick with x86 for historical and commercial reasons, this would be a relatively quick and easy way to allow the compilers to produce *much* groovier code.
So, if the missile used LIDAR, then the answer would be yes. Anyone happen to know what wavelengths common SA missiles use, if that kind of information is available?
Yeah, we get that in London, too. Except it's not as cheap. Every so often, some politician or other tries to bring the idea of a 24-hour tube service to the table, only to have it swept away by the next scandal.
Need to dredge my memory here, but as far as I remember the arms pipeline set up by the ISS and the CIA for the mujaheddin was reinstated under Pakistani control for the Taliban's benefit. Whether there was any CIA involvement at that point is open to debate, but I doubt it, somehow.
Interestingly, initially the Taliban did create stability and did manage to get rid of corruption and violence in large areas, usually by getting rid of whoever was causing the problem, and then handing power straight back to whoever was the legitimate local leader. To start off with, they had no interest in national leadership. However, at some point between 1994 and 1996, this changed, along with a load of new faces in the upper levels. There is a fair amount of suspicion around the place that this change was entirely due to ISS infiltration, rather than merely their support. Now, it is interesting to speculate whether there was CIA involvement in the ISS-Taliban arms pipeline, and thence in the (possible) ISS infiltration, given that the Taliban *were* a stabilising factor in an unstable region that some very large US firms were trying to invest in.
Uh... The americium only acts as a radiation source. The smoke alarm still needs a battery (or mains connection) to actually do anything useful with the detected radiation levels. The deep space probes have used radioactive fuel cells driving thermopiles - it's the grey cylinder sticking out of the side in this picture. On a smaller scale, there's this little wonder, which just about fills your gap.
If the signal is being transmitted by radio, that heavily implies that it's serialised, and the easiest way to serialise an image is frame by frame. Without reading the article, that's why I'd guess that there is a base frame rate here. Of course, the Nyquist frequency of a conductive electrode in the eye is going to be an order of magnitude higher than the persistence of a rod or cone in the retina would be designed for, and that's before the signal hits the processing in the optic nerve.
Definitely. Neural nets can be astonishingly flexible. It may need to be implanted when the user is very young, though.
I genuinely think that this is going to happen, one way or another. Even normal-sighted people are going to get some variant on this idea - apart from anything else, it would make IR goggles a fair bit simpler, because you don't need half of the imaging optics, and there's no reason that the signal sent to the chip needs to originate with an optical device. Can you imagine seeing the sound in a club? Or how about flying a submarine with active (or passive) sonar? See what the whales see. Cool or what?
It may even be plausible to see with passive microwave pickup - the headset might be a little large, though.
I'm there right now - have been for the last year or so. I have been known to down a can of coke to get to sleep at night. The initial rush doesn't have much of an effect, and the subsequent down sends me swiftly to the land of nod...
An espresso isn't too shoddy in that respect, either.
Ah, sod it. I'm giving up right now.
That's what marketing consultants are for 8^)
Doesn't C4 get a small government subsidy?