The next step is to drop sparkling water for regular water. There is no particular difference when you are thirsty, and bubbles have some adverse effects, some say.
This lead me to the following - what if you make a compost pile the size (mass) of Sun? Meaning, it won't be made of hydrogen, but rather some carbon-based molecules. I'm not sure about other atoms in these molecules, but I think carbon is stable enough not to initiate nuclear reactions. So probably fusion won't start. What then?
> RAID or storage replication in distributed storage <..> is not only useless, but actively undesirable
I guess I'm different from most people, good news!
When building my new "home server" half a year ago I made a raid-1 (based on ZFS) with 4 NVMEs. I rarely appear at that city, so I brought the fifth one and put it into an empty slot. Well, one of the 4 nvmes lasted for 3 months and stopped responding. One "zpool replace" and I'm back to normal, without any downtime, disassembly, even reboots. I think that's quite useful. When I'm there the next time I'll replace the dead one, of course.
The same functionality has been in boost [0] for quite a while. So, if you can't see the ugly iterators anymore, but have an outdated compiler, this is an option.
> Once you std::move an object and pass it to someone who takes an rvalue-reference, your local object may very well end up in an invalid state.
As far as I remember, move constructors/assignments must leave the moved-from object in a valid state - just that the standard doesn't say anything about what that state is for standard classes.
Also, I have seen code where some kind of "result" can be moved from an object and then re-generated from scratch with different inputs. In that case it was perfectly valid to use it after move. But that's nitpicking, anyways.
I got so fed up with Outlook that I surveyed the bigger half of the office population to find out the outbound server and switched to Thunderbird under a linux vm. Not sure whether it helped with the keyhole problem tho.
The tool we develop at work has recently moved from RHEL 5 to 6 as the bottomline supported release. For us that meant a switch from GCC 4.8 to 6.3. So it's not that bad.
And when we switch to Red Hat 7 in the next 3-4 years we might start using GCC 8 with all those cool new features!
For some blocks I checked a week ago the transaction fees amounted for approx. 1/3 of the reward. Like, 12.5btc of newly generated coins and 6btc of fees.
Although, to compensate for the next reward halving the fees would need to go further up, and they already aren't acceptable for smaller transactions.
Recalling the first-year university math analysis course, our professor himself told us about Wolfram Alpha. Which followed by a whole year of equations and integrals the site could solve only numerically.
The high enough level of the tasks beats any cheating attempts.
The world seems full of possibilities that would be interesting to check. Doing all forms of art, travelling without destination goals, learning chemistry and making my own boat. I'd change my name to Alexander Shulgin. Or perhaps Genesis C-Ereal.
If the technology revolution stops happening, we should move to the original path.
We had these labs as a base for our course on OS development. Original tasks seemed to be very good - even if you did something wrong, the tests would probably catch it. But those who made our course decided to introduce some changes, which led to the following proportions of spending time: about 0.5-1 hours for the task itself and continiously growing number of hours for debugging, first mistakes in their code, then the bugs we introduced ourselves. My first hacking experience, indeed.