The author concludes that our best hope to fix this trend is a return of high gasoline prices.
IMO, that's ONE way it might change, but pretty much the WORST option.
Oh, there are far far worse options. Increasing the cost of something will decrease usage, starting with the least necessary usage. Also, a lot of supposedly "necessary" usage will eventually be reduced or eliminated, possibly after a painful transition. The price could be increased by placing a tax on it, and returning the proceeds to the people in a way that would minimize the damage to the most affected people or industries.
Alternatives such as laws requiring carpooling, laws forbidding gasoline engines, etc would have a similar effect but be painfully inflexible. Certainly less restrictive laws or even "encouraging conservation" could also help, but would have a more limited effect.
You have to "decarbonize" limestone (CaCO3) to Calcium Oxide (CaO) to make cement. You _cannot_ make cement without producing a lot of carbon dioxide, even if your energy source is carbon-free.
Nothing says you have to dump that CO2 into the atmosphere. CO2 has various uses in industry, or can give a slight growth boost to greenhouses.
1) Mine bitcoins using electricity
2) Pay electricity bill using bitcoins
What's draconian about not trusting someone proven to be untrustworthy? Is it because their only job was to be trustworthy?
A properly designed system shouldn't be highly dependent upon any kind of persistence layer, although if you follow the provider's example programs you'll tend to spread dependencies through your code. But a smart designer hides that all away deep down in some kind of abstraction.
A demonstration of exactly how little you are dependent on a vendor is probably a very good thing, if you're a big customer. Oh, we'll run *this* part of our product on the other guy's cloud service and boom. It happens. Shows the vendors who's boss.
Most parents use those games to train their kids with good reflexes and hand-eye coordination.
The developer of this thing has thoughtfully provided a "hello.c" file and cc. Oh, yes, and emacs. So go ahead and type:
cc -o hello hello.c
and marvel at the speed.
This environment is just like my first full-time, non-student programming job. There was no IDE, so we pretty much lived in emacs. I haven't used emacs in decades, but my fingers still remember the key bindings for the commands -- as long as I'm not trying to consciously remember them.
It was on a 68020 running at 16 MHz which delivered a grand total of 2 MIPS at 16 MHz. We shared all that computing power among four programmers, which was luxury because the system was supposed to support 16 users (32 max).
It seems almost inconceivable, but the funny thing is it was really just as fun programming back then as it is now with a supercomputer all to myself. Our office was next to a reservoir, and used to start a compile, wait five minutes for the parsing to catch any syntax error (about 75% of the time), then go for a walk on the 1.5 mile trail around the pond. Then I'd stop in at the convenience store to buy a cup of coffee, and head back to the office, and make would just be finishing up the linking. God forbid you got a link error though. That's why we had time to read the entire Unix manual (all eight sections) cover to cover. Many times.
This has fed my conviction that user perceptions of system speed are as strongly affected by consistency as it is by absolute speed. If you're used to a build taking fifteen seconds,a sudden change to 30 seconds seems unbearable.
From the top of "linux.js"
Copyright (c) 2011-2012 Fabrice Bellard
Redistribution or commercial use is prohibited without the author's
Look, this is a prime example of what I'm talking about. It all seems plausible to the poster because he doesn't personally know any scientists. Trying to organize scientist into a vast, disciplined conspiracy is laughable, if you've ever worked with them. They're waaay more likely to be obstreperous free thinkers than they are to be timid conformists.
You don't need a browser.
Over the course of decades.
HOST SYSTEM RESPONDING, PROBABLY UP...