Actually, the key thing for them is "cheap". They need to keep costing sub-$1k missiles in the ballpark of these Iron dome systems - the more, the better. They might as well just omit the warheads to save money and increase range. Every $50k shot Israel fires with those systems costs 25 Israelis' annual tax contribution to the IDF. Every $55m system they deploy costs 27.500 Israelis' IDF tax contributions.

Palestinians are poor, but they're not *that* poor that they can't leverage those kind of lopsided financial ratios.

I can't help but picture a sign on the door at the exit of an airport in Israel. It reads "Thank-you for not stirring up ancient inter-tribal conflict".

Now I can't help but think of this excellent video :)

Using a nuclear device at high altitude? You do know what happens if you do that, right? That one test bomb knocked out street lights and long distance phone service nearly 1000 miles away and took out a third of all satellites in orbit around Earth at that point in time.

No, in the case of Iron Dome, that's only PR too. They're shooting $50k+ missiles at $800 rockets. Even after factoring in that Israel's per-capita GDP is 20 times that of Palestine's, that's still a losing proposition, even *if* they had a 100% hit rate (which this article is suggesting it's anything-but) and assuming that you get the launcher, radar, etc for free instead of the actual $55 million per unit. It's in Palestine's best interests that Israel deploy as many of them as possible and try to shoot down every last rocket, because every shekel they spend on Iron Domes and missiles is a shekel they don't spend on jets, tanks, and bombs.

... the greater your capacity, the less cycle life matters. If you want an EV that battery that will run a 250Wh/mi vehicle for an average 20 miles a day for 15 years, then you want it to cycle through about 30MWh. If you use a 100 mile (25kWh) battery pack, then that's 1100 cycles. If you use a 200 mile (50kWh) battery pack, then that's 550 cycles. If you use a 400 mile (100kWh) battery pack, then that's a mere 275 cycles. Actually, the improvement is even better than that in the real world, because the greater your capacity vs. how far you're actually driving, the more you can cycle the cells through a less destructive state of charge range rather than doing deep discharges.

A lot of people picture battery packs in EVs backwards, they think that things like hybrids stress the packs the least, PHEVs moderately, and EVs the worst. But it's reversed. If you look at how big hybrid packs are vs. how much electric range they hold, you'll see that they're disproportionately large, even after you factor in any differences in Wh/kg. The reason is that because hybrid packs get cycled so much, they have to keep the cycling in a very narrow state of charge range, only allowing shallow discharges. So if you only have a narrow discharge range, you have to make your pack bigger to make up for it. EVs can discharge through much more of their pack because they need fewer total cycles and only rarely go down toward the lower end of their allowable discharge range. Some EVs also let you limit the max that your pack charges up to to further extend lifespan (it's usually destructive both to use the very top end and the bottom end of the discharge range).

1024 mAhg1 is excellent capacity even vs. brand new graphite or amorphous carbon, about 3x as much as graphite's maximum. Silicon's theoretical max is 8-10x that of graphite, but the main problem with it is durability, it tends to tear itself apart on loading. There are silicon anodes in some newer li-ion cells on the market, but the tech is in its infancy.

That said, the real papers you want to be on the lookout for are cathode improvements, there's a lot more potential for volume/mass reduction there than in the anode. But it seems to be a more difficult challenge. Getting a 3x improvement in anode density is absolutely not the same a getting a 3x improvement in battery life.

Commercial li-ion battery energy densities have continued to improve during that time period, including the commercial introduction of cells with silicon anodes. Of course, silicon anodes are a new tech, so there's a great deal of room for improvement, which probably won't come close to "maxing out" for a decade or more.

Of course, that said, this article is your typical fluff piece following the guidelines of fluff science reporting.

1. Present an oversimplified version of one technology challenge that may or may not address the biggest issue and certainly doesn't address all of them - but don't mention that.
2. Introduce an outside-the-establishment loner with a passion - or at least someone you can try to present as "outside the establishment" and glaze over anyone who helped him.
3. Loner gets a "vision" based on some everyday activity
4. Present their solution and make it out to be a huge revolution that will certainly solve all our problems - if they can only get corporate backing / funding!

I think these sort of articles hurt the image of science because people read them, think "OMG, all our problems are solved!", then when everything's not solved afterward, fail to trust science in the future. For example, in this case, the most important element to improve is the cathode, not the anode. And cathode improvements are less common and usually less major than anode improvements. There's also tons of different anode improvements out there in various stages of research. Pretty much all of the silicon ones get way better than graphite or amorphous carbon.

That doesn't mean that this isnt an important paper - actually, from looking at it, it looks pretty good. It's just not "all that".

BTW, anyone know how credible this journal is? I see it's hosted on Nature.com but not part of Nature, and I tried to find an impact rating for it but couldn't.

But you see you are in the Windows CE embedded niche. Your vision is clouded.

I'm not in a "windows CE embedded" niche and the grandparent poster is right.

It's not an issue with the target. It's an issue with the platform(s) supported by the development tool vendors and the chip manufacturers.

For instance: With Bluetooth 4.0 / Bluetooth Low Energy (BLE), two of the premier system-on-a-chip product families are from Texas Instruments and Nordic Semiconductors.

TI developed their software in IAR's proprietary development environment and only supports that. Their bluetooth stack is only distributed in object form - for IAR's tools - with a "no reverse engineering" and "no linking to open source (which might force disclosure)". IAR, in turn, doesn't support anything but Windows. (You can't even use Wine: The IAR license manager needs real Windows to install, and the CC Debugger dongle, for burning the chip and necessary for hooking the debugger to the hardware debugging module, keeps important parts of its functionality in a closed-source windows driver.) IAR is about $3,000/seat after the one-month free evaluation (though they also allow a perpetual evaluation that is size-crippled, and too small to run the stack.)

The TI system-on-a-chip comes with some very good and very cheap hardware development platforms. (The CC Debugger dongle, the USB/BLE-radio stick, and the Sensor Tag (a battery-powered BLE device with buttons, magnetometer, gyro, barometer, humidity sensor, ambient temp sensor, and IR remote temp sensor), go for $49 for each of the three kits.) Their source code is free-as-in-beer, even when built into a commercial product, and gives you the whole infrastructure on which to build your app. But if you want to program these chips you either do it on Windows with the pricey IAR tools or build your own toolset and program the "bare metal", discarding ALL TI's code and writing a radio stack and OS from scratch.

Nordic is similar: Their license lets you reverse-engineer and modify their code (at your own risk). But their development platforms are built by Segger and the Windows-only development kit comes with TWO licenses. The Segger license (under German law), for the burner dongle and other debug infrastruture, not only has a no-reverse-engineering clause but also an anti-compete: Use their tools (even for comparison while developing your own) and you've signed away your right to EVER develop either anything similar or any product that competes with any of theirs.

So until the chip makers wise up (or are out-competed by ones who have), or some open-source people build something from scratch, with no help from them, to support their products, you're either stuck on Windows or stuck violating contracts and coming afoul of the law.

He said ice sheet. So we're supposed to ignore what he actually said and assume he meant something completely different? Um, no.

"I am not well read in this department" - wait a minute, you can give exact cites for research papers on sea ice, but don't even have a *general* conception of what percentage of the Antarctic ice sheet is gaining versus what is losing? Something tells me you're just grabbing cites you've never even read from denier websites.

Let me help you out with ice sheet. Pretty much all of the East Antarctic ice sheet is gaining, while pretty much the only area losing is the Antarctic peninsula and surrounding areas in West Antarctica. Now, they're losing *mass* a lot faster per unit area than the east is gaining mass, but in terms of area, the overwhelming majority of Antarctica is gaining ice. Because it almost never gets above freezing there, even in a warming world.

The 2010 paper was evaluating the failed CMIP5 predictions

If you'd actually read the paper, which you clearly haven't, you'd know that they themselves did the CMIP5 runs, it's not CMIP5 runs that had been done earlier. Do you even have a clue what CMIP5 stands for? Coupled Model Intercomparison Project Phase 5. As in, "there were four freaking phases that came before this one". CMIP5 is comprised of all of the latest models from all over the world. They didn't even start planning CMIP5 unitl September 2008. Your notion that this is some sort of review of old climate predictions just shows how terrible your understanding is of what you're talking about and how you don't actually read the papers that you cite, that you're just simply grabbing them from whatever denialist trash websites you read.

First, that's a paper from 2010. How was a paper from 2010 supposed to be "predicting" anything about what scientists in the past thought?

Secondly, and more importantly, I had been responding to Archangel Michael, who was talking about the thickness of the Antarctic ice sheet, not Antarctic sea ice. So your link about pack ice is totally irrelevant.

But hey, let's switch topics totally and talk about sea ice, since you seem to want to. Here's how the IPCC sums up all papers on the modelling of antarctic sea ice, including this one:

Whereas sea ice extent in the Arctic has decreased, sea ice extent in the Antarctic has very likely increased. Sea ice extent across the Southern Hemisphere over the year as a whole increased by 1.3– 1.67% per decade from 1979–2012 with the largest increase in the Ross Sea during the autumn, while sea ice extent decreased in the Amundsen-Bellingshausen Sea. The observed upward trend in Antarctic sea ice extent is found to be inconsistent with internal variability based on the residuals from a linear trend fitted to the observations, though this approach could underestimate multi-decadal variability. The CMIP5 simulations on average simulate a decrease in Antarctic sea ice extent , though Turner et al. (2013) find that approximately 10% of CMIP5 simulations exhibit an increasing trend in Antarctic sea ice extent larger than observed over the 1979-2005 period. However, Antarctic sea ice extent variability appears on average to be too large in the CMIP5 models . Overall, the shortness of the observed record and differences in simulated and observed variability preclude an assessment of whether or not the observed increase in Antarctic sea ice extent is inconsistent with internal variability. Based on Figure 10.16b and (Meehl et al., 2007b), the trend of Antarctic sea ice loss in simulations due to changes in forcing is weak (relative to the Arctic) and the internal variability is high, and thus the time necessary for detection is longer than in the Arctic.

Weak trend, short observed record, and high internal variability in the simulations. Which shouldn't be surprising, sea ice is a lot harder to model than ice sheet thickness, which really only has three main parameters - snowfall, melt/sublimation, and outflow, and the short observed record is due to how few people historically have navigated antarctic waters vs. arctic.

But again, to reiterate the primary point: the conversation you jumped into was about ice sheet thickness, not sea ice.

I'm sorry, I just read through that paper, and nowhere in it does it say that a decline in Antarctic ice is a forecast of AGW. That's one of the worst examples of "proof by ghost reference" I've ever seen. Not to mention that the paper is mainly focused on the Antarctic Peninsula, the one place that actually gets melt on more than super-rare occasions and juts into a different climate zone.

Go right ahead and point me to where a decline in Antarctic ice was a forecast of AGW.

You do know that - below freezing - there's an inverse correlation between temperature and snowfall, don't you? And I really hope you know that it's very rare that temperatures rise above freezing in the vast majority of Antarctica, whether you add a couple degrees to the temperature or not, right? Or did you not know / ever consider that?

Just because you didn't realize something that should have been really bloody obvious to you doesn't mean it was a scientific prediction by your straw-man scientists.

AEI, for one. $10k for any paper that attacks the IPCC reports. There's other public offers out there, too. And I'm sure they're outnumbered 100 times over by not-so-public ones.

Corr: That should read "doesn't lose much IR transmission as a consequence of neutron bombardment like happens in higher frequency bands" - accidentally lost that middle part. Fused silica and fused quartz (especially the latter, but also the former) blacken under neutron exposure, losing transparency; it's even done intentionally to make jewelry. But the papers I ran into when researching the topic showed that this effect isn't very pronounced in the IR band.