60% of the drive's contents might not change, but its location on disk will. Thanks to the wonders of logical block addressing, the disk controller is free to move data wherever it likes to ensure proper wear leveling.
According to the linked page, it isn't a complete J2EE implementation, which kind of makes sense given the threading and io restrictions specified.
Also, no SQL. Data access is mediated through JDO or JPA. Which also makes sense, given that it's highly likely that the back end isn't a traditional RDBMS.
That bit aside, equipping a programmer with a MacPro desktop or laptop is just far too expensive to justify anyway.
Unless you're developing for multiple platforms, in which case it's actually pretty cost effective to be a reboot away from Linux/Windows/OSX rather than purchasing separate machines.
I guess it would depend on the potential methods of inheritance. If, in addition to directly modifying the production of male sperm, the patch could be delivered through the placenta to a fetus similar to how antibodies are transferred then it could still be heritable through the female.
That all being said, I'm not a biologist, so it's entirely possible that what I've described can't actually happen.
This accurately describes how states currently handle immunization registries. The CDC sets up federal reporting guidelines, but each state has its own registry implementation. This leads to all sorts of fun when trying to do stuff like transfer records when people relocate to another state, or tracking disease infection rates across state lines.
I'm not saying that having a national medical database is necessarily a good thing, but it's immeasurably better than having individual state repositories.
I'm not seeing the actual encryption part, either. It sounds more like message signing to me, with transcription being a hashing function to produce the "signature" protein.
According to the few people I know who have an ipod touch, it's not so much the paying for new functionality, it's the paying for new functionality that other people get for free on their iphone.
So basically, they resent being second-class citizens.
But the real question, of course, is whether or not a teenage hacker girl can successfully use this to navigate your data and fix your TPS reports before the velociraptors eat you all.
They were thinking server stability. The basic problem is that their servers were not capable of dealing with large subsets of the population localized in one area. Over the few months that I played, I don't think a single Tier 4 fortress was successfully captured, because every time one was attempted the server crashed.
There are a lot of good ideas in WAR, but the technology just doesn't back them up.
What is this "brand" you speak of? All the average user cares to know about it is that its a big E on their desktop and its name is "the internet".
And when they click on "the internet", a window pops up that says Internet Explorer on the top, and probably takes them straight to MSN, where they can check their email through Hotmail. It's all part of the MS brand, and they're not about to toss any piece of it.
Good marketing is a lot like whale hunting - you might not notice one or two small harpoons/elements of the branding strategy, but eventually you end up tied to the ship. After which your ribs are made into corsets and your precious body fat is rendered into fuel oil. Or something.
Methinks I should think these metaphors through before I start writing them.
Priceless. 'send()' would have been a boring name for that function.
Look on the bright side, at least it's spelled right. I'd rather have doTheSend() than excetute(), which some kind soul helpfully made an abstract in one of our base classes, and that has since been propagated across a few hundred other classes that I'm not allowed to refactor. A little piece of me dies every time I see it.
At least I sort of know who did it, thanks to cvs history. And if I ever figure out who the hell ers4634 is, they'll truly know what it means to be excetuted. Bastard.
Agreed, but everything I've read to date about electronic voting seems to indicate that it's more expensive to implement/maintain than traditional methods. I honestly don't know if it's any faster in recording votes, but counting them always seems to fall back to manual methods due to accuracy concerns anyway.
So electronic systems inherit the rules that mechanical/manual systems ran under.
Then why bother switching at all? If the best they can do is to match the defect rate of the previous process, then it seems silly to convert over to an entirely different way of doing things.
Mind you, I have no idea if this is actually the case; just that the statement above struck me as a bit odd.
The fact that they have corporate accounts paying for access to the service should preclude the 'beta' label. I like a lot of what Google has done, but sometimes it seems like the whole beta thing is just a convenient excuse for failure, or as a free pass for iffy behavior like testing in production.
3. Is there any way to extract this information from transmissions we've recorded in the past? Would be interesting if turns out that SETI has been pulling down alien sitcoms for years without knowing it.
It's not a question of absolute control, it's a question of more eyeballs. The proof is right in front of us - every single software rev for the thing has been broken, and not utilizing the same method every time.
Slashdot Mirror
Article Link
Most of the articles I saw regarding losses were based on this projection.
Win the civil war?
Sincerely,
a smug Yankee.
60% of the drive's contents might not change, but its location on disk will. Thanks to the wonders of logical block addressing, the disk controller is free to move data wherever it likes to ensure proper wear leveling.
According to the linked page, it isn't a complete J2EE implementation, which kind of makes sense given the threading and io restrictions specified.
Also, no SQL. Data access is mediated through JDO or JPA. Which also makes sense, given that it's highly likely that the back end isn't a traditional RDBMS.
Unless you're developing for multiple platforms, in which case it's actually pretty cost effective to be a reboot away from Linux/Windows/OSX rather than purchasing separate machines.
I guess it would depend on the potential methods of inheritance. If, in addition to directly modifying the production of male sperm, the patch could be delivered through the placenta to a fetus similar to how antibodies are transferred then it could still be heritable through the female.
That all being said, I'm not a biologist, so it's entirely possible that what I've described can't actually happen.
I'd be interested to see whether or not the "patch" is heritable; the article doesn't mention it. In any case, it's really impressive work.
This accurately describes how states currently handle immunization registries. The CDC sets up federal reporting guidelines, but each state has its own registry implementation. This leads to all sorts of fun when trying to do stuff like transfer records when people relocate to another state, or tracking disease infection rates across state lines.
I'm not saying that having a national medical database is necessarily a good thing, but it's immeasurably better than having individual state repositories.
I think you're grossly underestimating popular cinema's appetite for overstimulation.
I'm not seeing the actual encryption part, either. It sounds more like message signing to me, with transcription being a hashing function to produce the "signature" protein.
According to the few people I know who have an ipod touch, it's not so much the paying for new functionality, it's the paying for new functionality that other people get for free on their iphone.
So basically, they resent being second-class citizens.
But the real question, of course, is whether or not a teenage hacker girl can successfully use this to navigate your data and fix your TPS reports before the velociraptors eat you all.
They were thinking server stability. The basic problem is that their servers were not capable of dealing with large subsets of the population localized in one area. Over the few months that I played, I don't think a single Tier 4 fortress was successfully captured, because every time one was attempted the server crashed.
There are a lot of good ideas in WAR, but the technology just doesn't back them up.
And when they click on "the internet", a window pops up that says Internet Explorer on the top, and probably takes them straight to MSN, where they can check their email through Hotmail. It's all part of the MS brand, and they're not about to toss any piece of it.
Good marketing is a lot like whale hunting - you might not notice one or two small harpoons/elements of the branding strategy, but eventually you end up tied to the ship. After which your ribs are made into corsets and your precious body fat is rendered into fuel oil. Or something.
Methinks I should think these metaphors through before I start writing them.
Look on the bright side, at least it's spelled right. I'd rather have doTheSend() than excetute(), which some kind soul helpfully made an abstract in one of our base classes, and that has since been propagated across a few hundred other classes that I'm not allowed to refactor. A little piece of me dies every time I see it.
At least I sort of know who did it, thanks to cvs history. And if I ever figure out who the hell ers4634 is, they'll truly know what it means to be excetuted. Bastard.
Agreed, but everything I've read to date about electronic voting seems to indicate that it's more expensive to implement/maintain than traditional methods. I honestly don't know if it's any faster in recording votes, but counting them always seems to fall back to manual methods due to accuracy concerns anyway.
Then why bother switching at all? If the best they can do is to match the defect rate of the previous process, then it seems silly to convert over to an entirely different way of doing things.
Mind you, I have no idea if this is actually the case; just that the statement above struck me as a bit odd.
We? Who is this 'we'? You tell him, I'm not going anywhere near Bruce while you're in the process of making him angry.
Oblig. link to Schneier Facts
The fact that they have corporate accounts paying for access to the service should preclude the 'beta' label. I like a lot of what Google has done, but sometimes it seems like the whole beta thing is just a convenient excuse for failure, or as a free pass for iffy behavior like testing in production.
In the cases you cite the individual would normally send in quarterly estimated taxes. Otherwise they'd run the risk of underpayment penalties.
On the other hand, the actual advisory from Adobe states that the issue affects all platforms. You'd think they'd be the ones to know best, right?
TFA doesn't mention whether or not Foxit is affected. If not, it's just one more reason to avoid the bloatware that is Reader.
Really? Well shit, Armageddon makes so much more sense now.
3. Is there any way to extract this information from transmissions we've recorded in the past? Would be interesting if turns out that SETI has been pulling down alien sitcoms for years without knowing it.
It's not a question of absolute control, it's a question of more eyeballs. The proof is right in front of us - every single software rev for the thing has been broken, and not utilizing the same method every time.