Looking at that data it appears that a majority of California's water for power generation is coming from salinated sources, so at least for California the largest user of fresh water sources is still irrigation (agriculture).
Either way, the point that agriculture takes a lot more water than people watering their lawns still stands.
I would define "post-scarcity" as when you organize your economic system to constrain supply in order to prop up prices.
For instance, the U.S. burns 30% of its corn crop to produce ethanol, which would never happen in a market system, but it happens because of a government mandate.
Still use Windows for HTPC though because I gave up on trying to get Ubuntu to sync video playback correctly after banging my head against the wall for a while.
> Although in our proof of concept demonstrations we rely on the assumption that the light conditions do not change during the exfiltration phase, extending the demos to handle these situations shouldn’t be a problem
They say themselves that their demo is not real world and wont work in the real work and then say it "shouldn't be a problem" to make it work.
Not to mention that it takes 20 seconds of flashing the users screen to do the thing (how is that supposed to work without setting off alarm bells).
As I said, they have no proof of a real world vulnerability, only proof it a staged environment, and they readily admit it.
This "vulnerability" is extremely hypothetical and they have not given proof that it can be exploited in the field. Just conjecture and a demo in a totally unrealistic environment.
Yes, multi-threading has high overhead to provide the illusion of parallel operation, but when all the cores are saturated you are in the same boat, whether you have 1 or 100.
The benefit to programs that don't use threading and use event loop and shared nothing multi-process is that they don't have the overhead when things are maxed out.
This is why virtually every high performance server (nginx, redis, memcached, etc) is written this way and things like varnish (thread per request) are multiples or orders of magnitude slower.
Funny people criticizing nodejs for using the same architecture that all the best-in-class products use.
> Tesla’s vertical integration of service centers has an interesting side effect - recalls and repairs are pretty cheap
This is assuming that Tesla's centrally managed monolithic dealer/service network will be run more efficiently than the distributed and competitive dealer networks typical of other car companies.
That assumption runs counter to typical economic thinking that competitive market based solutions will be more efficient.
> Predicting that it will rain at 2:00 PM November 10, 2017 is much more difficult than predicting that the average summer of 2040-2060 will be hotter than the average from 1980-2000
Yes, it is much easier to make predictions about the far future which no one will remember or care about when the time comes to test there veracity.