Well sure YOU DO, but your Gran still has a 5200 with "Turbo memory" (actually that's only 3 years old, she probably has worse).
What year are you living in? 1: Turbocache didn't exist until the 6100. 2: The 5200 is seven years old 3: You can apparently still buy them: eBuyer Link
I quit caffeine altogether once because I realised I was drinking nothing but "Irn Bru", and decided that that was probably a bad idea. For the uninformed, Irn Bru's caffeine content is comparable to mountain dew (except apparently in Canada, where it's caffeine free!). They do an energy drink version too now, called "Irn Bru 32", which I am staying well clear of.
Basically my point was that you shouldn't need to set it back to decimal after printing something in hex, and setting the fill character should be part of the width setting. My preference to using temporaries instead of state changers is purely from having to track down bugs caused by things misusing state. e.g. not specifying std::dec when wanting to print in decimal, and something else that prints in hex not changing the state back to decimal. The same goes for fixed width printing and god knows what else.
They have a few good points though. On the iostream vs printf issue, they're right that printing formatted output with iostream is stupidly verbose. The following are indeed equivalent (actually, the stream version seems to be missing either "0x" or std::showbase) printf("0x%08x\n", x); std::cout std::hex std::setfill('0') std::setw(8) x std::dec std::endl;
I'd much prefer it if it was: using namespace std; cout fixwidth(hex(x), 8, '0') endl; which is nearly as short as the printf line.
My Sony Ericsson phone on "3 Mobile" has completely free skype to skype calls. They don't even charge data. Skype to phone calls only cost skype credit, and not data either.
Especially a JMP (GOTO) or CALL. If the instruction is JMP 0x04203733 and a transmission error makes it do JMP 0x00203733 instead, causing it to attempt to execute data or an unallocated memory page, how the hell can it recover from that? It could be even worse if the JMP instruction is changed only subtly, jumping only a few bytes too far or too close could land you the wrong side of an important instruction that throws off the entire rest of the program. All you could do is to detect the error/crash and restart from the beginning and hope. What if the error was in your error detection code? Do you have to check the result of your error detection for errors too?
I even saw one with two cores (actually "quads" of four cores IIRC) locked, and we successfully unlocked one of them. The other was completely fucked. But you can't say no to adding 50% to the power of a card with just a couple of hours experimenting!
You've nicely summed up three of the kinds of overclocking (restoring the clock speed of a slow-binned-but-actually-really-good cpu, unlocking extra cores and actually overclocking a cpu using a decent cooling system). I remember in the Athlon XP era all the cool kids were taking mobile and other low-power cpus and overclocking the crap out of them. Most people had XP-M 2400s or 2600s, but one of my mates managed to find a Athlon XP-M 2800+ (2.1 GHz stock), and ran it at 2.8 GHz perfectly stable on just air cooling. Royally pissed off my brother with the water-cooled 2600+ that couldn't break 2.5 GHz. Considering the fastest chip of the era was the 2.3 GHz XP 3200+, getting 2.8 GHz out of an air-cooled setup was just insane.
Of course, not long after the Athlon 64s came out and eclipsed everything:)
Most of those mods merely map the Direct-X 10 calls into Direct-X 9. The stuff that Direct-X 9 doesn't support? Geometry shaders? Not supported. Cross-process sharing of surfaces? Not supported.
In other words, those mods let you run games which were written for Direct-X 10, but don't actually use any direct-x 10 features. Nothing more.
I am so for that. Some of the recent EVE trailers would make fantastic parts of movies. Can you imagine a story following someone through becoming a pod pilot, running a mission against pirates (say, the classic "worlds collide" rescue mission, you could have them sneak the first areas and then uncloak to expletives from the pirates, always a good scene), and as a result, getting embroiled in a war for the galactic civilisation's very survival!?
At some point there has to be a scene where their poor little frigate is on the verge of destruction, and the navy warps in. "Good try kid, now lets show you how the Navy deals with pirates", followed by a fair few shots of weapons turning, and then all firing together in an awesome spectacle of destruction.
Ok, I'm no writer. But damn I would like to see an EVE movie.
The scary thing is, a lot of those are true (or at least close). Windows 7 is a great OS. Not sure how it compares to MacOSX, never used that. Windows Media Center is pretty awesome. Office... OpenOffice is catching up, I could probably do without Office. Excel: Pivot Tables. If you've never used/heard of pivot tables, you don't know what you're missing. Everything else in excel could be replaced by OpenOffice Calc. Who doesn't like powerpoint? Not managers (gah double negative). Everyone else hates it purely because of their presentations. Visual Studio IS the best toolchain on the market. I just couldn't develop as quickly without "Intellisense" autocomplete, despite all the people who recommend alternate programs that only have syntax highlighting. I don't know about keyboard, but the 5-button wired MS mice are awesome. I bet there are others that are as good, if not better, but I already have this mouse. Zune? Haha. 360? Best console out at the moment. And I'm saying that as a dev who's currently making a PS3 game. I don't know if that biases me or just reinforces the argument. Then there's the Wii, which isn't really in the argument. It's not Wii vs 360 vs PS3, but Wii+360 vs Wii+PS3. Everyone seems to own one these days.
Assuming there's no vulnerability in the handshake process. And at longer distances, even with a strong antenna, I bet communication with it would be unreliable at best. It's impractical.
But possible.
I wonder if we'll ever see it used as a technique for assassinating someone in power? Against someone like that, I can see it being more practical. It could even be done remotely, so that the killer isn't even at the scene of the crime.
I'm not referring to the battery-backed RFID that's readable from 300 feet, I'm referring to the passive low-frequency RFID that's used in passports (which I already mentioned before). Those RFID tags were designed to be read at a range of 4 inches (actually shorter than your device), but it has been clearly demonstrated that they can actually be read from more than 100 times that distance (35 feet, not 35 cm), as long as a half-decent antenna is used.
If the same holds true for your implant, then it could be reprogrammed from at least 50 feet away. And don't assume that the fact it takes a long time to program would help, it would probably only take a much shorter transmission to trash its programming.
Not that it's very likely, someone would have to specifically know what implant a person had, and would have to be specifically target them, unlike RFID passport skimming, where everyone in the area would be a target.
It sounds like you didn't read what I said at all. I never said it was RFID. I wasn't referring to the 2008 article.
What I did say, is that biomedical devices are designed to communicate at the same range as RFID, despite the skin in the way. Presumably that means after the effect of the skin is taken into account, the signal level is similar. That means that the range when using a decent antenna should be similar, so it should be possible to communicate with a biomedical device from a significant distance.
Then investigate the reports of long-range theft of RFID-data from passports etc. Skin is a good insulator, but the power of your device makes up for that (both it and RFID are designed to be read at the same range).
Of course, if you turned around, so that nearly your entire body was between the device and the hacker, it probably wouldn't be possible.
Slashdot Mirror
Only just, and you'd need a case that has backplates for two more slots than the height of a full ATX motherboard.
On the other hand, can you imagine a PC with a 36-monitor display?
It's an ATI card, therefore uses crossfire and not SLi.
It's also a 3-backplate card, good luck finding a motherboard with three pci-e x16 slots spaced far enough apart.
Well sure YOU DO, but your Gran still has a 5200 with "Turbo memory" (actually that's only 3 years old, she probably has worse).
What year are you living in?
1: Turbocache didn't exist until the 6100.
2: The 5200 is seven years old
3: You can apparently still buy them: eBuyer Link
I quit caffeine altogether once because I realised I was drinking nothing but "Irn Bru", and decided that that was probably a bad idea. For the uninformed, Irn Bru's caffeine content is comparable to mountain dew (except apparently in Canada, where it's caffeine free!). They do an energy drink version too now, called "Irn Bru 32", which I am staying well clear of.
On the plus side, it's bright orange.
Basically my point was that you shouldn't need to set it back to decimal after printing something in hex, and setting the fill character should be part of the width setting.
My preference to using temporaries instead of state changers is purely from having to track down bugs caused by things misusing state. e.g. not specifying std::dec when wanting to print in decimal, and something else that prints in hex not changing the state back to decimal. The same goes for fixed width printing and god knows what else.
I was definitely trialled at my UK high school, 10? years ago.
Well a quick check shows that you can buy 1 TB 2.5" disks easily: http://www.ebuyer.com/search?page=1&store=2&cat=4&subcat=2274&ca76=1000
It's scary how close they are to the capacity of desktop drives (which are currently only available up to 2 TB).
High end mechanicals are measured in TB these days. I think 4 TB ones are being released in the next couple of months.
You'll have to imagine the <<
They have a few good points though. On the iostream vs printf issue, they're right that printing formatted output with iostream is stupidly verbose.
The following are indeed equivalent (actually, the stream version seems to be missing either "0x" or std::showbase)
printf("0x%08x\n", x);
std::cout std::hex std::setfill('0') std::setw(8) x std::dec std::endl;
I'd much prefer it if it was:
using namespace std;
cout fixwidth(hex(x), 8, '0') endl;
which is nearly as short as the printf line.
My Sony Ericsson phone on "3 Mobile" has completely free skype to skype calls. They don't even charge data. Skype to phone calls only cost skype credit, and not data either.
3 are mad.
The phone can already make emergency calls, so that seems like a non-issue...
Perhaps addresses need to be error-corrected then. Oh wait, isn't that the kind of complexity he's trying to avoid?
Especially a JMP (GOTO) or CALL. If the instruction is JMP 0x04203733 and a transmission error makes it do JMP 0x00203733 instead, causing it to attempt to execute data or an unallocated memory page, how the hell can it recover from that? It could be even worse if the JMP instruction is changed only subtly, jumping only a few bytes too far or too close could land you the wrong side of an important instruction that throws off the entire rest of the program. All you could do is to detect the error/crash and restart from the beginning and hope. What if the error was in your error detection code? Do you have to check the result of your error detection for errors too?
I even saw one with two cores (actually "quads" of four cores IIRC) locked, and we successfully unlocked one of them. The other was completely fucked. But you can't say no to adding 50% to the power of a card with just a couple of hours experimenting!
You've nicely summed up three of the kinds of overclocking (restoring the clock speed of a slow-binned-but-actually-really-good cpu, unlocking extra cores and actually overclocking a cpu using a decent cooling system). I remember in the Athlon XP era all the cool kids were taking mobile and other low-power cpus and overclocking the crap out of them. Most people had XP-M 2400s or 2600s, but one of my mates managed to find a Athlon XP-M 2800+ (2.1 GHz stock), and ran it at 2.8 GHz perfectly stable on just air cooling. Royally pissed off my brother with the water-cooled 2600+ that couldn't break 2.5 GHz. Considering the fastest chip of the era was the 2.3 GHz XP 3200+, getting 2.8 GHz out of an air-cooled setup was just insane.
Of course, not long after the Athlon 64s came out and eclipsed everything :)
Most of those mods merely map the Direct-X 10 calls into Direct-X 9. The stuff that Direct-X 9 doesn't support? Geometry shaders? Not supported. Cross-process sharing of surfaces? Not supported.
In other words, those mods let you run games which were written for Direct-X 10, but don't actually use any direct-x 10 features. Nothing more.
Apparently. Of course, it would be nice if they'd named it after what it is...
What the hell is "Data Pilot" supposed to even mean?
I am so for that. Some of the recent EVE trailers would make fantastic parts of movies.
Can you imagine a story following someone through becoming a pod pilot, running a mission against pirates (say, the classic "worlds collide" rescue mission, you could have them sneak the first areas and then uncloak to expletives from the pirates, always a good scene), and as a result, getting embroiled in a war for the galactic civilisation's very survival!?
At some point there has to be a scene where their poor little frigate is on the verge of destruction, and the navy warps in. "Good try kid, now lets show you how the Navy deals with pirates", followed by a fair few shots of weapons turning, and then all firing together in an awesome spectacle of destruction.
Ok, I'm no writer. But damn I would like to see an EVE movie.
The scary thing is, a lot of those are true (or at least close).
Windows 7 is a great OS. Not sure how it compares to MacOSX, never used that. Windows Media Center is pretty awesome.
Office... OpenOffice is catching up, I could probably do without Office.
Excel: Pivot Tables. If you've never used/heard of pivot tables, you don't know what you're missing. Everything else in excel could be replaced by OpenOffice Calc.
Who doesn't like powerpoint? Not managers (gah double negative). Everyone else hates it purely because of their presentations.
Visual Studio IS the best toolchain on the market. I just couldn't develop as quickly without "Intellisense" autocomplete, despite all the people who recommend alternate programs that only have syntax highlighting.
I don't know about keyboard, but the 5-button wired MS mice are awesome. I bet there are others that are as good, if not better, but I already have this mouse.
Zune? Haha.
360? Best console out at the moment. And I'm saying that as a dev who's currently making a PS3 game. I don't know if that biases me or just reinforces the argument. Then there's the Wii, which isn't really in the argument. It's not Wii vs 360 vs PS3, but Wii+360 vs Wii+PS3. Everyone seems to own one these days.
Assuming there's no vulnerability in the handshake process. And at longer distances, even with a strong antenna, I bet communication with it would be unreliable at best. It's impractical.
But possible.
I wonder if we'll ever see it used as a technique for assassinating someone in power? Against someone like that, I can see it being more practical. It could even be done remotely, so that the killer isn't even at the scene of the crime.
That's a scary thought.
I'm not referring to the battery-backed RFID that's readable from 300 feet, I'm referring to the passive low-frequency RFID that's used in passports (which I already mentioned before). Those RFID tags were designed to be read at a range of 4 inches (actually shorter than your device), but it has been clearly demonstrated that they can actually be read from more than 100 times that distance (35 feet, not 35 cm), as long as a half-decent antenna is used.
If the same holds true for your implant, then it could be reprogrammed from at least 50 feet away. And don't assume that the fact it takes a long time to program would help, it would probably only take a much shorter transmission to trash its programming.
Not that it's very likely, someone would have to specifically know what implant a person had, and would have to be specifically target them, unlike RFID passport skimming, where everyone in the area would be a target.
It sounds like you didn't read what I said at all. I never said it was RFID. I wasn't referring to the 2008 article.
What I did say, is that biomedical devices are designed to communicate at the same range as RFID, despite the skin in the way. Presumably that means after the effect of the skin is taken into account, the signal level is similar. That means that the range when using a decent antenna should be similar, so it should be possible to communicate with a biomedical device from a significant distance.
Then investigate the reports of long-range theft of RFID-data from passports etc. Skin is a good insulator, but the power of your device makes up for that (both it and RFID are designed to be read at the same range).
Of course, if you turned around, so that nearly your entire body was between the device and the hacker, it probably wouldn't be possible.
Surely similar techniques to those used to hack wifi/bluetooth devices from miles away (i.e. really nice antennas) would also work here?
The vulgar word (in the literal sense, meaning of the common people)
God damn, "Vulgar" means that!?