I quoted the part of the article where the reporter states that the security firm made that forecast. But as often happens, the headline makes claims which don't match either the truth or the body of the article. It's far from unknown for reporters or opinion writers to get a nasty shock when they see the headline which the subeditor chose to put on their copy.
If the issue were the length of the headline, a 20% saving could be made and the accuracy improved by rewriting it to "Online attacks could lead to deaths, warns Europol".
The first link in the summary is to a news report with the headline "First online murder to happen by the end of 2014, warns Europol". When you read the story, what it actually claims is
The study, which was published last week, analysed the possible physical dangers linked to cyber criminality and found that a rise in ‘injury and possible deaths’ could be expected as computer hackers launch attacks on critical connected equipment.
The assessment particularly referred to a report by IID, a US security firm, which forecast that the world’s first murder via a ‘hacked internet-connected device’ would happen by the end of 2014.
And the reference that it mentions is right here and says
With more objects being connected to the Internet and the creation of new types of critical infrastructure, we can expect to see (more) targeted attacks on existing and emerging infrastructures, including new forms of blackmailing and extortion schemes (e.g. ransomware for smart cars or smart homes), data theft, physical injury and possible death [188], and new types of botnets.
No mention of 2014. No assertion that it will happen: just that it might.
TL;DR: Europol isn't predicting an online murder in 2014. That's just a subeditor who either didn't understand the plain English of the reporter or who chose to outright lie when writing the headline in order to sensationalise it.
No. The software isn't the hard part. The hard part is the requirements gathering for the data schemata (aka archetypes). For example, suppose you want to create an archetype for blood samples. At a minimum you need to talk to phlebologists and GPs, but you probably also need input from other specialists who might refer someone for a blood sample to see what they need from the data. Then you work out the indivisible chunks of data, run them past your domain experts, fix any bugs they spot, repeat. And even with a lot of input from experts, unless the standards for blood sampling are universal you risk creating an archetype which doesn't quite fit the way the hospitals in the neighbouring province do things.
the situation is analogous to the poor dudes in gitmo. Everybody knows they're not terrorists, yet because they were seized illegally there's no way for the justice system to process them.
I'm puzzled by this one. Surely all the justice system needs to do is say "The U.S. Constitution binds the actions of the U.S. government even outside U.S. territory" and then admit a writ of habeas corpus?
I'm not quite sure whether your question is "Why allow reference comparisons?" or "Why use == for reference comparisons?" If it's the former: if you look at equals(Object o) implementations, a lot of them begin with if (this == o) return true; It can be a major performance boost in some situations.
Or get bitten by. The hypothesised reservoir is fruit bats, but other primates can be infected by filoviruses, and pigs have also been found to carry them asymptomatically. Source: the WHO fact sheet on Ebola virus disease.
The compiler doesn't always know how big that free space is, because there's no type or size associated with it. It's possible in some cases to do bounds-checking, but not in many others. It's a fundamental difficulty with the language, and it's impossible for the compiler to check all those bounds without help from the language or the programmer.
That's not quite true: the compiler could arrange to pass around more than just the raw pointer (or in extremis could maintain a duplicate of the malloc table and work out the bounds given the pointer), but the performance hit would be considerably more than for direct checking.
Only two? I think that grammatically any of the three nouns could be the one that's growing on trees. The 13-year-old growing on trees is even more semantically problematic than the AIDS patients.
"This is/. after all" was intended to refer to "I admit not having read", but now that you point it out I suppose it is fair to say that most of the stuff posted is clickbait. I couldn't say in general whether that's because it's submitted by the authors of the links or because submitters can't be bothered to track back to the less sensational source.
I admit not having read the clickbait (this is/. after all), but I presume that the real story behind it is that an experiment to measure the muon magnetic moment has recently moved from Brookhaven to Fermilab to get access to more energetic muons. They're hoping to start measuring data in 2.5 years.
Well, if we use the same kind of accounting principles that were used to try to extradite Gary McKinnon, this is an article about an intelligence agency causing potentially billions of pounds/dollars/euros of damage to computers, 99%+ of which were not "legitimate targets" for a black bag job. It may not be a surprise, but it's still rather embarrassing.
$42k would be low for an entry-level video game developer in a low cost of living area even as just a salary.
You're thinking in US terms. It's pretty good in the UK (25k GBP, which is the top end of what the main UK graduate careers site thinks an entry-level game programmer might get).
Also, real computer scientists know who the fucking founding father of the discipline is.
I used to think I was a computer scientist, but now I'm not sure. Euclid? Diophantus? Babbage? Lovelace (albeit she'd be a founding mother)? Church? Goedel?
The UK one which inspired the US one is actually mentioned in the summary, but if you're assuming that 90% of/.ers won't even RTFS you're probably right.
But he's not charged with money laundering. He's charged with conspiracy to launder money. If dirty money comes in and clean money comes out then money laundering has occurred, whether or not some of the intermediate steps involved the exchange of non-monetary assets. So "I was only involved in transactions involving the exchange of non-monetary assets" is irrelevant: what matters is a) whether they were part of a larger chain of transactions to launder money; b) whether he was aware of that larger chain.
Slashdot Mirror
I quoted the part of the article where the reporter states that the security firm made that forecast. But as often happens, the headline makes claims which don't match either the truth or the body of the article. It's far from unknown for reporters or opinion writers to get a nasty shock when they see the headline which the subeditor chose to put on their copy.
If the issue were the length of the headline, a 20% saving could be made and the accuracy improved by rewriting it to "Online attacks could lead to deaths, warns Europol".
The first link in the summary is to a news report with the headline "First online murder to happen by the end of 2014, warns Europol". When you read the story, what it actually claims is
And the reference that it mentions is right here and says
No mention of 2014. No assertion that it will happen: just that it might.
TL;DR: Europol isn't predicting an online murder in 2014. That's just a subeditor who either didn't understand the plain English of the reporter or who chose to outright lie when writing the headline in order to sensationalise it.
No. The software isn't the hard part. The hard part is the requirements gathering for the data schemata (aka archetypes). For example, suppose you want to create an archetype for blood samples. At a minimum you need to talk to phlebologists and GPs, but you probably also need input from other specialists who might refer someone for a blood sample to see what they need from the data. Then you work out the indivisible chunks of data, run them past your domain experts, fix any bugs they spot, repeat. And even with a lot of input from experts, unless the standards for blood sampling are universal you risk creating an archetype which doesn't quite fit the way the hospitals in the neighbouring province do things.
If you're that worried about it, why don't you run a local mirror and point your hosts file at it?
His role on most of the papers was probably just to write the grant request.
Medicine. Patents give large US pharmaceutical companies monopolies on treatments and the embargo prevents them from being sold to Cuba.
I'm puzzled by this one. Surely all the justice system needs to do is say "The U.S. Constitution binds the actions of the U.S. government even outside U.S. territory" and then admit a writ of habeas corpus?
I'm not quite sure whether your question is "Why allow reference comparisons?" or "Why use == for reference comparisons?" If it's the former: if you look at equals(Object o) implementations, a lot of them begin with if (this == o) return true; It can be a major performance boost in some situations.
International Social Outcasts.
Or get bitten by. The hypothesised reservoir is fruit bats, but other primates can be infected by filoviruses, and pigs have also been found to carry them asymptomatically. Source: the WHO fact sheet on Ebola virus disease.
That's not quite true: the compiler could arrange to pass around more than just the raw pointer (or in extremis could maintain a duplicate of the malloc table and work out the bounds given the pointer), but the performance hit would be considerably more than for direct checking.
Only two? I think that grammatically any of the three nouns could be the one that's growing on trees. The 13-year-old growing on trees is even more semantically problematic than the AIDS patients.
"This is /. after all" was intended to refer to "I admit not having read", but now that you point it out I suppose it is fair to say that most of the stuff posted is clickbait. I couldn't say in general whether that's because it's submitted by the authors of the links or because submitters can't be bothered to track back to the less sensational source.
I admit not having read the clickbait (this is /. after all), but I presume that the real story behind it is that an experiment to measure the muon magnetic moment has recently moved from Brookhaven to Fermilab to get access to more energetic muons. They're hoping to start measuring data in 2.5 years.
An alpha particle?
Well, if we use the same kind of accounting principles that were used to try to extradite Gary McKinnon, this is an article about an intelligence agency causing potentially billions of pounds/dollars/euros of damage to computers, 99%+ of which were not "legitimate targets" for a black bag job. It may not be a surprise, but it's still rather embarrassing.
You're thinking in US terms. It's pretty good in the UK (25k GBP, which is the top end of what the main UK graduate careers site thinks an entry-level game programmer might get).
There have been cases (at least two reported this year) of people burning down houses when using this approach, so a modicum of caution is indicated.
I used to think I was a computer scientist, but now I'm not sure. Euclid? Diophantus? Babbage? Lovelace (albeit she'd be a founding mother)? Church? Goedel?
Austria is metric, so it's only 60mph.
The UK one which inspired the US one is actually mentioned in the summary, but if you're assuming that 90% of /.ers won't even RTFS you're probably right.
Vulcan definitely has "religious connotations".
But he's not charged with money laundering. He's charged with conspiracy to launder money. If dirty money comes in and clean money comes out then money laundering has occurred, whether or not some of the intermediate steps involved the exchange of non-monetary assets. So "I was only involved in transactions involving the exchange of non-monetary assets" is irrelevant: what matters is a) whether they were part of a larger chain of transactions to launder money; b) whether he was aware of that larger chain.
Probably not, but they don't make $50 billion annually either.
"A new law that has a fairly vague scope"? It's a law which dates back to 1995, and its scope is fairly clear. See the ECJ's Factsheet.