It would be cool to find out just what the real statistics are. I'm pretty sure, though, that Israel classifies this information as a state secret and we may never know in our lifetimes.
The rockets generate more psychological damage then physical. As far as weapons go, they are rather pathetic. All the iron dome really has to do is to make those it protects feel safe. If statistics have the potential of damaging this feeling of safety then you ca be assured that they will be kept secret.
The other purpose of the iron dome is to limit the desire to fire the rockets in the first place. If one thinks their efforts are in vain then they are less likely to follow through. If Israel can convince members of Hamas that their rockets are not working then there will be fewer rockets launched at Israel.
And hopefully in any lectures on Moore's Law, the students learn that Moore's Law refers to transistors on a die, not the speed of the chips. This 36-core chip probably jumps ahead of Moore's Law a bit, as it's got to be a fairly large die.
Moore's Law refers to the number of components per integrated circuit for minimum cost. Note that this is basically transistor density and is not impacted by core size. Silicon defects and transistor size determine the optimal number of components per IC.
A quote from Wikipedia,
Moore himself wrote only about the density of components, "a component being a transistor, resistor, diode or capacitor," at minimum cost.
With MIMO you have multiple channels
I was under the impression that MIMO gives you multiple antenna to facilitate beam forming. Channel bandwidth requirements do not change nor does the number of channels required. MIMO still only requires 1 channel. A quick wiki search appears to agree with this impression.
Now you can also use multiple channels but this is independent of MIMO technology. Both techniques can be used together - and typically are which might explain the confusion. Either that or I am confused which is always a possibility....
Don't see much need for high power output when Thunderbolt devices like displays will probably need their own power supply anyway.
It's not high power output - it's high power transfer. It will be used as single connection display / ethernet / webcam / USB Audio / power adapter when connecting your laptop to a monitor. Sort of like the ultimate dock.
I built a FreeBSD 9.1 file server using usb 3 / usb 3 docks, but I failed them all back down to using their 2.0 interface due to persistent flakiness/dropping off the bus type issues.
If you look at MacZFS you will notice that ZFS over a USB bus is garbage. Far too many problems - developer says to not even bother reporting the bugs. And in my experience, FreeBSD is not much different in this regard. Had major problems with ZFS over USB while UFS appears to work fine. Use a different connection, like eSATA or Firewire, and ZFS starts to work again.
I only mention this because it is quite possible that USB was working fine. Glitches / delays / disconnects, regardless of which layer they originate in, appear to hit ZFS hard. Better to use eSATA if you have a FreeBSD box.
The real question is how efficient is it?
It does not have to be any more efficient if they manage to reduct weight and increase reliability. Efficiency has a big part to play but even a less efficient engine would be desirable if they improve greatly on other aspects.
Remember that this is being targeted for vehicles that will run mostly on electric power. An ICE is a dead weight when not being used. If someone drives using 90% pure electric then the efficiency gains of carrying less weight could easily outweigh the losses of an ICE that was 5% less efficient but only operates for 10% of the time.
Someone needs to start a Kickstarter project to create a decent calculator. A solid case and keyboard as per the older HP calculators. Color display - they're common enough. Embedded ARM CPU as you would expect in a cell phone. And similar to a cell phone, a rechargable battery. Add in bluetooth, WiFi, and USB for communication and your hardware is done.
The interesting part would be on the software end. One could attempt to emulate an HP calculator - but a standard Forth VM would also be interesting. Synchronizing with a PC is a huge area where things could be improved. It would be great to share a workspace with a computer so that once you solve a problem on the calculator - the requred functions would be available on the PC allowing you to automaticaly integrate the solution into your own code / spreadsheet / etc.
An open calculator design would open up lots of possibilities. Cell phones are great start but regardless of how impressive the software is, it still lacks a physical keyboard. Automatic type correction works great for text - not so much for calculators.