Well, the movie is about exactly why this dystopian idea is dumb: people don't give up, especially when they have little to lose. The movie just shows the 'during', not the 'after'.
Obama, Cameron and Mugabe are on a boat, when they realise it is sinking and there is only one lifejacket. They decide, being leaders of ostensibly democratic countries, to vote over who gets the lifejacket, so they each write a name on a piece of paper and put it in a cup.
Once everybody is finished, they counted the pieces of paper, and the results were: Obama: 1 Cameron: 1 Mugabe: 6
OK, how about renaming them "Killer Dolphins". Seriously, what GP was talking about was the removal of the 'killer' from their name. If we were hearing about a lion, tiger, pack of hyenas or grizzly bear that killed people that snuck into its cage after dark nobody would care.
When a core hits an IO block the OS hands the core off the next thread that actually needs to do something. An IO bound application is an example of something that needs less cores.
AKA Parallel Merge sort? Your merging at the end still needs to be done on a single core, so there goes any power advantage you claimed to have. Add to that, your CPUs will all fight with each other over the limited memory bandwidth, making it even worse.
The problem is that each switch causes your cache lines to flush, so it only makes sense firing up a big core if you have something big to do. It seems that Qualcomm has got their execution speed and power consumption just as competitive (or better) as the big.LITTLE scheme, so until their current strategy fails I don't think their idea of making the cores they do have more efficient can really be discarded.
Who said 4 core mobile was awesome? 2 cores, particularly for Android, is great because it lets the GC run in the background without halting your main GUI thread. Beyond that, well, your benchmark scores increase, but that's about it.
Lots of cores is great if your workload is parallelisable, but if that's the case you're generally better off using a bunch of smaller cores like in CUDA or OpenCL. Games don't generally use more than a few cores because they throw the stuff they can at the GPU instead.
It's a fairly narrow set of tasks that need both high-level cores AND can be parallelised.
Hmmm, it seems my memory fools me. I'm sure I read that all of the unlocked-sim models are unlocked-bootloader as well, but I can't seem to find it now. Regardless, they are also planning to have a Google Play version (which will be unlocked, if the S4 and One are anything to go by) and a developer version, which will be bloatware-free and unlocked. But we might have to wait longer for those.
ERMAGERD LESS CPU CORES SUCKS!!! I RUN 4 CPU INTENSIVE TASKS AT ONCE, ONE WITH EACH OF MY INDEX FINGERS, AND ONE WITH EACH OF MY NIPPLES. I LIKE TO KEEP 1BAJILLION MOVIES ON MY PHONE IN HIGHER RESOLUTION THAN THE SCREEN! I NEED A 1TB SD CARD. I CAN TELL BETWEEN 1080p AND 720p AT NORMAL VIEWING DISTANCES ON A 4.7" SCREEN! I NEVER EVEN USE MY PHONE, I JUST DROOL AT THE SPEC SHEET!
Yep, that pretty much summarises all the complaints I've seen.
If you look at the benchmarks, it does better than or equal to a Galaxy S4 on everything except GeekBench, where it still ties for memory speed. So I wouldn't call the CPU/GPU 'mid-range', like everybody seems to be saying.
People want 1080p on a 4.7" screen - are they crazy? I really don't understand where that sentiment comes from. It's just more pixels for the GPU to push around, and it means your games will run worse.
So, they have 'just' 2 cores and a 720p screen, this gives better battery life without making the phone massive. I can totally live with that. I really like what they've done here. They've looked at the system as a whole, and instead of loading it with pointless shit like Samsung, or going with massive bezels on something that's meant to fit in your pocket like HTC, they've made almost the entire front of the phone a screen, make it fit in your hand nicely, given it great battery life, and great performance. And it's customisable and made in the USA. It even has 802.11ac.
What else do you want? And be reasonable, this is today's tech we're talking about.
The Moto X ships with an unlocked bootloader. Take that as you want, but to me it is a sign of change. I know, personally, I swore off of Moto after one particularly bad experience, but this might change my mind.
You can't get a phone with 4GB RAM and 128GB flash for $650, and those are the specs this has. Also, fuck Gorilla Glass, it has a sapphire crystal screen.
I never said the contaminated areas are less than Denver, please don't put words in my mouth. I said the 'contaminated' areas are less than Denver. Big difference. Those single quotes mean I was referring to stuff which wasn't actually contaminated.
Obviously the area directly around the reactor is contaminated. Obviously. It blew up, and it contained radioactive material when it did. That material had to go somewhere, and it (mostly) ended up directly around the reactor. If you thought I was referring to this when I said "10x less than Denver", I wasn't. A miscommunication, misunderstanding, whatever.
But the 'contaminated' areas, the greater surrounding areas which were evacuated, the farmlands, the fields, the houses, the shops, are perfectly habitable, perfectly safe, and yes, 10x less radiation than Denver. That area is a lot bigger than the actual next-to-the-reactor contaminated area. Orders-of-magnitude kind of bigger. Big enough to make the actual contaminated area look pretty irrelevant in the greater scheme of things.
And I think you missed when I said:
We just need to move away from 70s technology and not do stupid things like build them where tsunamis and earthquakes can do a double-wammy, without sufficient safety mechanisms to handle that.
So you see, as far as I can tell, we agree on this. In fact, I believe you'll find my position has been entirely consistent once you read what I actually said. No goalpost shifting. No bait-and-switch. No rabid fanboyism.
All I'm trying to point out is that the actual contamination (no quotes this time) was significantly less, in both area and intensity, than people seem to believe. Even in the bad areas, the ones directly around the reactor, decontamination efforts can make them safe again. Safe to within 6x what is experienced at Denver from 100% natural causes, even after you normalise for the different types of radiation and how it affects the human body.
Even if you can use the D-Wave to take off say 128 bits of uncertainty, that still leaves a pretty big problem in a 512 bit system, never mind a 1024 or 2084 bit system.
Slashdot Mirror
Well, the movie is about exactly why this dystopian idea is dumb: people don't give up, especially when they have little to lose. The movie just shows the 'during', not the 'after'.
Obama, Cameron and Mugabe are on a boat, when they realise it is sinking and there is only one lifejacket. They decide, being leaders of ostensibly democratic countries, to vote over who gets the lifejacket, so they each write a name on a piece of paper and put it in a cup.
Once everybody is finished, they counted the pieces of paper, and the results were:
Obama: 1
Cameron: 1
Mugabe: 6
OK, how about renaming them "Killer Dolphins". Seriously, what GP was talking about was the removal of the 'killer' from their name. If we were hearing about a lion, tiger, pack of hyenas or grizzly bear that killed people that snuck into its cage after dark nobody would care.
Trololol
When a core hits an IO block the OS hands the core off the next thread that actually needs to do something. An IO bound application is an example of something that needs less cores.
AKA Parallel Merge sort? Your merging at the end still needs to be done on a single core, so there goes any power advantage you claimed to have. Add to that, your CPUs will all fight with each other over the limited memory bandwidth, making it even worse.
Java only does array range checking when it needs to, at the beginning/end of a loop or at any point where the array ends.
See: https://wikis.oracle.com/display/HotSpotInternals/RangeCheckElimination
Newer JVMs also allocate objects which won't escape context to the stack.
Well, you could always just buy a new house. And hope it isn't haunted.
It doesn't make sense for a motorcycle. Because ultimately, the phone needs to fit in your pocket.
The problem is that each switch causes your cache lines to flush, so it only makes sense firing up a big core if you have something big to do. It seems that Qualcomm has got their execution speed and power consumption just as competitive (or better) as the big.LITTLE scheme, so until their current strategy fails I don't think their idea of making the cores they do have more efficient can really be discarded.
Uhhhm GPU? Those are all tasks that aren't suitable for an ARM core to be doing.
Who said 4 core mobile was awesome? 2 cores, particularly for Android, is great because it lets the GC run in the background without halting your main GUI thread. Beyond that, well, your benchmark scores increase, but that's about it.
Lots of cores is great if your workload is parallelisable, but if that's the case you're generally better off using a bunch of smaller cores like in CUDA or OpenCL. Games don't generally use more than a few cores because they throw the stuff they can at the GPU instead.
It's a fairly narrow set of tasks that need both high-level cores AND can be parallelised.
Clear your cookies?
Non-electric razors give me a rash. YMMV.
Hmmm, it seems my memory fools me. I'm sure I read that all of the unlocked-sim models are unlocked-bootloader as well, but I can't seem to find it now. Regardless, they are also planning to have a Google Play version (which will be unlocked, if the S4 and One are anything to go by) and a developer version, which will be bloatware-free and unlocked. But we might have to wait longer for those.
ERMAGERD LESS CPU CORES SUCKS!!! I RUN 4 CPU INTENSIVE TASKS AT ONCE, ONE WITH EACH OF MY INDEX FINGERS, AND ONE WITH EACH OF MY NIPPLES.
I LIKE TO KEEP 1BAJILLION MOVIES ON MY PHONE IN HIGHER RESOLUTION THAN THE SCREEN! I NEED A 1TB SD CARD.
I CAN TELL BETWEEN 1080p AND 720p AT NORMAL VIEWING DISTANCES ON A 4.7" SCREEN!
I NEVER EVEN USE MY PHONE, I JUST DROOL AT THE SPEC SHEET!
Yep, that pretty much summarises all the complaints I've seen.
If you look at the benchmarks, it does better than or equal to a Galaxy S4 on everything except GeekBench, where it still ties for memory speed. So I wouldn't call the CPU/GPU 'mid-range', like everybody seems to be saying.
People want 1080p on a 4.7" screen - are they crazy? I really don't understand where that sentiment comes from. It's just more pixels for the GPU to push around, and it means your games will run worse.
So, they have 'just' 2 cores and a 720p screen, this gives better battery life without making the phone massive. I can totally live with that. I really like what they've done here. They've looked at the system as a whole, and instead of loading it with pointless shit like Samsung, or going with massive bezels on something that's meant to fit in your pocket like HTC, they've made almost the entire front of the phone a screen, make it fit in your hand nicely, given it great battery life, and great performance. And it's customisable and made in the USA. It even has 802.11ac.
What else do you want? And be reasonable, this is today's tech we're talking about.
The Moto X ships with an unlocked bootloader. Take that as you want, but to me it is a sign of change. I know, personally, I swore off of Moto after one particularly bad experience, but this might change my mind.
You can't get a phone with 4GB RAM and 128GB flash for $650, and those are the specs this has. Also, fuck Gorilla Glass, it has a sapphire crystal screen.
Never mind the 4GB of RAM and 128GB of flash.
Seriously. Where do you intend to get a phone with those specs?
You won't have a phone with a sapphire screen. Those aren't available *anywhere*, at *any* price.
Call it what you want. It wasn't intended that way.
I never said the contaminated areas are less than Denver, please don't put words in my mouth. I said the 'contaminated' areas are less than Denver. Big difference. Those single quotes mean I was referring to stuff which wasn't actually contaminated.
Obviously the area directly around the reactor is contaminated. Obviously. It blew up, and it contained radioactive material when it did. That material had to go somewhere, and it (mostly) ended up directly around the reactor. If you thought I was referring to this when I said "10x less than Denver", I wasn't. A miscommunication, misunderstanding, whatever.
But the 'contaminated' areas, the greater surrounding areas which were evacuated, the farmlands, the fields, the houses, the shops, are perfectly habitable, perfectly safe, and yes, 10x less radiation than Denver. That area is a lot bigger than the actual next-to-the-reactor contaminated area. Orders-of-magnitude kind of bigger. Big enough to make the actual contaminated area look pretty irrelevant in the greater scheme of things.
And I think you missed when I said:
We just need to move away from 70s technology and not do stupid things like build them where tsunamis and earthquakes can do a double-wammy, without sufficient safety mechanisms to handle that.
So you see, as far as I can tell, we agree on this. In fact, I believe you'll find my position has been entirely consistent once you read what I actually said. No goalpost shifting. No bait-and-switch. No rabid fanboyism.
All I'm trying to point out is that the actual contamination (no quotes this time) was significantly less, in both area and intensity, than people seem to believe. Even in the bad areas, the ones directly around the reactor, decontamination efforts can make them safe again. Safe to within 6x what is experienced at Denver from 100% natural causes, even after you normalise for the different types of radiation and how it affects the human body.
Even if you can use the D-Wave to take off say 128 bits of uncertainty, that still leaves a pretty big problem in a 512 bit system, never mind a 1024 or 2084 bit system.