What we need is a physical write-protect switch for the firmware itself, as well as for the contents of the drive.
It wouldn't be hard to have a single pin control whether or not the microcontroller firmware can be written to.
What we need is a physical switch that write-protects the microcontroller firmware. Most people would never want to update the firmware on their USB controller so it can default to "off".
Blackbody radiation is emitted from all sides of the emitter; it cannot be made directional. This means that the design that MIT has created, with the collector sandwiched against the emitter, will be at most 50% effective (When used with a light-source derived heat source). This is because some non-trivial portion of the re-emitted light will be beamed off the back of the device, where there is no collector to catch it!
Couldn't you put the intermediate radiator behind a layer of glass with a coating that is tuned to be highly reflective at the exact frequency that it is re-radiating at? That would reduce the amount of wasted energy.
In the article the intermediate body is simply absorbing heat energy but then re-radiating it at a specific frequency. Would the Carnot effiency rules apply?
Actually, the performance difference between an i3 and an i7 is negligible.
That chart you pointed at is specifically for gaming. If you're doing parallel compiling, or running multiple VMs, or other easily parallelizable work the fact that an i7 generally has twice as many cores/threads can make a huge difference.
At work we have a 24-core machine that we use for compiling. It makes a huge difference when you're basically building a custom linux distro.
Even when using sendfile() in linux, the disk does a DMA transfer into RAM, and the NIC does a DMA transfer out of RAM.
While the CPU is not involved in copying the data, it still goes into RAM.
The user input is in the form of specially-crafted HTTP headers in the HTTP request that cause environment variables to be set on the server.
While you don't need to pass arguments, you still need to set environment variables based on user input.
Whoever thought it was a good idea to allow an HTTP request to set environment variables within the HTTP server to arbitrary values wasn't thinking about security.
Sony Xperia Z3 Compact
I have no problems at all with an ISP prioritizing certain types of traffic, but that prioritization should be 1) under the control of the subscriber, and 2) it should *only* affect traffic belonging to that subscriber. My traffic and your traffic should be shaped (as a whole) based on the subscriptions that each of us has paid for.
That is, I could ask my ISP to prioritize my Netflix packets over my bittorrent packets, but if you and I have paid for the same level of service then your VoIP packets shouldn't get priority over my Netflix packets.
Typically the scoopers carry a tank of fire retardant concentrate that gets injected into the scooped water.
...and the DC-10 can deliver as much water as five of the largest water scoopers.
I question that. The Martin Mars scooper holds 7200 US gallons.
Most providers of "cloud" services are *not* free. You pay for time, workload, network, storage, etc.
In IaaS (infrastructure as a service) you're basically just renting time/space/bandwidth on someone else's equipment.
To an independent body that doesn't report to the police.
If someone complains about an interaction with an officer where the officer's camera has no record of the interaction, the officer is assumed to be guilty.
That should give officers incentive to ensure their cameras are in working order.
If all else fails, lower your standards.
