Sorry, but South Africa is a signatory of the NPT. They developed nuclear weapons in secrecy under Apartheid, but those were dismantled before signing the NPT in 1991.
Looking for shortcuts I can understand, but I think we're already seeing that with "cannot know the momentum and the position". But if we're inside the simulation we wouldn't notice if it gets switched off, because we wouldn't have any post-simulation consciousness. And anything we can do, as tiny specks of dust in the corner of one medium sized galaxy in a very large universe isn't going to have much impact on the overall simulation, I would think.
Yeah, I think Intel was running scared for a bit so pulled some nasty moves. The gist from this side of the argument that I'm getting is now that Intel's nice and comfortable, it might be worrying about some old skeletons in its closet coming back from the grave to haunt it...
From that link, it comments that a lot of it may have been influenced by Nixon's decisions. I'd like to add that it was probably furthered by GWB with his WMD wild goose chase in Iraq... these people fail to realise that there was once a time when the US/UK was actually threatened by countries which did real harm to more than a couple buildings...
That's odd. I'm struggling to do a smooth zoom of our (fully assembled) robot using Solidworks on a Nehalem-era i5. If you remove all of the internals, nuts, bolts and washers it isn't quite as bad... the GPU is a lot newer than the CPU, as well, and hardly gets taxed. Maybe next year's Solidworks will be better...
Just trolling =) There's a line of thinking that says that the US sentiment was very much against war at the time but that the president would ignore this or attempt to manipulate the public, and would need a decisive attack from which no retaliation could be given until the US war effort was well under way. It's fairly well explained here that this isn't really true, US polls showed that the people were happy to go to war with Japan and Germany, so I don't really think the motive the conspirators are claiming is realistic.
Erm... he called you an *Intel* fanboy. That litigation is because of Intel using its monopoly position to force PC makers to use its chips instead of those of AMD. Thus, relevant.
Unless the increased demand and rising oil prices make alternative electricity sources more economically viable. Sure, electric cars will have a short term marginal cost purely of the dirty power, but once the supply system adapts (and it will) the new power is likely to come in a large portion from renewables.
That's essentially what he did: sent out encrypted files, and gave the password to just a few people who he trusted. A website or single system is far too easily compromised, anything other than what he did is dependant on a central server and is far too easily taken down by something with the resources of the US government. His problem wasn't with his technical skills or choice of encryption technique or password, but rather with his people skills and his choice of people to trust with the password. One of those people turned out to be untrustworthy, which is why there was a problem, not because of Assange's encryption efforts.
Your question about the bank is moot - I wouldn't care as long as the password was safely kept. If somebody leaks the password, especially if they know what might happen and they do it intentionally, that is their fault, not the person who set up the system as a safeguard. Besides, all of this assumes there would be consequences of the leaked data against the people the data was actually about - so far, the only consequences have been diplomatic and political ones, not things like regimes killing informers (well, besides the US locking up Manning, that is).
The moment Cryptome releases documents which are actually politically sensitive (you know, like the US cables, or the current Syrian emails), I might start taking them seriously.
You are aware of the stance on hostage takers, right? No bargaining. Well, the government has purposefully mixed in 'hostages' with this data which should be released to the public. Are you seriously saying that we should play to their game?
There was a reasonable effort. For instance, the names of informants were all redacted to prevent harm to them.
Claiming that what wikileaks did was a bad thing because they went too far, well, if the government hadn't been classifying all of this stuff wikileaks wouldn't be necessary in the first place. Don't blame Wikileaks because the government is mixing all of this 'personal' information in with stuff that should be released to the people. That is like terrorists using human shields to avoid snipers.
It still explains why it is stupid to use a Vector in a single-threaded application. The fact that it's stupid to use a Vector in a multi-threaded application is entirely besides the point;-)
Yeah, I'm just pointing out that there are cases where the standard method is far from the best, even for something trivial like sorting, and strings and integers are something which pop up all the time. Sure, for general business "keep track of these 200 customers" kind of jobs blue-collar IT is fine, but the moment you want to sequence somebody's genome and look for specific patterns to see if they have a disease, do programming in any sort of limited embedded environment or communicate between different types of systems somebody who doesn't understand the foundations of the techniques they are using is useless. Most of the 'grunt work' could actually be done by improving our IDEs instead of hiring blue collar IT workers.
Approximately one minute and 19 seconds into last night’s launch, the Falcon 9 rocket detected an anomaly on one first stage engine. Initial data suggests that one of the rocket’s nine Merlin engines, Engine 1, lost pressure suddenly and an engine shutdown command was issued immediately. We know the engine did not explode, because we continued to receive data from it. Our review indicates that the fairing that protects the engine from aerodynamic loads ruptured due to the engine pressure release, and that none of Falcon 9’s other eight engines were impacted by this event.
As designed, the flight computer then recomputed a new ascent profile in real time to ensure Dragon’s entry into orbit for subsequent rendezvous and berthing with the ISS. This was achieved, and there was no effect on Dragon or the cargo resupply mission.
Falcon 9 did exactly what it was designed to do. Like the Saturn V, which experienced engine loss on two flights, Falcon 9 is designed to handle an engine out situation and still complete its mission.
Slashdot Mirror
The thing is, if you deposit say $1 into your account, then they can loan you $10. $9 was created out of thin air, as AC rightly surmises.
My friend had a big lytic blow just last week... fuzz EVERYWHERE!!!
Sorry, but South Africa is a signatory of the NPT. They developed nuclear weapons in secrecy under Apartheid, but those were dismantled before signing the NPT in 1991.
Looking for shortcuts I can understand, but I think we're already seeing that with "cannot know the momentum and the position". But if we're inside the simulation we wouldn't notice if it gets switched off, because we wouldn't have any post-simulation consciousness. And anything we can do, as tiny specks of dust in the corner of one medium sized galaxy in a very large universe isn't going to have much impact on the overall simulation, I would think.
My GPU is Nvidia because I also need CUDA for some of my image processing. Maybe SW likes AMD/ATI better.
It you're inside the simulation, how will you tell if the simulation is slowing down?
Yeah, I think Intel was running scared for a bit so pulled some nasty moves. The gist from this side of the argument that I'm getting is now that Intel's nice and comfortable, it might be worrying about some old skeletons in its closet coming back from the grave to haunt it...
From that link, it comments that a lot of it may have been influenced by Nixon's decisions. I'd like to add that it was probably furthered by GWB with his WMD wild goose chase in Iraq... these people fail to realise that there was once a time when the US/UK was actually threatened by countries which did real harm to more than a couple buildings...
That's odd. I'm struggling to do a smooth zoom of our (fully assembled) robot using Solidworks on a Nehalem-era i5. If you remove all of the internals, nuts, bolts and washers it isn't quite as bad... the GPU is a lot newer than the CPU, as well, and hardly gets taxed. Maybe next year's Solidworks will be better...
Just trolling =) There's a line of thinking that says that the US sentiment was very much against war at the time but that the president would ignore this or attempt to manipulate the public, and would need a decisive attack from which no retaliation could be given until the US war effort was well under way. It's fairly well explained here that this isn't really true, US polls showed that the people were happy to go to war with Japan and Germany, so I don't really think the motive the conspirators are claiming is realistic.
Erm... he called you an *Intel* fanboy. That litigation is because of Intel using its monopoly position to force PC makers to use its chips instead of those of AMD. Thus, relevant.
Unless the increased demand and rising oil prices make alternative electricity sources more economically viable. Sure, electric cars will have a short term marginal cost purely of the dirty power, but once the supply system adapts (and it will) the new power is likely to come in a large portion from renewables.
It's almost like the government is only willing to fund the things which might be of long term benefit... wow.
No, he just saw it coming and made sure that it was successful enough to galvanise the rest of the country into action.
That's essentially what he did: sent out encrypted files, and gave the password to just a few people who he trusted. A website or single system is far too easily compromised, anything other than what he did is dependant on a central server and is far too easily taken down by something with the resources of the US government. His problem wasn't with his technical skills or choice of encryption technique or password, but rather with his people skills and his choice of people to trust with the password. One of those people turned out to be untrustworthy, which is why there was a problem, not because of Assange's encryption efforts.
Your question about the bank is moot - I wouldn't care as long as the password was safely kept. If somebody leaks the password, especially if they know what might happen and they do it intentionally, that is their fault, not the person who set up the system as a safeguard. Besides, all of this assumes there would be consequences of the leaked data against the people the data was actually about - so far, the only consequences have been diplomatic and political ones, not things like regimes killing informers (well, besides the US locking up Manning, that is).
The moment Cryptome releases documents which are actually politically sensitive (you know, like the US cables, or the current Syrian emails), I might start taking them seriously.
Claiming that it is Assange's fault that the Guardian editor leaked the password... how utterly twisted is your logic?
You are aware of the stance on hostage takers, right? No bargaining. Well, the government has purposefully mixed in 'hostages' with this data which should be released to the public. Are you seriously saying that we should play to their game?
There was a reasonable effort. For instance, the names of informants were all redacted to prevent harm to them.
Claiming that what wikileaks did was a bad thing because they went too far, well, if the government hadn't been classifying all of this stuff wikileaks wouldn't be necessary in the first place. Don't blame Wikileaks because the government is mixing all of this 'personal' information in with stuff that should be released to the people. That is like terrorists using human shields to avoid snipers.
The trouble is, the followers of Jesus don't tend to follow his teachings, but rather those of their church.
It still explains why it is stupid to use a Vector in a single-threaded application. The fact that it's stupid to use a Vector in a multi-threaded application is entirely besides the point ;-)
Yeah, I'm just pointing out that there are cases where the standard method is far from the best, even for something trivial like sorting, and strings and integers are something which pop up all the time. Sure, for general business "keep track of these 200 customers" kind of jobs blue-collar IT is fine, but the moment you want to sequence somebody's genome and look for specific patterns to see if they have a disease, do programming in any sort of limited embedded environment or communicate between different types of systems somebody who doesn't understand the foundations of the techniques they are using is useless. Most of the 'grunt work' could actually be done by improving our IDEs instead of hiring blue collar IT workers.
Approximately one minute and 19 seconds into last night’s launch, the Falcon 9 rocket detected an anomaly on one first stage engine. Initial data suggests that one of the rocket’s nine Merlin engines, Engine 1, lost pressure suddenly and an engine shutdown command was issued immediately. We know the engine did not explode, because we continued to receive data from it. Our review indicates that the fairing that protects the engine from aerodynamic loads ruptured due to the engine pressure release, and that none of Falcon 9’s other eight engines were impacted by this event.
As designed, the flight computer then recomputed a new ascent profile in real time to ensure Dragon’s entry into orbit for subsequent rendezvous and berthing with the ISS. This was achieved, and there was no effect on Dragon or the cargo resupply mission.
Falcon 9 did exactly what it was designed to do. Like the Saturn V, which experienced engine loss on two flights, Falcon 9 is designed to handle an engine out situation and still complete its mission.
It's far from perfect, but check out LabView as an alternative input method to CLI/text based programming.
I think GP is referring to Java, where a Vector is a lot slower than an ArrayList, but is guaranteed to be threadsafe.